Track the conversions of your ChatGPT ads
Published on by the Oriva team. Updated on .
For a ChatGPT ad to know it produced a sale, OpenAI offers two main paths: the OpenAI pixel, a script placed in the browser, and the Conversions API, which receives sales from a server. In both cases, tying a sale to the ad rests first on oppref, the identifier OpenAI adds to your site's address when someone clicks: it is the most direct signal, not the only one. Use both paths with the same event identifier, configure the pixel's consent, which is “yes” by default, and create a conversion setting of the right type: an accepted send does not count until the campaign uses an event that matches it. To optimize your campaigns on conversion, send your purchases under their standard type.
Situation on October 13, 2026
- What OpenAI offers. A pixel for the browser, a Conversions API for the server and a tracking image with no JavaScript. Since August 31, 2026, advertisers in 31 European markets, including France, can buy their ads themselves in Ads Manager, if the entity that advertises and is billed is based in one of those countries.
- What traps you. An event can be accepted and show 0 conversions if it does not match the one your campaign uses. OpenAI says so in its help center, and we saw it on a real account (section “Accepted does not mean counted”).
- What changed recently. Since September 30, 2026, OpenAI's reporting API lets you choose the attribution windows (click and view), and conversion totals include one-day views by default: they can differ from older reports. The help center also describes a choice between impression and click billing for the conversion objective, which the developer documentation does not carry over.
This page is updated when one of these points changes; the date at the top is the one to go by.
Who sees ChatGPT ads, and since when in France?
Ads are shown to users of ChatGPT's free and Go plans; Plus, Pro, Business, Enterprise and Edu subscribers do not see them, nor do accounts identified as minors, nor temporary chats. What dates from the end of August 2026 is the opening: OpenAI announced on August 18 the extension of ChatGPT Ads to 31 European markets, including France, and self-serve through Ads Manager has been available there since August 31, 2026, if the entity that advertises and is billed is based in one of those countries. A company can therefore buy its ads itself, without going through an agency.
What is oppref?
It is ChatGPT Ads' click identifier, the equivalent of Google's gclid or Meta's fbclid. OpenAI adds it to the address of your landing page at the moment of the click. It is what later ties a sale to the ad that triggered it.
The OpenAI pixel reads it by itself and keeps it in a cookie (__oppref) for the following pages. The Conversions API does not capture it: it is up to you, or your tool, to pick it up when the visitor arrives and send it back with the sale. A sale sent by the server without oppref is accepted, but OpenAI ties it to a click less directly, through the customer data. It publishes no figure on what you lose. The details are on the oppref page.
OpenAI pixel or Conversions API?
| OpenAI pixel | Conversions API | |
|---|---|---|
| Where it runs | In the visitor's browser | On a server |
| Picks up oppref | Yes, automatically | No, you have to pass it along |
| Ad blockers | Can keep it from going out | Do not see it |
| Setup | A script on your site | A server call with an API key |
| Consent | “Yes” by default, to configure | Handled by you before sending |
The rows about the browser and ad blockers are a general fact about pixels, not something OpenAI states.
The two complement each other. OpenAI deduplicates them if you give them the same event identifier (see the next section). A third path exists, the Image Tag, a plain image with no JavaScript: it does not capture oppref.
Accepted does not mean counted
When the Conversions API answers that your event is accepted, it tells you it arrived, not that it counts. OpenAI's help center describes it in its question “Why do my conversion events show 0 in Ads Manager?”: an event that was triggered and accepted shows 0 if it does not match the conversion event configured for the campaign.
Three things have to line up:
- the type: for a standard event, the configured type is the one you send,
order_createdfor example; - the name, for a custom event: the setting is of the Custom type and its name matches exactly what you send. An identical display name is not enough, and OpenAI lowercases the name;
- the attachment: the right conversion is attached to the campaign before traffic starts. Events from before are not replayed into the corrected setting.
After the fix, run eligible traffic again and allow 24 to 48 hours before concluding. To see what OpenAI actually received, its API returns a sample of the events of the last fifteen minutes or so, with their origin: pixel_sdk for the browser, server_to_server for the server. A validation-only send (validate_only) does not show up there. The Create a ChatGPT Ads conversion event guide walks through the steps on a real account.
How do I avoid counting a sale twice?
OpenAI recognizes a duplicate when two events carry the same Pixel ID, the same event name and the same identifier (event_id on the pixel side, id on the Conversions API side). It keeps the first one received and ignores the following ones. Use your order reference as the identifier, on both sides.
The consent trap
By default, the OpenAI pixel assumes the visitor has given their consent. In France, the CNIL, the national data protection authority, requires the visitor's prior consent for advertising-related trackers, and that applies to any site whose visitors are in France. So initialize the pixel with consent set to “no” (oaiq("consent", false) before oaiq("init", …)), then switch it to “yes” from your cookie banner when the visitor accepts (oaiq("consent", true)). The pixel also remembers a refusal already expressed.
OpenAI writes that, if consent is required to measure conversions, you should use the pixel's consent feature. It does not say that the law requires it: it is the CNIL that says so, with the principle of prior consent and personalized-advertising cookies named expressly. While consent is “no”, the pixel sends nothing, and events blocked in the meantime are not replayed if the visitor accepts later. A refusal also deletes the __oppref and __obref cookies. On the Conversions API side, OpenAI offers no consent setting: it is up to your server to send only what the visitor accepted and, for obref, to stop sending it if they withdraw their consent.
Optimize your campaigns on sales
ChatGPT Ads offers conversion-optimized campaigns (“oCPC” bidding): OpenAI shows your ad to those most likely to buy. Depending on your Ads Manager, these campaigns are billed per impression or per click: OpenAI's help center describes that choice, while the developer documentation still describes payment per click. Look at what your account offers. These campaigns are in open beta, and they need:
- conversion tracking in place, through the pixel, the Conversions API or both;
- a single standard event as the goal, for example
order_createdfor a purchase. A custom event cannot serve as the goal. The chosen event cannot be changed after creation: to change it, clone the campaign; - enough conversions for OpenAI to judge performance. OpenAI gives no numeric threshold.
Practical consequence: send your purchases under the order_created type, never under a name of your own, or you will not be able to optimize on them.
What to set up in Ads Manager
- In the Conversions tab, create your pixel: Ads Manager gives you its Pixel ID and, if you go through the server, a Conversions API key;
- create a conversion setting: it tells OpenAI which event counts as a conversion, and it is the one your campaign uses (see “Accepted does not mean counted”);
- choose the attribution window. An event setting takes a 30-day window after the click. In Ads Manager reports, you choose click over 7, 14 or 30 days and view over 0 or 1 day; changing that window changes neither optimization nor billing.
Do you need a tool like Oriva?
Not necessarily. If you only advertise on ChatGPT and the OpenAI pixel, properly set up for consent, is enough for you, you can stop there. If you already have a server-side Google Tag Manager container, you can build the send to the Conversions API in it: that is Oriva's view, OpenAI does not describe this path.
A tool like Oriva becomes useful when you want the Conversions API without writing or maintaining server code, and above all when you also send your sales to Meta, TikTok or Google Ads: one installation, one consent, one log to prove each send.
The setup details are on the ChatGPT Ads page.
Frequently asked questions
Do I need the pixel or the Conversions API?
Both, with the same event identifier: OpenAI deduplicates them by Pixel ID, event name and identifier, and keeps the first one received. The pixel sees what the browser does; the API receives a sale the browser did not see.
Why are my sends accepted but I see 0 conversions?
Because the event does not match the one your campaign uses: the type, the exact name for a custom event, or the attachment to the campaign before traffic starts. Fix the setting, run eligible traffic again and wait 24 to 48 hours.
Do I have to send oppref from the server?
It is optional, but it is the most direct signal: the Conversions API does not capture it by itself, so your server has to keep it when the visitor arrives and send it back as it is with the sale. See the oppref page.
What does the warning “Ad click information is missing or cannot be connected” mean?
It is the one Ads Manager shows when events arrive without usable click information. OpenAI then asks you to keep oppref across redirects and navigation, and to include it in the events sent by the server.
Does the OpenAI pixel respect consent by default?
No: it initializes consent to “yes” unless you set it to “no” or it finds a refusal already expressed. Set it to “no” before initialization, then to “yes” when the visitor accepts.
Until when can a sale be sent?
The server must send an event within 7 days of its date, and no more than 10 minutes in the future. A single refused event makes the whole batch fail.
How long does oppref stay usable?
OpenAI does not document how long the identifier itself stays valid. Only the pixel cookie's duration is documented: 30 days.
Keep reading
- oppref: the ChatGPT Ads click identifier: What oppref is, how the OpenAI pixel keeps it (__oppref cookie, 30 days), why the API does not capture it and what to send back.
- Create a ChatGPT Ads conversion event: An accepted send can show 0 conversions without a conversion event of the right type, attached to your campaign. Lived on a real account.
- ChatGPT Ads: server-side Conversions API: Send your purchases and leads to ChatGPT ads from the server, with the oppref click ID and deduplication against the OpenAI pixel.
- ExitPass: its sales to Meta and ChatGPT Ads: One hour fifteen between creating the domain and the first visit: how its sales reach Meta and ChatGPT Ads, and what that does not prove.
Sources
Pages of OpenAI and the CNIL read on October 13, 2026. OpenAI's developer documentation shows no update date per page; the help center only shows relative durations.
- OpenAI, Measurement Pixel
- OpenAI, Conversions API
- OpenAI, Conversion tracking
- OpenAI, Conversion-optimized campaigns
- OpenAI, Image Tag
- OpenAI, Troubleshooting
- OpenAI, Ads API changelog
- OpenAI, help center: measure results
- OpenAI, help center: conversion measurement
- OpenAI, help center: Ads Manager availability
- OpenAI, help center: conversion-optimized campaigns
- OpenAI, ChatGPT Ads expands across Europe
- CNIL (in French), Cookies et traceurs : que dit la loi ? (cookies and trackers: what does the law say?)