AI traffic is invisible in GA4 by default. When someone clicks a link inside ChatGPT, Perplexity or Gemini, GA4 files that visit under « Referral » or « Direct », drowned among dozens of other sources: no « AI » channel exists natively. To track it, you have to create a custom channel group that bundles the assistants' referral domains — chatgpt.com, perplexity.ai, gemini.google.com and their variants — then build a dedicated exploration report and attach your conversions to it. Without this setup, you steer your GEO strategy blind: you can't tell whether your optimizations generate clicks, leads or revenue. This guide covers GA4's attribution mechanics, the up-to-date list of AI referrals, the step-by-step channel and report build, conversion measurement, and the blind spots to know before reading your numbers.
Why AI traffic is invisible
GA4 has no native « AI » channel. Traffic sent by ChatGPT, Perplexity or Gemini is scattered across « Referral », « Organic Search » and above all « Direct », with no grouping or dedicated label. The result: you don't see it.
The cause is mechanical. GA4 attributes a source from the HTTP referer header passed by the browser, then applies channel-classification rules. AI assistants blur that signal in two ways. First, some propagate a referer (perplexity.ai, gemini.google.com) that GA4 files under « Referral », buried among all your other referrers. Second, many clicks come from the native app or a context that sends no referer: GA4 then has nothing to attribute and flips the visit to « Direct ».
The problem is strategic. GEO is now an acquisition channel in its own right — ChatGPT exceeds 900 million weekly users, and more than 50% of Google queries trigger an AI Overview. Without dedicated measurement, you can't connect your optimizations to clicks, leads or revenue. You steer blind a channel that weighs more every month.
GA4 has no AI channel. You must create it manually via a custom channel group that bundles the assistants' referral domains. Without it, your GEO traffic is diluted across « Referral » and « Direct », and your AI visibility strategy stays unmeasurable.
The list of AI referrals to track
To isolate AI traffic, you first need to know the referral domains the assistants pass. Those are what will serve as the grouping rule in GA4.
Here are the domains to watch, sorted by assistant. This list evolves: vendors add subdomains and variants with each release. Check your referral reports each quarter to keep it current.
| Assistant | Referral domains | Default GA4 behavior |
|---|---|---|
| ChatGPT | chatgpt.com, chat.openai.com | Referral or Direct depending on context |
| Perplexity | perplexity.ai, www.perplexity.ai | Referral (propagated referer) |
| Gemini | gemini.google.com | Referral, sometimes Organic Google |
| Copilot | copilot.microsoft.com, bing.com/chat | Referral or Organic Bing |
| Claude | claude.ai | Referral (propagated referer) |
| Others | you.com, poe.com, grok.com | Referral |
Note the key nuance: these domains only cover clicked traffic. AI citations that generate no click — zero-click answers, mentions in an AI Overview with no visit — will never appear in GA4. To measure that visibility, traffic tracking isn't enough: you need citation and AI share of voice tracking in parallel.
Create the custom GA4 channel
The grouping is created via a custom channel group in GA4 admin. The operation takes a few minutes and is fully reversible.
In GA4, click Admin (gear icon, bottom left), then, under the Property column, « Channel groups ». You'll see the default group, which can't be edited. Click « Create a channel group ».
Name the group « Acquisition with AI », for example. Inside it, add a new channel named « AI Assistants » and place it at the top of the list: GA4 applies rules in order, and the first matching channel wins.
For the « AI Assistants » channel, set the condition: « Source » matches one of the regular expressions bundling your domains, for example chatgpt.com|openai.com|perplexity.ai|gemini.google.com|copilot.microsoft.com|claude.ai. Use the « matches regex » operator.
Save. Make sure « AI Assistants » ranks above « Referral » and « Organic Search », otherwise those channels will capture the traffic first. Priority order governs the whole measurement.
The custom group only applies to data collected from its creation, not retroactively across all reports. Allow 24 to 48 hours before seeing the first consolidated volumes in the new channel.
Once this channel is in place, your standard acquisition reports will show « AI Assistants » as soon as you select the custom channel group in the dimension selector. That's the baseline. For fine-grained analysis, move to exploration.
To move faster, start from ready-made templates: our GEO Audit Templates Pack includes the up-to-date AI referral regex, the exploration report structure and the interpretation grid. Just paste your domains and start collecting.
Build the exploration report
The free-form exploration lets you cross AI traffic with landing pages and conversions, something standard reports don't do well. That's where the data becomes actionable.
Go to « Explore » then « Free form ». Import the following dimensions and metrics, then build the table.
| Element | To use | Why |
|---|---|---|
| Primary dimension | Default channel group (custom) | Isolates the « AI Assistants » row |
| Secondary dimension | Source / Landing page | Identifies which assistant and page convert |
| Metrics | Sessions, Users, Engagement | Volume and quality of AI traffic |
| Key metric | Conversions, Revenue | Connects GEO to revenue |
| Filter | Channel group = AI Assistants | Excludes all other traffic |
Apply a filter on the custom channel group to keep only « AI Assistants », add « Source » and « Landing page » as rows, and place sessions, engagement rate and conversions as values. You get a table that answers three questions: which assistants send you traffic, on which pages, and with what business result.
92% of AI Overview citations come from the top 10, but 47% involve positions 5 to 10. Your exploration report crossed with Search Console reveals which pages — even non-first ones — capture AI traffic, a valuable signal for prioritizing your optimizations.
Save this exploration and share it with your team. Compared month over month, it shows the real evolution of your AI channel. To go further and benchmark your performance against competitors, cross these volumes with an LLM competitive benchmark.
Measure AI-driven conversions
A session volume is useless without an attached conversion. The real business question is: how many leads or sales does this AI channel generate, and at what quality compared to the rest of your traffic?
In your exploration, add your conversion events (form submitted, meeting booked, purchase) as metrics, segmented by « Source ». You get a conversion rate per assistant. That's often where the surprise comes: AI traffic frequently converts better than average, because it arrives bottom-of-funnel, after the user has already gotten an answer and is looking to validate a choice or buy.
Three best practices to make this measurement reliable:
Verify that your value actions (lead, quote, purchase) are properly set as « key events » in GA4. Without that, the conversions column of your report will stay empty for the AI channel.
An AI conversion almost always points to a specific answer page — guide, comparison, product page. Identify these pages: they are your most-cited assets, to reinforce first.
AI traffic is often an intermediate touchpoint. Compare last-click attribution and data-driven attribution so you don't underestimate the assistants' real contribution to the journey.
To connect this measured traffic to the queries that actually trigger it inside the assistants, complement the analysis with ChatGPT mention tracking: you'll know not only how many visits arrive, but on which questions you're cited.
The blind spots of measurement
No GA4 tracking captures 100% of AI traffic. You have to read your numbers knowing three structural limits, or risk false conclusions.
Masked Direct traffic
When an assistant doesn't propagate a referer — click from the native app, answer with no tagged outbound link — GA4 classifies the visit as « Direct ». An irreducible share of your AI traffic stays invisible. An unexplained jump in « Direct » concurrent with a GEO campaign is often disguised AI traffic: cross-check with your high-citation-potential landing pages.
Zero-click
Most of GEO's value isn't measured in clicks. A brand cited in a ChatGPT answer gains awareness and authority without a single visit being recorded. Recall that off-site mentions correlate at 0.737 with AI citations, versus 0.266 for Domain Rating (Ahrefs analysis of 200,000 domains, Dec. 2025): the lever is presence, not just the click.
Low source overlap
Only 11% of domains are cited by both ChatGPT and AI Overviews. Tracking a single assistant gives a partial view. Your report must segment by source to reveal these gaps and guide platform-specific optimizations.
GA4 traffic tracking measures clicks, not visibility. Always combine it with citation and share-of-voice tracking to steer full GEO. « Direct » and zero-click hide a value your dashboard will never show.
Beyond clicks: citations and share of voice
GA4 answers « how many visitors do the AIs send me ». It doesn't answer « am I cited, and more than my competitors ». These two questions are complementary and require two distinct toolsets.
Traffic tracking tells you what flows down to your site. Citation and share-of-voice tracking tells you what happens upstream, inside the answers themselves — including all the invisible zero-click. Without the second, you optimize a funnel where you only see the exit.
To pick the right tooling for this measurement layer, compare the market solutions in our 2026 GEO tools comparison. The goal: a single dashboard combining measured traffic (GA4) and upstream visibility (citations + share of voice), to steer GEO end to end.
Our free GEO audit reveals where your AI traffic comes from, what you're leaving on the table and the priority optimizations to become a cited source.
Questions fréquentes
Why does ChatGPT traffic show up as Direct in GA4?+
Because ChatGPT does not always pass a referer header. When the user clicks from the native app or from an answer with no propagated referer, GA4 has no source to attribute and classifies the visit as « Direct ». Part of AI traffic therefore remains structurally invisible, even with a well-configured custom channel.
Do I need to create the channel in a new GA4 property?+
No. The custom channel group is created within an existing property, via Admin then Channel groups. It does not affect the default group and is reversible. Note: custom groups only apply to future data and to certain reports, not retroactively everywhere.
Which referral domains should I include for AI traffic?+
At minimum chatgpt.com, chat.openai.com, perplexity.ai, gemini.google.com, copilot.microsoft.com and claude.ai. Add mobile variants and subdomains. The list evolves: check your referral reports every quarter to capture new assistant domains.
Does UTM tracking work for AI traffic?+
Not directly, because you don't control the links generated by AI. You cannot tag a ChatGPT answer with UTM parameters. The only reliable method remains grouping by referral domain in a custom channel, complemented by an analysis of landing pages with strong AI signal.
How long before I see data in my AI channel?+
The custom channel group only applies to data collected after its creation. Allow 24 to 48 hours to see the first consolidated volumes, and several weeks before you have enough history to identify reliable trends per assistant and per page.
