{"id":141,"date":"2026-06-11T06:53:46","date_gmt":"2026-06-11T06:53:46","guid":{"rendered":"https:\/\/maxaeo.ai\/blog\/?p=141"},"modified":"2026-06-11T07:18:36","modified_gmt":"2026-06-11T07:18:36","slug":"ai-referral-traffic-ga4","status":"publish","type":"post","link":"https:\/\/maxaeo.ai\/blog\/ai-referral-traffic-ga4\/","title":{"rendered":"How to Track AI Referral Traffic in GA4 (ChatGPT, Perplexity & More)"},"content":{"rendered":"

AI referral traffic in GA4 is the set of sessions that start when someone clicks a link to your site inside an AI answer<\/strong> \u2014 in ChatGPT, Perplexity, Gemini, Copilot, Claude, or Grok. By default, GA4 scatters those sessions across Referral, Direct, and Organic Search, so most teams underreport the exact channel they are being asked to defend in budget meetings.<\/p>\n

This guide fixes that: a copy-paste regex and custom channel group that surfaces every known AI source (and applies retroactively), the real limits of GA4's new native AI Assistant channel, a workaround playbook for the "dark" AI traffic GA4 cannot see, benchmarks so you know whether your numbers are good, and \u2014 the part most tracking guides skip \u2014 a method for pairing GA4 click data with AI mention-rate data<\/strong>, so you can tell whether AI visibility is actually turning into pipeline.<\/p>\n

What Is AI Referral Traffic in GA4?<\/h2>\n

AI referral traffic is website traffic that arrives from an AI assistant or AI search engine. GA4 records it when the visitor's browser passes a referrer (such as chatgpt.com<\/code>) or when the AI platform appends UTM parameters to the link. No referrer, no attribution \u2014 the visit falls into Direct.<\/p>\n

Each platform shows up under a predictable session source<\/strong>. These are the values you will filter on throughout this guide:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Platform<\/th>\nTypical session source in GA4<\/th>\nWhere it lands by default<\/th>\n<\/tr>\n<\/thead>\n
ChatGPT<\/td>\nchatgpt.com<\/code> (legacy: chat.openai.com<\/code>)<\/td>\nReferral, or Direct from apps<\/td>\n<\/tr>\n
Perplexity<\/td>\nperplexity.ai<\/code><\/td>\nReferral<\/td>\n<\/tr>\n
Gemini<\/td>\ngemini.google.com<\/code> (legacy: bard.google.com<\/code>)<\/td>\nReferral<\/td>\n<\/tr>\n
Microsoft Copilot<\/td>\ncopilot.microsoft.com<\/code>, edgeservices.bing.com<\/code><\/td>\nReferral, or Direct from Windows app<\/td>\n<\/tr>\n
Claude<\/td>\nclaude.ai<\/code><\/td>\nReferral<\/td>\n<\/tr>\n
Grok<\/td>\ngrok.com<\/code>, x.ai<\/code><\/td>\nReferral<\/td>\n<\/tr>\n
Google AI Overviews \/ AI Mode<\/td>\ngoogle<\/code><\/td>\nOrganic Search \u2014 not separable<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

That last row matters: clicks from AI Overviews and AI Mode carry a standard Google referrer. Google's own documentation<\/a> confirms they are reported inside the "Web" search type and ordinary organic traffic, with no separate click breakout. Do not promise stakeholders an "AI Overviews traffic" number \u2014 it does not exist in GA4.<\/p>\n

Where Does AI Traffic Hide in GA4 by Default?<\/h2>\n

By default, AI visits split across three buckets: Referral (browser clicks with a referrer), Direct (apps and clients that strip the referrer), and Organic Search (all AI Overviews and AI Mode clicks).<\/strong> Until you reclassify the first bucket, your "Referral" line quietly absorbs your fastest-growing channel.<\/p>\n

Google has started closing part of this gap. In May 2026, GA4 began auto-classifying some AI visits under a new "AI Assistant" channel<\/strong> with medium ai-assistant<\/code>, as reported by MarTech<\/a>. Here is how the native channel compares with the custom channel group this guide builds:<\/p>\n\n\n\n\n\n\n\n\n
<\/th>\nNative AI Assistant channel<\/th>\nCustom AI Referral channel<\/th>\n<\/tr>\n<\/thead>\n
Confirmed coverage<\/strong><\/td>\nChatGPT, Gemini, Claude; no full referrer list published<\/td>\nEvery source in your regex \u2014 15+ platforms<\/td>\n<\/tr>\n
Historical data<\/strong><\/td>\nNew data from the May 2026 rollout onward (default channel assignments are set at processing time)<\/td>\nRetroactive<\/strong> \u2014 reclassifies your history at report time<\/td>\n<\/tr>\n
Dark traffic (no referrer)<\/strong><\/td>\nMissed<\/td>\nMissed too \u2014 recover via UTMs and heuristics (below)<\/td>\n<\/tr>\n
Who controls updates<\/strong><\/td>\nGoogle, on its schedule<\/td>\nYou, the day a new assistant launches<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Treat the native channel as a floor, not a finish line: Perplexity, Copilot, and Grok coverage is unverified, and anything arriving without a referrer still lands in Direct. The custom channel group remains the reliable way to capture the full platform list.<\/p>\n

\"GA4<\/figure>\n

How to Set Up a GA4 Custom Channel Group for AI Traffic (Step by Step)<\/h2>\n

The permanent fix is a custom channel group: one regex condition on session source, evaluated above Referral, that groups every AI platform into a single "AI Referral" channel.<\/strong> It takes about 15 minutes and, unlike default channel group edits, custom channel groups apply retroactively \u2014 your historical AI sessions get reclassified too.<\/p>\n

The copy-paste regex<\/h3>\n

Use this pattern as your source condition. It covers the eight platforms above plus the long tail (DeepSeek, Meta AI, Mistral's Le Chat, You.com, Poe):<\/p>\n

.*(chatgpt\\.com|chat\\.openai\\.com|perplexity\\.ai|claude\\.ai|gemini\\.google\\.com|bard\\.google\\.com|copilot\\.microsoft\\.com|edgeservices\\.bing\\.com|grok\\.com|x\\.ai|deepseek\\.com|meta\\.ai|chat\\.mistral\\.ai|you\\.com|poe\\.com).*\n<\/code><\/pre>\n
Four notes before you paste:<\/p>\n