ChatGPT Ads conversion tracking is the process of sending conversion events to OpenAI so Ads Manager can credit them to ads in ChatGPT. Events arrive through the measurement pixel, a JavaScript snippet on your pages; the Conversions API, a server-to-server link from your backend; or a measurement partner, a third-party tool that sends them for you.
By default Ads Manager credits a conversion to a click within 30 days or an impression within 1 day, as of October 2026. This guide is part of our analytics, tracking and privacy hub. It covers what OpenAI announced on October 5, 2026, which setup fits which business, how to avoid double counting and why the numbers will not match GA4. For formats, bidding and access, start with the ChatGPT Ads explainer.
The short recommendation: run the pixel and the Conversions API together with shared event IDs, add your own UTM parameters to every ad URL, and judge results on your backend order or lead count, not on any single dashboard.
How does ChatGPT Ads conversion tracking work?
ChatGPT Ads conversion tracking connects three parts: a data source that receives events, a conversion event setting that defines what counts as a conversion, and the campaign that uses that setting. The data source is a pixel ID, and events reach it from the browser, from your server or from a partner.
The measurement pixel reads the oppref click ID from the landing page and sends browser events. The Conversions API sends the same events from your backend, and partners such as Triple Whale, Hightouch or AppsFlyer send or attribute them for you.
A conversion is an action you want people to take after an ad, such as a purchase or a lead. In OpenAI's conversion tracking docs, you create a pixel, set an event type such as order_created and attach it to a campaign.
The measurement pixel docs describe oppref as a privacy-preserving identifier read from the landing page URL and stored in the first-party cookie __oppref for 30 days.
OpenAI supports 13 event types, from page_viewed and lead_created to order_created and custom. A campaign that bids for conversions needs exactly one active standard event, and custom events cannot be the optimization goal.
What did OpenAI announce for measurement on October 5, 2026?
OpenAI announced on October 5, 2026 that advertisers can send conversion data to ChatGPT Ads through Hightouch, Tealium and LiveRamp, and measure results with a group of attribution and incrementality partners. The same post introduced a visual ad format to be tested during image generation in the US.
Here is how the news breaks down by source.
- Confirmed by OpenAI: the announcement names Hightouch, Tealium and LiveRamp for conversion data, and AppsFlyer, Triple Whale, Adjust, DV Rockerbox, Northbeam, Branch, Singular, Kochava, Airbridge and Tenjin for Conversions API, reporting and click attribution. It says Haus, Measured and WorkMagic will "explore geo-based experiments to help advertisers understand the causal impact of ChatGPT Ads," and names Fospha, Measured and INCRMNTAL as full-funnel measurement partners. DoubleVerify and Integral Ad Science run brand suitability pilots.
- Reported by trade press: PPC Land counts 22 firms, 20 in measurement roles, and adds Kantar and Cint for brand studies. It also notes that the partner case studies came without spend, dates or sample sizes. Digiday frames the update as a response to buyer complaints about measurement, formats and inventory.
- Speculation: that partner data will make ChatGPT Ads easier to compare with search. Nothing published so far shows that.
Pixel, Conversions API or a measurement partner: which setup fits your business?
The right ChatGPT Ads tracking setup depends on where your conversions happen. Websites with simple forms can start with the pixel, stores and lead businesses with a backend should add the Conversions API, apps need a mobile measurement partner, and companies with a customer data platform can route events through Hightouch, Tealium or LiveRamp.
The Conversions API docs say the API accepts batches of up to 1,000 events, rejects the whole batch if one event fails, and only takes events from the last 7 days. Emails and phone numbers must be SHA-256 hashed.
The table below is our own recommendation; the image tag limits come from OpenAI's image tag docs, which say it loads with the page and does not support a user object.
| Business type | Recommended setup | Why | Watch out for |
|---|---|---|---|
| Static site, conversion on a thank-you page | Image tag or pixel | Event fires on page load | The image tag cannot send user data or track clicks |
| Lead generation with forms | Pixel plus Conversions API for qualified leads | Server events survive blocked scripts | Same event ID in both channels |
| Ecommerce store | Pixel plus Conversions API, or Triple Whale or Northbeam | Purchase value feeds ROAS reporting | Amounts in minor units, currency required |
| Mobile app | Mobile measurement partner | Installs happen outside the browser | Click-based attribution only |
| Company with a CDP or offline sales | Hightouch, Tealium or LiveRamp | Reuses existing event pipelines | Events older than 7 days are rejected |
How do you set up the OpenAI pixel and Conversions API without double counting?
Setting up ChatGPT Ads conversion tracking without double counting means sending each conversion from the browser and the server with the same event name and event ID. Deduplication is the step in which OpenAI matches copies on pixel ID, event name and event ID, keeps the first one it receives and ignores the rest.
The Conversions API docs say to reuse one value as API id and pixel event_id.
- Choose one goal event. Bid on one standard event, such as
order_created; keep the others for reporting. - Create the pixel. Create it in the conversions section of Ads Manager and add the script with
oaiq("init")and your pixel ID to every page head. - Wire consent. Call
oaiq("consent", false)until the visitor agrees; the pixel measures by default. - Keep the click ID. Make sure redirects and checkout steps keep the
opprefparameter. - Send values correctly. Pass
amountas an integer in minor units (12999 for 129.99 dollars) pluscurrency. - Mirror events on the server. Post the same event to the Conversions API with the order or lead number as event ID, plus
opprefwhen available. - Test before launch. Use
debug: truein the browser andvalidate_onlyon the API, then look forpixel_sdkandserver_to_serverrows in recent events.
How do you connect a measurement partner to ChatGPT Ads?
ChatGPT Ads connects to web measurement partners such as Fospha, Hightouch, INCRMNTAL, LiveRamp, Northbeam, Rockerbox, Triple Whale and WorkMagic, and to mobile measurement partners such as Adjust, Airbridge, AppsFlyer, Branch, Kochava, Singular and Tenjin. A web partner authenticates with an Ads Manager API key, or with a pixel ID and Conversions API key.
Both partner lists come from OpenAI's help articles on measurement partner integrations and mobile measurement partners, as of October 2026. The web article says you create a key under "Settings", "General", "API Keys" in Ads Manager, then enter it in the partner tool. Triple Whale requires at least one active campaign first.
Which attribution windows does ChatGPT Ads use?
An attribution window is the period after an ad interaction in which a conversion can still be credited to that ad; ChatGPT Ads uses 30 days after a click and 1 day after an impression by default, per OpenAI's reporting docs as of October 2026. View-through attribution is credit for a conversion after an impression without a click.
The reporting docs expose two settings for reports pulled through the API: attribution_window_days accepts 7, 14 or 30, so you can shorten the click window, and view_through_attribution_window_days accepts 0 or 1, so you can switch view-through off. When a conversion qualifies for both, the click takes precedence.
Three more details affect how you read the numbers:
- Reporting date. By default conversions are dated on the day of the ad interaction (
ad_event_time), not on the day of the purchase. You can switch toconversion_time. - Freshness. Conversions update in daily processing, and OpenAI says to allow at least one day before they appear.
- History. Most metrics keep 365 days of history; hourly and product reporting keep 30 days.
Mobile partners are different: OpenAI says their attribution windows are configured in the partner tool, separately from Ads Manager. For background on how windows and models shift credit, see our guide to attribution models.
Why don't ChatGPT Ads conversions match GA4?
ChatGPT Ads conversions do not match GA4 because the two systems count different things. ChatGPT Ads credits view-through conversions, dates them on the ad interaction and attributes within its own windows, while GA4 only sees sessions, applies its own attribution model and misses users who declined analytics consent.
Traffic sources add a second layer. OpenAI's publishers FAQ documents utm_source=chatgpt.com on referral links in ChatGPT answers, but not on ad clicks. OpenAI's help article on creating ads says you can add your own UTM parameters to each ad's destination URL. Without them, ad visits can blend into GA4's AI Assistant channel. The AI Assistant channel is the GA4 default channel for sessions with the medium ai-assistant, according to Google's default channel group. With medium cpc and a custom source, they land in Paid Other, which is the GA4 default channel for paid traffic that matches no more specific paid channel. Our guide to Gemini referral traffic covers an AI channel for organic visits.
Hypothetical worked example. Ads Manager reports 50 order_created conversions for a month, 41 from clicks and nine from views. GA4 shows 28 purchases with the custom ChatGPT Ads source. The gap of 22 breaks down like this:
- Nine view-through conversions. GA4 never sees impressions.
- Seven later purchases. Buyers clicked, left and returned through another channel, which GA4 credits.
- Four declined consent. The Conversions API captured the orders; GA4 did not.
- Two date shifts. Clicks at month end converted the next month, which ChatGPT Ads reports on the click date.
The numbers are invented for illustration. The method is the point: match backend orders first, then explain each bucket of difference.
Common mistakes with ChatGPT Ads conversion tracking
The most common mistakes with ChatGPT Ads conversion tracking are lost click IDs, mismatched event IDs and wrongly formatted values. Each one either drops conversions, doubles them or breaks return on ad spend, and each can be caught with a single test conversion before launch.
- Stripping the oppref parameter. Redirects that drop query parameters remove the click link. Test the path from ad URL to thank-you page.
- Using different IDs in pixel and server events. Use the order or lead number in both.
- Sending amounts as decimals. OpenAI expects integers in minor units plus a currency, or revenue and ROAS break.
- Choosing a custom event as the bidding goal. Custom events cannot optimize; map the action to a standard event.
- Judging a campaign on the same day. Conversions arrive in daily processing, so compare full weeks.
- Ignoring click quality. PPC Land reported that TrafficGuard flagged 0.1% to 34% of clicks as invalid per advertiser across 40,021 clicks from August 24 to September 14, 2026, in a study that was not audited. Check sessions and bounce patterns behind your clicks.
- Treating view-through as click credit. Report click and view conversions separately, or set the view window to 0 when comparing with search.
Retailers find feed reporting in the guide to ChatGPT Ads product feed campaigns.
