The platform reports impressions, clicks, click-through rate and cost. Everything past the click, conversions and revenue, comes from your own analytics through static UTMs and your pixel or Conversions API. But there is a catch that makes ChatGPT harder to measure than any other channel: a large share of AI-assistant referrals arrive with no referrer and get logged as Direct, so your analytics shows a fraction of the traffic you actually earned. Measuring this channel well means correcting for what it hides.
What the platform shows you
In-platform reporting is deliberately simple: impressions, clicks, CTR, CPM and spend. It tells you whether your ads are serving and being clicked, not whether they made money. For that you connect the click to your own analytics, which is why the tracking setup in the conversion-tracking guide is the foundation everything else sits on.
The part of the journey search never saw
The reason this channel is worth measuring properly is that it reaches buyers where search never could. According to OpenAI's own breakdown of the shopping journey, only about a third of buying activity is the evaluation-and-purchase moment that classic search was built to capture. The other two-thirds is problem framing, product discovery and comparison, with product discovery the single largest slice at roughly a third of all activity, and comparison and single-product evaluation each around a fifth to a quarter.
The public figures point the same way. OpenAI has said that roughly 83% of the queries that trigger ads inside ChatGPT would never have triggered a Google Shopping ad, that a large share of ad moments are purely research-oriented, and that many users who start a conversation with no commercial intent develop buying signals before it ends (reported by PYMNTS). Keyword search only ever monetised the last stretch of the journey. ChatGPT reaches the problem-framing, discovery and comparison stages that come before it, which is why measuring it as if it were a bottom-of-funnel search channel undercounts what it actually does.
Static UTMs and naming
The platform accepts only static UTM parameters, written into each landing URL by hand. Turn that constraint into a discipline: one consistent convention across every ad, so a click can always be traced back to the campaign, ad group and ad that earned it. Inconsistent tags are the quiet way a channel looks like it is not working when really it is just not joinable.
Finding the AI traffic that hides
Even with perfect UTMs, you will under-count. Many AI assistants strip the referrer header, so the visit lands in Direct instead of an AI channel. Across a dataset of more than 440,000 visits, roughly 50 to 70% of AI-assistant referrals arrived with no referrer, and analytics platforms have been shown to under-count AI traffic by 30 to 40% even after adding their own AI channels. The practical correction is a gross-up, not a guess:
- +Recover the AI visits that do keep their referrer with custom channel rules for the main assistants.
- +Gross up from there: your true AI traffic is roughly the tracked count divided by 0.3 to 0.5.
- +Treat the analytics number as a floor, not a ceiling, and corroborate with landing-page and behavioural evidence.
This matters because the hidden traffic is the good traffic. AI-referred visitors arrive further along the decision and convert well above other sources, so under-counting them makes your best channel look like your weakest. Correcting for it is exactly the AI-attribution work we already do for organic visibility, now pointed at your paid results. When you want the full picture built and reported for you, that is part of the service.
