ChatGPT Ads server-side conversion tracking
Advertising opened in ChatGPT on 24 August 2026 across 31 European markets, including France. Measure it properly from day one: send your store's conversions to the ChatGPT Ads Conversions API from the server, deduplicated with the OAIQ pixel on a shared event ID, gated on marketing consent and processed in the EU. One connection key, and the same event also reaches Meta CAPI, GA4, TikTok, Pinterest, Google Ads and Microsoft Advertising.
Your ChatGPT Ads API key stays encrypted on our side: you never paste it into your store.
What is ChatGPT Ads measurement?
Since 24 August 2026, advertisers can run ads inside ChatGPT in 31 European markets, France included. Ads appear only on Free and Go accounts, and in Europe targeting is contextual: the topic of the conversation, approximate location and device, with no use of conversation history or memory. On the advertiser side, measurement rests on two layers: a browser pixel (OAIQ) and a Conversions API your server calls directly.
Contextual ads, 31 European markets
Live since 24 August 2026, visible on Free and Go accounts only. In Europe, targeting uses the conversation's topic, approximate location and device: not the visitor's history or memory.
The OAIQ pixel: the browser layer
oaiq.min.js reads the oppref URL parameter
carried by the ad click and stores it in a first-party
__oppref cookie valid 720 hours. That signal is what
ties a later conversion back to the ad.
The Conversions API: the server layer
Your server posts events to
https://bzr.openai.com/v1/events with a Bearer key,
deduplicated with the pixel on a shared event ID. OpenAI presents
this API as more reliable than the pixel alone.
Looking for the wider picture rather than ChatGPT Ads specifically? Read what server-side tracking is and how it works.
Why measurement must be ready before your first campaign
ChatGPT Ads is a brand-new channel, and its attribution model rewards advertisers who arrive with their measurement already in place.
-
An oCPC campaign optimises on one single event
chosen from the standard events and locked when the campaign is created. If that event is not arriving reliably, the campaign learns on nothing.
-
Conversions appear within 24 to 48 hours
so a measurement problem discovered after launch costs you days of blind spend before the fix even shows up in reporting.
-
The pixel alone is exposed to the browser
ad-blockers can stop
oaiq.min.jsfrom loading, and browser cookie limits weigh on the__opprefcookie, exactly as they do on every other advertising pixel. OpenAI itself presents the Conversions API as more reliable than the pixel alone.
The channel is too young for anyone to promise you performance numbers, and we won't. What we can make sure of is that when your first campaign spends, every conversion it produces is delivered, deduplicated and visible.
A managed ChatGPT Ads connection, without the plumbing
Install the connector for your platform, or call our API directly, and every funnel step is mirrored server-side to the ChatGPT Ads Conversions API, deduplicated with the OAIQ pixel and gated on consent.
Conversions that survive the browser
The server-side event is delivered from your infrastructure. When the pixel is blocked, that event is the one OpenAI receives.
Deduplication handled for you
Pixel and server event share the same event ID, so OpenAI matches the two and counts each conversion once. You don't wire up the matching logic yourself.
The click signal, captured
Our modules capture the oppref URL parameter and the
__oppref/__obref cookies, so the server
event carries the signal that ties it back to the ad.
All ten standard events, correct units
From page_viewed to order_created,
lead_created and subscription_created: with
amounts converted to minor units as their API requires.
Consent enforced twice
The browser layer injects nothing without marketing consent, and the dispatcher applies a second check before anything reaches OpenAI.
API key never in your store
Your ChatGPT Ads Bearer key is encrypted on our side. A compromised store front-end can't leak it.
Inspector to prove it works
Every event and its per-destination status is visible in the Inspector, so you can confirm delivery to OpenAI rather than assume it.
One event, seven destinations
The same conversion also reaches Meta CAPI, GA4, TikTok, Pinterest, Google Ads and Microsoft Advertising, no second integration to build.
Connecting your store to the ChatGPT Ads Conversions API
Add your ChatGPT Ads API key once
In your DataFirefly account, add the API key from your ChatGPT Ads account. It is stored encrypted and never sent to your store.
Install the connector for your platform
PrestaShop,
WooCommerce or
Shopware: then paste
your single dfss_ connection key. On any other stack,
post events to our API.
Verify before you spend
Place a test order, then check the Inspector for a delivered
order_created. On OpenAI's side, conversions become
visible in ChatGPT Ads reporting within 24 to 48 hours.
OAIQ pixel alone, your own integration, or a managed connector?
Three routes reach the same Conversions API. They differ in what you have to build and maintain, and in whether ChatGPT Ads is the only destination.
The OAIQ pixel alone
OpenAI's official snippet, quick to install, and enough to get started: you will see conversions. It shares the limits of every browser pixel: ad-blockers, cookie restrictions, no server-side backup.
Your own Conversions API integration
Post to bzr.openai.com/v1/events yourself. Full
control, and you build and maintain the event mapping, the
deduplication, the retries and the consent gating on your own.
DataFirefly
A managed connector: one key, deduplication and consent gating built in. ChatGPT Ads plus Meta CAPI, GA4, TikTok, Pinterest, Google Ads and Microsoft Advertising from the same event, EU-hosted.
When another route fits better. For a first test campaign, the OAIQ pixel alone is a perfectly sound starting point: install the snippet and you will see conversions. Our value begins where reliability starts to matter: ad-blockers, Safari's cookie limits, deduplication, per-destination monitoring, and one integration feeding seven destinations instead of one more pixel to babysit. See also our server-side tagging versus server-side tracking comparison.
ChatGPT Ads tracking for every e-commerce platform
PrestaShop
A native module that sends the full funnel to ChatGPT Ads, with deduplication and consent handling built in.
WooCommerce
A WordPress plugin with a retry queue, an Activity panel and HPOS support, delivering purchases server-side to OpenAI.
Shopware 6
A Shopware plugin covering the same funnel, connected with the same single key.
Shopify
Shopify's order webhooks, subscribed in minutes with the same single key. Nothing to add to the theme.
A headless front-end or a custom stack? Post your events to our API and the dispatcher handles ChatGPT Ads and every other destination the same way. Tell us about your setup.
ChatGPT Ads included in every plan
One subscription covers your whole account and all its destinations: ChatGPT Ads is not a paid add-on. Move up a tier for more sites and more monthly events.
Swipe to see all four plans
Free
Free while you stay under the monthly allowance: nothing breaks if you go over.
Starter
For a single store getting server-side tracking in place.
Billed €390 per year: 12 months commitment, no pro-rata refund.
Growth
For merchants and small agencies running up to five sites.
Billed €1 190 per year: 12 months commitment, no pro-rata refund.
Scale
For agencies and portfolios managing up to twenty stores at higher volume.
Billed €3 490 per year: 12 months commitment, no pro-rata refund.
Just want to try the connection first? The free plan lets you send events and see them land before you subscribe.
Sending data to OpenAI, under European rules
Server-side tracking moves where the request comes from. It does not move you outside the GDPR: so we built the consent checks in rather than around.
Events are processed in the EU before they reach OpenAI.
Nothing fires client-side without marketing consent, and the server re-checks.
Your ChatGPT Ads key is encrypted at rest and never sent to the browser or the store.
Retryable delivery failures are replayed automatically, and every event's status per destination is visible in the Inspector.
A data processing agreement covering this flow is on our DPA page.
Tracked in real time on our public status page, in line with our SLA.
Frequently asked questions: ChatGPT Ads
What is advertising in ChatGPT?
Advertising opened in ChatGPT on 24 August 2026 in 31 European markets, including France. Ads are shown only on Free and Go accounts. In Europe, targeting is contextual: the topic of the conversation, approximate location and device type. It does not use conversation history or memory.
Do I still need to install the OAIQ pixel?
Yes. The OAIQ pixel (oaiq.min.js) captures the oppref URL parameter from the ad click and stores it in a first-party __oppref cookie valid for 720 hours: that browser signal is what ties a later conversion back to the ad. Our server-side events share an event ID with the pixel, so OpenAI deduplicates the two and counts each conversion once. Running both is the setup OpenAI itself presents as more reliable than the pixel alone.
How does deduplication work?
Each conversion carries a shared event ID, sent by both the OAIQ pixel in the browser and our server-side event to the Conversions API. OpenAI matches the two on that ID and counts the conversion once. If the pixel is blocked, the server event still arrives and the conversion is recorded: that is the whole point of running both.
Which events are sent to ChatGPT Ads?
The standard events of the ChatGPT Ads Conversions API: page_viewed, contents_viewed, items_added, checkout_started, order_created, lead_created, registration_completed, subscription_created, trial_started and appointment_scheduled. Amounts are converted to minor units (cents) as the API requires.
Does server-side tracking bypass the consent banner?
No, never. Server-side tracking does not remove the need for consent. Our connectors gate both the browser layer and the server layer on marketing consent, and the dispatcher applies a second check before any event leaves for OpenAI. Server-side is a reliability and data-quality mechanism, not a way around a consent banner.
When do conversions appear in ChatGPT Ads?
OpenAI shows conversions within 24 to 48 hours. That delay is also why measurement should be in place before your first campaign: an oCPC campaign optimises on a single standard event, locked when the campaign is created, so that event needs to be arriving reliably before you spend.
ChatGPT and OpenAI are trademarks of OpenAI. DataFirefly is not affiliated with OpenAI. Product names are used to describe interoperability.
Be measurable before your first ChatGPT Ads campaign
Send the complete, deduplicated funnel to the ChatGPT Ads Conversions API: consent-aware, EU-hosted, with Meta CAPI, GA4, TikTok, Pinterest, Google Ads and Microsoft Advertising from the same event.