The ChatGPT Ads pixel: three ways to have it installed and measure nothing

If you have started advertising inside ChatGPT, there is one thing worth checking before you look at a single number: that measurement is actually working. That is not as obvious as it sounds. OpenAI's measurement pixel can be installed, load without a single error on screen, and count nothing at all.

We are saying this because it happened to us. We installed that pixel on our own site and it took an afternoon to find three traps that appear in no guide, raise no warning, and leave a campaign spending money without knowing what works. Here are all three, explained so anyone can check them.

Trap 1: you install it, and it never reports visits

With almost every measurement system you know (Google's, Meta's), you paste the snippet into your site and from then on every visit is recorded by itself. That is what everyone assumes.

OpenAI's does not work that way. The code loads, sits ready, and waits for your site to explicitly tell it "someone just arrived". If nobody tells it, absolutely nothing happens: the page works normally, there is no error, and the platform never learns that a single person came in.

The outcome is the worst possible one, because it is invisible: you pay for the clicks, people reach your site, and your reports are empty or nearly so. It is easy to conclude the ad does not work when the truth is you are not measuring it.

Trap 2: it reports, but a missing field means it does not count

Suppose your site does report visits. There is still one detail. That signal has to carry a field stating what kind of content it is. Without it, the signal leaves your site, travels to OpenAI, arrives correctly, and is not recorded.

Notice how awkward that is: in your browser you would see the request going out and coming back fine. Everything looks right. It simply does not count on the other side. We only found it by comparing what we sent with what later showed up in the platform.

Trap 3: your own site blocks it, silently

Many modern sites carry a list of which external providers are allowed to load code. It is a security measure and having one is good. The problem is that if OpenAI is not on that list, the browser blocks the whole pixel and tells nobody.

There is no error message, the page looks perfect, and whoever installed the tracking walks away believing it is done. This is more common than you would think on stores built with the big platforms, which often ship that list preconfigured.

And it affects two separate things: the code that loads the pixel, and the sending of the data. You have to allow both, not one.

The other three things worth checking

That you do not have two pixels at once

This happens when someone installs it by hand and then it gets installed again through a tag manager. Every sale is counted twice, your reports show double what happened, and if you let the platform set bids automatically it will do so on a false number.

That you record more than visits

Counting visits tells you who arrives, not who buys. If you do not tell the platform when someone leaves their email, starts checkout or buys, it cannot learn who to show your ad to: it will chase cheap clicks instead of customers. And one detail that costs money: only OpenAI's seven standard event names count as a goal. A made-up name is received, but cannot be optimised for.

That purchases are also sent from your server

Everything above happens in your customer's browser, which is a fragile place: ad blockers, people who decline cookies, browsers that limit tracking. The way not to lose those sales is for your server to send the purchase on its own, alongside the browser. It is the half of measurement nobody teaches, and the one that saves the conversions the browser loses.

How to check it yourself, in a minute

1. Open your site in the browser and open the developer tools (F12 on most).
2. Go to the network tab and reload the page.
3. Look for requests to OpenAI's measurement domain. If none appear on load, the visit signal is not being sent (trap 1) or something is blocking it (trap 3).
4. If they do appear, perform the action that matters to you (leave an email, start checkout) and see whether another request appears. If it does not, you are not recording conversions.
5. Compare with what you see in OpenAI's panel a few minutes later. If it leaves your site and never shows up there, suspect trap 2.

If you would rather not do it by hand, our free checker runs these checks for you: you enter your address and it tells you what is right, what is wrong, and what cannot be known from outside. No account, no card, and it changes nothing on your site.

What to remember

• The ChatGPT Ads pixel does not report visits on its own: you have to ask it to, explicitly.
• That signal needs a content-type field, or it arrives and is not recorded.
• If your site has an allowed-providers list and OpenAI is not on it, the browser blocks it without a word.
• Two pixels at once count every sale twice and corrupt automated bidding.
• With no conversion events, the campaign optimises for clicks, not customers, and only the seven standard names count.
• Send purchases from your server too, or you lose everyone using a blocker or declining cookies.