Growth marketer operator · San Jose, CA | ZuAI: 10K → 2M users at $0.02 CAC | $300k/mo ad spend managed
Ar.Bhavesh Pro
sep 2, 2026 chatgpt adspaid ads

ChatGPT Ads conversion tracking: the OAIQ pixel, image tag and Conversions API

how to wire up ChatGPT Ads tracking properly, and why getting it wrong degrades delivery rather than just breaking your dashboard.

the short version: ChatGPT Ads has three ways to report conversions and they all feed one Pixel ID. set this up before you create a campaign, not after, because the conversion objective needs it to exist first and broken tracking actively harms delivery.

Why this comes first

with most ad platforms, bad tracking means bad reporting. you still get your clicks, you just cannot tell what they did.

under ChatGPT Ads’ conversion objective it is worse than that. delivery is optimised toward the conversion signals you send, so if those signals are missing, wrong or delayed, the system optimises against bad data and your spend goes to the wrong people. the dashboard being wrong is the least of it.

that is why every piece of advice here is “do it before you launch”.

The three paths

all three report to the same Pixel ID from Ads Manager, and you can run more than one.

The JavaScript pixel. the snippet goes inside the <head> of every page, initialises with your Pixel ID, and automatically fires a page_viewed event. then on the pages where something meaningful happens, you add explicit calls:

oaiq("measure", "purchase", { value: 49.00, currency: "USD" });

this is the fastest to install and the one most people start with.

The image tag. a no-JavaScript fallback for places where you cannot run a script. useful for email confirmations and some checkout flows where script injection is restricted.

The Conversions API. server side. this is the one that survives ad blockers, browser privacy changes and users who close the tab before the pixel fires. it is more work and it is the version I would push any serious advertiser toward, because browser-side tracking loses more events every year.

The mistake I made

I installed the pixel, saw page_viewed firing, and assumed I was done.

page_viewed fires automatically. your actual conversion events do not. they only exist if you add the measure calls yourself, on the specific pages where the action completes. it is easy to have a green-looking pixel and zero conversion data, and easy to not notice for a week.

check the actual event, not the pixel. fire a real test conversion and confirm it appears in Ads Manager before you spend money against it.

Getting the events right

pick a small number of events that map to real business outcomes and use them consistently. a signup, a trial start, a purchase. resist the urge to instrument twenty micro-events, because you will end up optimising toward whichever one is easiest to trigger, and the easiest event to trigger is rarely the one that makes money.

send a value where one exists. optimising toward “a conversion” treats a ₹50 order and a ₹5,000 order identically, which is only correct if your product has one price.

What about apps

the Conversions API defines app_installed and app_opened with a mobile app action source. but during the self-serve beta, the data sources in Ads Manager listed Web, iOS and Android with only Web actually selectable.

so app install campaigns are not straightforwardly available yet, whatever the API reference implies. check your own account before you plan around them, and read ChatGPT Ads for app installs for what actually works today.

Before you spend

three checks, in order. the pixel is in the head of every page. a real conversion event fires and appears in Ads Manager. the value you are sending matches what you actually earn.

then work out what you can afford to pay. the LTV to CAC and payback calculator tells you both whether a user is worth more than they cost and how long your cash is tied up before you get it back, which is the number that kills companies with otherwise healthy ratios.

the rest of the paid discipline is in the paid ads playbook, and the full library covers the fifteen other channels.

Sources: pixel behaviour, event syntax and the three reporting paths from OpenAI’s conversion-optimized campaigns documentation and Choice OMG’s 2026 field guide.

Want this applied to your startup?

the breakdown call is free. bring one real growth problem, leave with the fix.

Let's talk Growth