# How to Measure AI Search Traffic in GA4 https://www.winstondigitalmarketing.com/playbooks/how-to-measure-ai-search-traffic-ga4/ // playbook / geo # How to measure AI search traffic in GA4. ChatGPT, Perplexity, and Gemini are sending you visitors right now, and GA4 is filing most of them under Referral where they vanish into the noise. Here is how to pull AI search traffic into its own channel, the exact hostnames to match, why the count will always be lower than the real influence, and what to track alongside it so you see the citations the clicks miss. // reading time 11 minutes · // last updated June 14, 2026 · // author John Morabito GA4 has had a native AI Assistant channel since 13 May 2026, rolled out broadly by 7 June, so AI sessions no longer sit in Referral by default. It undercounts. The documented list covers ChatGPT, Gemini, Deepseek, Copilot and Grok, which leaves Perplexity in Referral. Google's own AI Overviews are never labelled as AI at all: those clicks land in Organic Search when they carry a google.com referrer and in Direct when they do not, and in practice a great deal of it shows up as Direct. Every other no-referrer session lands in Direct too. So read the built-in channel as a floor, build a custom channel group alongside it for the assistants Google does not classify, and accept that the AI Overviews slice cannot be separated out at all, which is the case for pairing all of it with citation-share tracking. ## Why GA4 hides AI search traffic by default. GA4's default channel grouping was built for a web where traffic came from search engines, social platforms, email, and direct visits. The AI assistants do not fit any of those buckets cleanly. A click from a ChatGPT answer arrives as a referral from chatgpt.com, so GA4 quietly drops it into the generic Referral channel next to forum links and newsletter footers. A click from a Gemini answer can land in Organic Search because the host is a google.com subdomain. The traffic is there. It is just smeared across two channels with no label that says "an AI sent this person." Google shipped that native channel on 13 May 2026 and it reached most properties by 7 June. It is on by default, it needs no configuration, and it tags qualifying sessions with a medium of `ai-assistant`. It is also incomplete, which is why a custom channel group is still worth building next to it rather than instead of it. The gap that cannot be closed by any channel rule is Google's own AI Overviews, because those clicks arrive either as ordinary organic or with no referrer at all, and nothing distinguishes them from a normal Google click. ## The AI referral hostnames to match. This is the core set as of mid-2026. Keep it in one place and review it quarterly, because the assistants rename and add domains constantly. Engine Referral host(s) Lands in GA4 as ChatGPT chatgpt.com, chat.openai.com Referral Perplexity perplexity.ai Referral Gemini gemini.google.com Organic Search or Referral Microsoft Copilot copilot.microsoft.com Referral Claude claude.ai Referral Google AI Overviews (none distinct) Organic Search, indistinguishable AI Overviews are the one you cannot solve in GA4. A click from inside an AI Overview arrives under google with the ordinary organic medium and carries no hostname that separates it from a normal blue-link click. GA4 alone cannot split AI Overview traffic out, which is one more reason the referral count runs low. ## Build the custom channel group. In GA4, this lives under Admin, then Data display, then Channel groups. Create a new group (cloning the default is the safe way to keep everything else intact) and add one channel above the existing rules so it claims the traffic first. - **Name the channel** AI Referral. - **Set the condition** to Source, then "matches regex," and use a single pattern that covers the host list: chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai . - **Order it first,** above Organic Search and Referral, so a Gemini session gets claimed as AI Referral before the Organic Search rule can grab it. - **Save, then wait.** Channel groups apply going forward and to most historical reports, but give it 24 to 48 hours before you trust the comparison. If you would rather not touch the channel group, the lighter version is an Exploration with a session-source filter for the same hosts, or a Looker Studio page that does the regex match. The channel group is cleaner because every standard report inherits it. **// the regex caveat** Escape the dots in your pattern. chatgpt.com without the backslash matches "chatgptXcom" too, which is harmless here but a bad habit that bites you on broader rules. And test the pattern against a few weeks of Referral data before you rely on it, because a host you typed wrong fails silently and you will think the AI traffic is zero. ## Why the number will always undercount. GA4 counts a session only when someone clicks through to your site. The entire purpose of an AI answer is to resolve the question in place, with no click. The engine reads your page, lifts your sentence, names your brand in the answer, and the user leaves satisfied without ever visiting. GA4 records nothing, because nothing was visited. So your AI Referral channel measures the slice of AI influence that converted into a click, while the larger slice (the citations and brand mentions that shaped the answer itself) stays invisible to any clicks-only tool. Watch the referral count as a trend line for the AI traffic that landed. It will not tell you how visible you are in AI search. And even the clicks that do happen often land in Direct rather than your AI channel, because most assistants pass no referrer, one of the reasons [your organic decline is partly a measurement problem](/playbooks/organic-traffic-isnt-dying-your-measurement-is/). Measuring the value that survives when the click does not is the whole subject of our [zero-click search strategy for 2026](/playbooks/zero-click-search-strategy/), and the fuller case for why clicks-based analytics is structurally blind to AI, and what to measure instead, is in [why you can't see AI search in your analytics](/playbooks/why-you-cant-see-ai-traffic-in-analytics/). Paid media has the same offline blind spot, and one clean fix for attributing walk-in and cross-device sales to a campaign is a coded offer, covered in [using promo codes to fix paid media attribution](/playbooks/promo-codes-paid-media-attribution/). ## What to pair it with. Because GA4 only sees clicks, the referral channel is half a dashboard. The other half is [citation share](/playbooks/citation-share-replaces-rankings/), the metric that measures how often the engines actually cite your domain for a fixed set of prompts, click or no click. The two read together: GA4 tells you the AI traffic that landed, citation-share tracking tells you the AI visibility that produced it. If the reason you are here is that AI Overviews cut your clicks while impressions held steady, the full diagnosis-and-recovery path is in [recovering traffic after AI Overviews cut your clicks](/playbooks/ai-overviews-traffic-recovery/). To stand the second half up, you run a fixed prompt set against each engine on a schedule and record who gets named. That instrumentation is the whole job in [how to build an AI visibility dashboard](/playbooks/how-to-build-an-ai-visibility-dashboard/), and if you would rather buy than build, the honest tradeoffs between the off-the-shelf options are in [the best tools to track AI citations](/playbooks/best-ai-citation-tracking-tools/). Either way, the GA4 channel and the citation tracker are the two halves of a real generative-engine measurement setup, which is the foundation under everything in our [generative engine optimization service](/services/generative-engine-optimization/). ## The 20-minute setup. - **Clone the default channel group** in GA4 Admin so you keep a safe fallback. - **Add the AI Referral channel** with the source regex above, ordered first. - **Validate** against a few weeks of Referral data to confirm the hosts match. - **Build one report or Exploration** that trends AI Referral sessions, engaged sessions, and conversions over time. - **Stand up citation-share tracking** so you see the influence the clicks miss. - **Revisit the host list quarterly,** because the engines keep changing domains. ## Frequently asked questions. ### How do you measure AI search traffic in GA4? GA4 has had a native AI Assistant channel since 13 May 2026, rolled out broadly by 7 June, so AI sessions no longer sit in Referral by default. It undercounts. The documented list covers ChatGPT, Gemini, Deepseek, Copilot and Grok, which leaves Perplexity in Referral. Google's own AI Overviews are never labelled as AI at all: those clicks land in Organic Search when they carry a google.com referrer and in Direct when they do not, and in practice a great deal of it shows up as Direct. Every other no-referrer session lands in Direct too. So read the built-in channel as a floor, build a custom channel group alongside it for the assistants Google does not classify, and accept that the AI Overviews slice cannot be separated out at all, which is the case for pairing all of it with citation-share tracking. ### What are the AI search referral hostnames to track in GA4? The core set as of mid-2026 is chatgpt.com and chat.openai.com for ChatGPT, perplexity.ai for Perplexity, gemini.google.com for Gemini, copilot.microsoft.com for Microsoft Copilot, and claude.ai for Claude. AI Overviews are the hard case: those clicks arrive under google with the normal Organic Search medium and carry no hostname that separates them from a blue-link click, so GA4 alone cannot isolate AI Overview traffic. Keep the host list in one place and review it quarterly, because the assistants add and rename domains often. ### Why does GA4 undercount AI search traffic? GA4 only counts a session when someone clicks through to your site, and the entire point of an AI answer is to resolve the question in place without a click. The engine can read your page, lift your sentence, name your brand, and send the user away satisfied, and GA4 records nothing because no visit happened. So the referral number is a floor. It tells you the AI traffic that converted into a click, while the larger influence (the citations and mentions that shaped the answer) stays invisible to a clicks-only tool. ## Want AI search measured properly? Our GEO engagements stand up both halves of the dashboard: the GA4 channel for the clicks and citation-share tracking for the visibility the clicks miss, so you stop arguing about whether AI search matters and start watching the number move. [See the GEO service →](/services/generative-engine-optimization/) [Start with a free audit →](/audit/)