To track ChatGPT Ads in GA4: tag every ad destination URL with utm_source=chatgpt and utm_medium=cpc, build a one-rule custom channel group named ChatGPT Ads, mark your own conversion events, and know what the defaults do without you. Tagged paid clicks land in Paid Other (not Paid Search: chatgpt is not on Google's search-sites list). Organic ChatGPT clicks land in the AI Assistants channel GA4 rolled out from mid-May 2026. Untagged paid clicks blend into one of those two, unrecoverably. OpenAI reports its own conversions in Ads Manager and sends nothing to GA4.
- Tag:
utm_source=chatgpt&utm_medium=cpc&utm_campaign={campaign-slug}&utm_content={ad-variant} - Default channel for tagged paid: Paid Other, by Google's two-condition Paid Search rule
- Organic side: auto-tagged
utm_source=chatgpt.com, rewritten to mediumai-assistant, channel AI Assistants - Fix the pooling: one custom channel group rule: session source matches
chatgpt - Conversions: OpenAI's pixel reports to Ads Manager only; GA4 needs its own key events
- Crawlers and agents: invisible to web GA4; server-side collection only
Ask five guides what ChatGPT Ads traffic looks like in Google Analytics 4 and you will get five confident, mutually exclusive answers: it is Referral, it is Direct, it is Paid Search if you tag it, GA4 has a native integration, GA4 has nothing. We ran the top queries through the AI engines while researching this post and watched them cite sources that contradict each other on exactly those basics.
The contradictions have a simple cause: the ground truth changed, and most guides were right on the day they were written. Google shipped a dedicated AI Assistants channel in mid-May 2026 that rewrote where organic AI traffic lands, forward-only, so pre-May guides describe a world that no longer exists and post-May guides describe one that did not exist before. This post is the date-scoped version: every claim below is checked against Google's current published channel definitions and source-category list, OpenAI's current ads documentation, and our own shipped measurement tooling, with verification dates stated.
Every popular answer was right once. GA4 changed underneath them.
What ChatGPT traffic actually shows as in GA4
Five scenarios cover everything. Two of them are healthy, one is recoverable, and two are structural limits you design around.
The row that costs real money is the second one. An untagged paid click is not misclassified, it is unclassifiable: nothing distinguishes it from an organic visit once it leaves ChatGPT, because OpenAI's oppref click identifier rides the URL for OpenAI's own attribution and GA4 does not read it. Whatever you do with the rest of this guide, tag every paid destination URL first.
The canonical tagging setup
The convention we use and recommend, unchanged since May 2026: utm_source=chatgpt, utm_medium=cpc, plus utm_campaign, utm_content, and optionally utm_term for the context-hint cluster. The full field-by-field reasoning lives in our UTM guide for ChatGPT Ads; the short version is that cpc keeps the traffic in GA4's paid buckets and matches the convention your Google Ads and Bing Ads tagging already uses.
https://yoursite.com/landing?utm_source=chatgpt&utm_medium=cpc&utm_campaign=q3-launch&utm_content=headline-a&utm_term=cluster-1One correction to the claim you will find in most guides, including, until this post shipped, ours: this does not land in Paid Search. Google's Paid Search channel requires the medium to match its paid regex and the source to be on its published search-sites list. We downloaded that list on August 12, 2026 and checked all 820 rows: it contains no AI assistant domains at all. So chatgpt + cpc lands in Paid Other, which is still a cleanly paid bucket, just a shared one.
Give it its own channel in one rule
In Admin, under Data display, choose Channel groups, create a custom channel group, and add a channel named ChatGPT Ads with the rule: session source exactly matches chatgpt. Reorder it above Paid Other so it wins. If you also want the organic side named, add a second channel keyed on session source exactly matches chatgpt.com. Custom channel groups apply in standard reports and Explorations, so this is the one setup step that makes every later report readable.
The AI Assistants channel, and what Google does not document
From mid-May 2026, GA4 ships a default channel for AI-assistant traffic. Google's channel definitions describe it as traffic from sources like ChatGPT, Gemini, DeepSeek, Copilot, and Grok, and define it mechanically: the session lands there when the medium exactly matches ai-assistant, and GA4 itself sets that medium, with campaign (ai-assistant), when the referrer matches its list of AI assistants. Organic ChatGPT citation clicks, which arrive carrying the auto-appended utm_source=chatgpt.com, land here.
Two things Google does not publish, stated plainly because they matter operationally. First, the AI-assistant referrer list itself is unpublished, unlike the search-sites list, so you cannot audit which assistants are recognized. Second, the definition does not say whether the automatic rewrite can override manually set UTM parameters. We have found no documented answer either way, so this guide does not claim one. The deterministic posture: tag every paid URL, watch the paid channel and AI Assistants channel for leakage in either direction, and treat any tagged session that lands in AI Assistants as a signal to re-check, not as a mystery.
Conversions: OpenAI's loop and GA4's loop never touch
OpenAI's Measurement Pixel and Conversions API report conversions into OpenAI's Ads Manager: that is where campaign CPA, oCPC optimization, and OpenAI's own attribution live. Nothing in OpenAI's ads documentation sends any of it to GA4, and no native integration exists as of August 2026. GA4 sees a ChatGPT Ads conversion only the way it sees any conversion: your site fires an event, you mark it as a key event, and attribution flows from the session's UTMs.
Run both loops. Ads Manager conversions feed OpenAI's bidding; GA4 key events put ChatGPT Ads in the same reporting frame as every other channel, which is the comparison your budget decisions actually use. The stitching between the browser pixel and server-side events, the event_id deduplication key and the rest of the identifier plumbing, is its own topic: our four-identifier map covers it, including the exact error the popular community server tag throws when the dedup key is missing.
What web GA4 cannot see, and the server-side fix
Two classes of ChatGPT-related traffic never appear in a web GA4 property at all. AI crawlers (GPTBot, OAI-SearchBot, and peers) do not execute JavaScript, so no web tag ever fires for them. And an untagged paid click's oppref parameter, OpenAI's own click identifier, is invisible to GA4's channel logic even though it is sitting on the URL.
Both are addressable server-side. Our free, open-source AI Crawler Analytics template for server-side GTM classifies AI crawler, agent, and referral traffic into dedicated GA4 events, and as of its v1.1 release it reads oppref directly: a paid ChatGPT click with a stripped referrer and no UTMs, the exact click web GA4 cannot classify, arrives as an ai_referral_visit event with ai_medium=paid. It requires a GTM server container, which is a real prerequisite and not a footnote; if you run web-only GTM, the tagging discipline above is the part of this guide that applies to you.
Three reports that answer the actual questions
1. Is the channel driving traffic? (Acquisition, 2 minutes)
With the custom channel group applied, Reports, Acquisition, Traffic acquisition, switch the primary channel dimension to your custom group. ChatGPT Ads sits next to Paid Search and AI Assistants as a first-class row.
2. Which campaigns and creatives convert? (Exploration, 10 minutes)
Build a free-form Exploration with session source exactly chatgpt as a filter, dimensions session campaign and session manual ad content (your utm_campaign and utm_content), metrics sessions, key events, and session key event rate. That is the campaign-and-variant table Ads Manager cannot give you, because it reports OpenAI's conversions, not your GA4 key events.
3. Paid vs organic ChatGPT, one chart
Same Exploration pattern, filter session source matching regex ^chatgpt(\.com)?$, breakdown by session default channel group (or your custom group). The paid line and the AI Assistants line on one time series is the chart that answers whether ads are buying you reach you were not already earning, which is the question that decides the budget.
Frequently Asked Questions
#What does ChatGPT Ads traffic show up as in GA4?
It depends entirely on your tagging. A paid click tagged with the canonical utm_source=chatgpt and utm_medium=cpc reports as source chatgpt, medium cpc, default channel Paid Other. An untagged paid click arrives looking like organic ChatGPT traffic: if the referrer survives, GA4 rewrites the medium to ai-assistant and it lands in the AI Assistants channel; if the referrer is stripped, it lands in Direct. Organic ChatGPT citation clicks carry the auto-appended utm_source=chatgpt.com and land in AI Assistants. There is no scenario where GA4 identifies a paid ChatGPT click on its own.
#Does GA4 classify ChatGPT Ads as Paid Search?
No. GA4's Paid Search channel requires two conditions: a paid medium (cpc qualifies) AND a source on Google's published search-sites list. That list contains no AI assistant domains (we verified all 820 rows of Google's source-category list in August 2026: no chatgpt, no chatgpt.com, no perplexity, gemini, copilot, or claude). So utm_source=chatgpt with utm_medium=cpc lands in Paid Other. It is still cleanly separated as paid traffic, and a one-rule custom channel group keyed on session source matching chatgpt gives ChatGPT Ads its own named channel in every default report.
#What is the AI Assistants channel in GA4?
A default channel Google rolled out from mid-May 2026 for traffic arriving from AI assistants such as ChatGPT, Gemini, Copilot, Grok, and DeepSeek. Per Google's channel definitions, a session lands there when the medium exactly matches ai-assistant, and GA4 sets that medium itself (with campaign set to (ai-assistant)) when the referrer matches its list of AI assistants. The classification is forward-only: sessions from before the rollout keep their original Referral or Direct classification, which is why year-over-year AI-traffic comparisons in GA4 break at that boundary.
#Do ChatGPT ad clicks end up in the AI Assistants channel?
Tagged clicks should not: an explicit utm_medium=cpc places the session in paid channels. Untagged ad clicks can, because without your UTMs a paid click is indistinguishable from an organic one, and GA4's rewrite fires on the referrer. One honest caveat: Google documents when it sets the ai-assistant medium, but does not document whether that rewrite can override manually set UTM parameters, so the deterministic strategy is to tag every paid destination URL and monitor the split rather than assume.
#Does OpenAI send ChatGPT Ads conversions into GA4?
No. There is no OpenAI-to-GA4 integration anywhere in OpenAI's ads documentation. The Measurement Pixel and Conversions API report conversions into OpenAI's Ads Manager, which is a separate loop from GA4's event stream. To see ChatGPT Ads conversions in GA4 you mark your own key events and attribute them through your UTM tagging, exactly as you would for any other paid channel.
#How do I get ChatGPT Ads broken out as its own channel in GA4?
Build a custom channel group with one rule: session source matches chatgpt (or exactly chatgpt if you want to exclude the organic chatgpt.com source), condition it on a paid medium if you tag consistently, and name the channel ChatGPT Ads. Custom channel groups apply to standard Acquisition reports and Explorations. Without it, tagged ChatGPT Ads traffic pools in Paid Other alongside every other paid platform whose source is not on Google's search list.
#Can GA4 see AI crawlers and agents visiting my site?
No. GPTBot, ClaudeBot, PerplexityBot, and OAI-SearchBot do not execute JavaScript, so the GA4 web stream never records them (Vercel measured zero JavaScript executions across 500 million GPTBot fetches). Agent visits behave similarly. Seeing that traffic requires server-side collection: a server-side GTM setup can classify AI crawler, agent, and referral traffic into GA4 events, which is what our free open-source AI Crawler Analytics template does.
Related Reading
- How to Add UTM Codes to ChatGPT Ads
- ChatGPT Ads Conversion Tracking Is Real: What OpenAI's April 30 Privacy Policy Update Tells You About the Roadmap
- ChatGPT Ads Automatic Advanced Matching Turns On August 17
- How to Report on ChatGPT Ad Campaigns: A 2026 Measurement Stack
- How to install the ChatGPT Ads Measurement Pixel via Google Tag Manager
