ChatGPT Ads Conversion Tracking: Complete CAPI + Pixel Guide

Why Tracking Fails First

OpenAI's ad platform is younger than Google's by two decades, so its measurement stack is still maturing. When a sale does not show up in the ads dashboard, most advertisers blame the channel and pause. In the overwhelming majority of debugging sessions, the real culprit is one of four implementation gaps: a missing oppref, a wrong minor-unit amount, a mismatched event_id, or simply checking too early.

Conversations with OpenAI's support and its documentation confirm that conversion credit requires all four conditions— event received, matched to a configured event, inside the attribution window, and connected to an eligible click. Fix the plumbing and most “ChatGPT doesn't convert” complaints disappear.

The 14 Standard CAPI Events

The Conversions API accepts a fixed vocabulary of standard events. Sending anything outside of it prevents matching, because auto-mapping is limited. The full list:

Match event names exactly. Use order_created for purchases on most e-commerce setups, lead_created for form submissions, appointment_scheduled for bookings, and trial_started for SaaS free trials. If none fit, apply the custom event with a descriptive label.

The Four Credit Conditions

OpenAI reports a conversion when, and only when, all of these hold:

1. 1

   The event is received

   Your pixel or CAPI delivered the event payload to OpenAI successfully (HTTP 200, valid JSON).

2. 2

   It matches a configured conversion event

   The event name and configuration match a conversion you selected for attribution in the OpenAI Ads dashboard.

3. 3

   It falls inside the attribution window

   The event timestamp is within the campaign's configured attribution window from the ad click.

4. 4

   It connects to an eligible click

   The oppref parameter ties the event back to a real, valid ad click from your campaign.

This is why a browser pixel alone can under-report: it sometimes loses the oppref across domains, while the Conversions API preserves it server-side. Best practice is to run both with deduplication — not one or the other.

Pixel + CAPI Setup

The robust architecture mirrors Meta and Google: a browser pixel captures events client-side, and a Conversions API endpoint sends the same events server-side where they cannot be lost to ad blockers or privacy restrictions. For WordPress, the free Ridoway Pixel plugindoes all of this automatically — including deduplication.

1. 1

   Install the pixel: Add the OpenAI browser pixel snippet to your site so page_viewed and standard events fire.

2. 2

   Add the Conversions API: Forward order_created, lead_created, and purchase events from your server with full order data.

3. 3

   Include oppref: Keep the utm/oppref click parameter intact in server-side payloads so clicks map to events.

4. 4

   Send minor-unit amounts: Convert totals to integers in the smallest currency unit (4200, not 42.00).

5. 5

   Use event_ids: Generate one event_id per purchase and send it in both pixel and CAPI so OpenAI dedupes for you.

oppref, Minor Units, and event_ids

Verifying Events

Before trusting any CPA, verify in this order:

• Confirm network calls: the pixel request returns 200 with a valid JSON response body.
• Use ChatGPT Pixel Helper in Chrome to see which CAPI events fired on the thank-you page.
• Run the network “server events” check and confirm the event shows a matching event_id and minor-unit value.
• Wait the full 24–48 hour reporting window before judging conversion volume.
• Cross-check one real order in the OpenAI dashboard before drawing any conclusion about CPA.

Once events show “Active” and cross-check on an actual order, your optimization signal is real. That is the moment the algorithm can start learning from purchases instead of clicks.

Frequently Asked Questions