Advertising in ChatGPT is new, and so is measuring it. OpenAI's pixel in the browser does not see everything: ad blockers and browser settings stop part of your conversions. The Conversions API sends the same conversion a second time, from your own server. OpenAI recognises the shared event ID, sees it is the same order and counts it once.
ChatGPT Ads is only just getting started. That is exactly when every conversion weighs heavily in what OpenAI learns about your campaign — and every conversion that never arrives steers your ads the wrong way.
Part of your conversions is blocked in the browser before the pixel sees them. You will not notice it in your revenue, but you will in your campaign: OpenAI optimises on numbers that are too low, and ads that perform well look like they do not.
The conversion goes out a second time, now from your own server, with the same event ID as the pixel. OpenAI deduplicates on pixel, event and ID: the first report counts, the second is ignored. There is never a double sale in your reports.
On a click from ChatGPT, OpenAI adds an identifier to your landing page. The pixel stores it in a cookie on your own domain and the server connection sends it along. Even when the order follows days later, it can still be linked to the right ad.
Fill in two fields and click enable. We do the installation in your own server container — you do not have to find, build or publish a tag yourself.
Rather have us do the whole setup, including the pixel in your browser container? Let us know.
Without your visitor's marketing consent, nothing goes to OpenAI. That is not a setting someone can forget, but how the connection works.
The conversion goes to OpenAI, with hashed details for matching. Your raw customer data never leaves your own server — only an irreversible hash of it goes along, exactly in the form OpenAI prescribes.
Nothing is sent. So you see fewer conversions in ChatGPT Ads than in your own checkout, because you only measure the visitors who consented. The difference is a decision, not a fault.
One detail worth knowing: OpenAI's pixel assumes consent as long as nobody says otherwise. Our server connection works the other way round: no demonstrable consent, nothing leaves. And if your visitor allows measurement but not personalised ads, we pass that along as an opt-out. Which status applies is decided by your own cookie banner — the connection works with every common banner, or use our own Consent Mode V2 Banner, free from Business.
Purchase, lead and account created are on by default. You choose what else goes along — a web shop usually wants the cart, a service provider the lead.
One condition: your events carry an event ID. If it is missing we do not send that event — better nothing than counted twice. Your dashboard shows whether your setup does this; if not, we help you add it. For a purchase the order value goes along, in the right currency.
No surcharge, no separate module. Like the Google Ads and Meta connections, this is simply part of the service.
No — keep it. The pixel and the server connection complement each other: the pixel stores the ChatGPT click identifier on your own domain, the server sends the conversion even when the browser blocks it. OpenAI recognises the shared event ID, sees it is the same conversion and counts it once — the first one to arrive wins.
A ChatGPT Ads account with a pixel, and a conversion key from that same account. Note: that is a separate key for the Conversions API, not the API key of your ad account. You enter both in your dashboard and click enable; we check the key and then install the connection in your own server container.
Because nothing is sent without marketing consent. You only see the visitors who consented. That is not a fault but a decision — and worth knowing before you compare the numbers.
Then we do not send that event. Without an ID OpenAI cannot tell that the pixel and the server are reporting the same order, and every conversion would count twice. Better nothing than double. Your dashboard shows whether your setup sends an ID; if not, we help you add one.
Purchase, lead or quote request, account created, checkout started, add to cart, product viewed and page view. Purchase, lead and account created are on by default. For a purchase the order value goes along, in the right currency.
Nowhere with us. The key goes into the settings of your own server container and that is the only place it lives.
Yes. They are four separate connections that all run through the same server container. You switch them on or off independently.
Fill in two fields, we do the installation. Deduplicated with the OpenAI pixel, behind a consent gate that only lets through what is allowed — included in every plan.
Start now