OpenAI Conversions API — How to Send WooCommerce Purchases to ChatGPT Ads

What Is OpenAI’s Conversions API?#

OpenAI’s Conversions API is a server-to-server endpoint that sends conversion events directly from your backend to ChatGPT Ads, bypassing browser-side limitations.

OpenAI launched its Conversions API and JavaScript pixel in May 2026, with conversion-optimized oCPC campaigns rolling out on June 5 for accounts that configured tracking before June 1 (Search Engine Roundtable, 2026). That timeline matters. Until May, ChatGPT Ads only offered CPM and CPC objectives — awareness and traffic. Conversion optimization requires a closed attribution loop: your store has to send post-click purchase data back to OpenAI before the algorithm can optimize toward buyers instead of clickers.

The Conversions API is that closed loop. It’s a server-to-server integration where your WooCommerce backend sends a POST request to OpenAI’s endpoint every time a qualifying event occurs — a purchase, a lead form submission, a checkout start. OpenAI explicitly describes the Conversions API as a more reliable tracking source than the pixel alone (OpenAI Developer Docs, 2026). If you’ve implemented Meta’s Conversions API or Google’s Enhanced Conversions, you’ll recognize the architecture. The difference is that this one feeds ChatGPT’s ad delivery algorithm, and the channel is six months old.

You may be interested in: GTM Is the Single Point of Failure — When Ad Blockers Kill Your Tag Manager, Every Tag Dies with It

Why Server-Side Matters for WooCommerce#

Browser-side tracking alone loses conversions to ad blockers, Safari ITP, and consent rejection — server-side events recover them.

29.5% of internet users worldwide use ad-blocking tools — roughly 1.77 billion people (Backlinko via GWI, 2025). For WooCommerce stores running ChatGPT Ads, that number translates directly into invisible conversions: purchases that happen in sessions your pixel never saw. The customer clicked a ChatGPT ad, landed on your store, bought something, and your Ads Manager shows nothing.

29.5% of internet users worldwide use ad-blocking tools, roughly 1.77 billion people as of Q2 2025 (Backlinko via GWI, 2025). Every blocked session is a conversion your pixel cannot record.

Here’s the thing… the OpenAI pixel fires client-side JavaScript. Ad blockers, Safari’s Intelligent Tracking Prevention, and consent rejections can all prevent it from executing. When the pixel doesn’t fire, the oppref click identifier doesn’t get captured, and the purchase event never reaches OpenAI. Your campaign looks like it’s underperforming even when it’s driving real revenue.

Server-side events fix this. When a WooCommerce order completes, your server sends the purchase data directly to OpenAI’s API endpoint. No browser involved, no script to block, no cookie to expire. The request originates from your hosting infrastructure, and the only thing standing between your order data and OpenAI’s optimization algorithm is a stable internet connection.

The 10 Standard Events and What WooCommerce Needs#

OpenAI supports 10 standard conversion events — WooCommerce stores should prioritize order_created and work backward through the funnel.

The Conversions API supports 10 standard conversion events plus one custom event type (OpenAI Developer Docs, 2026). Here’s how they map to a WooCommerce store’s purchase funnel:

OpenAI’s Conversions API supports 10 standard conversion events plus one custom event type (OpenAI Developer Docs, 2026). For WooCommerce, order_created is the event that unlocks oCPC optimization.

Start with order_created. That’s the event OpenAI’s oCPC algorithm needs to optimize toward buyers. Once purchase tracking is reliable, work backward: add checkout_started and items_added to give OpenAI upper-funnel signals. Conversion tracking is a hard prerequisite for oCPC campaigns — it has to be standard events, not custom ones (SweetCode, 2026).

How the oppref Click Identifier Works#

The oppref parameter is OpenAI’s click identifier — lose it between the ad click and the purchase, and the conversion cannot be attributed.

When a user clicks a ChatGPT ad, OpenAI appends a click reference to your landing page URL in the format ?oppref=gAAAAAb123 (OpenAI Help Center, 2026). The JavaScript pixel captures this value and stores it in a first-party cookie named __oppref.

For server-side events, you include the oppref value in your Conversions API payload. Without oppref, OpenAI can still attempt to match the conversion using hashed email or phone data, but the match quality drops. The oppref is the strongest attribution signal available — treat it like Meta’s fbclid or Google’s gclid.

The practical risk for WooCommerce stores: if your checkout redirects through a payment gateway on a different domain, the oppref cookie may not follow. You need to capture the oppref value early — ideally when the order is created — and store it as order meta. Then your server-side event handler reads it from the order record, not from a cookie that may have been lost.

The WooCommerce-to-Conversions-API Data Flow#

Sending a WooCommerce purchase to OpenAI requires a pixel ID, a Conversions API key, the order data, and the oppref click identifier.

