Full Answer

The endpoint itself is straightforward: POST requests go to bzr.openai.com/v1/events with your Pixel ID appended as a query string. Authentication uses a Conversions API token generated inside OpenAI Ads Manager — the same dashboard where you create your ChatGPT Ads campaigns. Every request carries the token in the Authorization header alongside the event payload.

The payload follows a predictable structure. Each event includes an event_name (order_created, checkout_started, or items_added), a timestamp, and a user_data object containing the customer's hashed PII. OpenAI requires SHA-256 hashing for email, phone, first name, and last name — these fields are matched against OpenAI's user graph for attribution. Geographic fields (city, state, postcode, country) are sent unhashed. Getting the hashing wrong means the event arrives but never matches, so your conversions show as unattributed.

For WooCommerce stores, no native plugin handles this yet. The [Netro Ads plugin](https://wordpress.org/plugins/netro-ads/) is the closest option, sending events server-side through a WordPress hook on order completion. Stores not using that plugin need a custom integration — typically a WooCommerce action hook (woocommerce_order_status_completed) that collects the order data, hashes the required fields, and sends the POST. Before building anything, [confirm your tracking infrastructure is ready](https://seresa.io/blog/woocommerce-tracking/before-you-spend-on-chatgpt-ads-the-woocommerce-tracking-health-checklist) — the endpoint accepts your events regardless, but without a working Pixel ID and valid token the data goes nowhere useful.