The setup involves three resources you create in OpenAI Ads Manager: a web conversion source (returns a Pixel ID), a Conversions API key, and an event setting that defines which event you’re optimizing for. Store the Conversions API key server-side — OpenAI explicitly warns against exposing it in browser code (OpenAI Developer Docs, 2026).

The data flow for a WooCommerce purchase event works like this:

Step 1: Capture. The woocommerce_thankyou hook fires after payment confirmation. Your handler reads the order object — total, currency, line items, customer email, phone.

Step 2: Hash. Customer PII (email, phone, address) gets SHA-256 hashed before leaving your server. Automatic advanced matching is on by default for new web pixels, hashing form data with SHA-256 (Choice OMG, 2026). Your server-side implementation should match that hashing to ensure deduplication works.

Step 3: Send. POST the event to OpenAI’s Conversions API endpoint with your Pixel ID, the event type (order_created), the oppref value, the hashed user data, and the event_id shared with the browser pixel.

Step 4: Verify. OpenAI’s API returns a response confirming receipt. Attributed conversions take 24 to 48 hours to appear in Ads Manager (Choice OMG, 2026). Don’t panic if the numbers aren’t instant.

Deduplication: Pixel Plus Server-Side#

When both pixel and server-side events fire for the same purchase, a shared event_id prevents double-counting.

OpenAI’s recommended architecture is a hybrid: pixel on the frontend, Conversions API on the backend. When a user completes a purchase with their browser unblocked, both sources will fire an order_created event. Without deduplication, that’s double-counted revenue in your Ads Manager.

The solution is straightforward. Generate a unique event_id for each purchase — typically the WooCommerce order ID — and send the same value from both the pixel and the Conversions API. OpenAI deduplicates on the combination of event_id and event type, prioritizing the server-side event when both arrive (OpenAI Help Center, 2026). This is architecturally identical to how Meta handles CAPI deduplication and how Google handles Enhanced Conversions.

You may be interested in: Seven New WooCommerce Server-Side Tracking Plugins Launched in 2026

ChatGPT Ads Performance Benchmarks for E-commerce#

Early e-commerce conversion data from ChatGPT Ads shows lower volume but higher-intent clicks compared to Google and Meta.

ChatGPT Ads e-commerce conversion rates range from 1.0% to 2.5%, while higher-intent service verticals see 4–7% click-to-conversion (First Page Sage, 2026). Translation: fewer clicks, but the people who do click from a ChatGPT conversation are further along in their buying decision.

The volume constraint is structural. ChatGPT shows a single ad per response, and ads only reach Free and Go tier users. Typical ChatGPT ad CTR runs 0.3% to 1.5%, well below Google Search’s 6.64% average. But those fewer clicks convert at 1.5 to 4x the rate of Google Search in matching verticals (Lapis Research, 2026).

For WooCommerce stores, the math is clear: this isn’t a volume channel yet. It’s a test-and-learn channel where accurate conversion tracking is the difference between knowing what works and guessing. Without the Conversions API feeding real purchase data back to OpenAI’s algorithm, your oCPC campaigns are optimizing blind.

How This Compares to Meta CAPI and Google Enhanced Conversions#

OpenAI’s Conversions API follows the same server-to-server pattern as Meta CAPI and Google Enhanced Conversions, with minor differences in identifier handling.

The pattern is identical. If your WooCommerce store already sends purchase events to Meta’s CAPI and Google’s Enhanced Conversions, adding OpenAI as a third destination is an incremental step — not a new architecture. The event payload structure is similar, the hashing requirements are the same, and the deduplication logic follows the same event_id principle.

For stores running Transmute Engine, this follows the same pattern the tool already uses for routing events to multiple ad platform APIs from a single server-side event pipeline. Adding OpenAI as a destination means one more endpoint in a system designed to handle exactly this kind of multi-platform delivery. You can learn more about how that works at seresa.io/transmute-engine.

Key Takeaways#

• OpenAI’s Conversions API launched May 2026: It sends purchase events server-to-server from your WooCommerce backend to ChatGPT Ads, bypassing ad blockers and browser restrictions.
• order_created is the critical event: Start with purchase tracking to unlock oCPC optimization, then add checkout_started and items_added for upper-funnel signals.
• Preserve the oppref click identifier: Capture it on landing and store it as WooCommerce order meta — it’s the strongest attribution signal for linking purchases to ChatGPT ad clicks.
• Use a shared event_id for deduplication: Both the pixel and the Conversions API should fire the WooCommerce order ID as the event_id so OpenAI doesn’t double-count.
• ChatGPT Ads is a test-and-learn channel for e-commerce: Conversion rates of 1.0–2.5% on lower volume means accurate tracking matters more, not less.