To track ChatGPT and AI referral traffic in GA4, build a custom channel group with a regex that matches the AI source domains, then reorder it above the Referral channel so AI sessions stop getting miscounted. It takes about five minutes, and it matters because AI traffic is small but converts near the top of every channel: ChatGPT referrals convert around 7.1 percent, second only to paid search, and Ahrefs measured AI search visitors converting at up to 23 times the rate of traditional organic. The catch is that between 35 and 70 percent of AI sessions arrive with no referrer and land in Direct, so even a clean setup undercounts. This post gives you the exact build and the honest limits.
Why bother tracking AI traffic separately?
You track AI traffic separately because it is small in volume, large in value, and growing fast, and your default GA4 reports bury it. AI search referrals averaged about 0.13 percent of total website traffic in 2026, which sounds ignorable until you look at quality. ChatGPT referral traffic converts at roughly 7.1 percent, ahead of organic search, social, email, and display, and second only to paid search at 7.8 percent. Ahrefs found AI search visitors converting at 23 times the rate of traditional organic in one analysis, where 0.5 percent of traffic drove 12.1 percent of signups. Even the more conservative Semrush figure puts AI conversion at about 4.4 times the cross-industry average.
The trend is steep. ChatGPT referral traffic rose about 60 percent per site in May 2026 across Adobe Analytics, GA4, and Optel, and spiked 157.7 percent week over week on May 7, 2026, when ChatGPT began surfacing clickable brand links inside its answers. ChatGPT drives roughly 82 percent of all AI platform referral traffic to external sites, so it is the engine to watch first. If you are doing AEO work, and any service business should be, you cannot prove it is paying back without isolating this channel. Lumping AI sessions into Referral or Direct hides your highest-converting visitors inside your least useful buckets.
What is the GA4 regex for AI traffic sources?
The working pattern matches the eight main AI referral domains, and you can extend it as new engines appear. Start with this for the core engines:
chatgpt\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|chat\.openai\.com|bard\.google\.com|meta\.ai
If you want broader coverage, this version adds more platforms:
chatgpt\.com|perplexity\.ai|claude\.ai|anthropic\.com|gemini\.google\.com|copilot\.microsoft\.com|deepseek\.com|you\.com|meta\.ai|poe\.com
The backslashes escape the dots so the regex matches the literal domain rather than treating the dot as a wildcard. Keep chat\.openai\.com and bard\.google\.com in the pattern even though both have been renamed, because old links and cached references still send traffic from those hostnames. Apply the pattern to the session source so it catches the referring domain rather than a page path.
How do you build the AI Traffic channel group in GA4?
Create a custom channel group in admin, add an AI Traffic channel with the regex, and put it above Referral so it claims AI sessions first. The steps:
Go to Admin, then Data display, then Channel groups, and create a new channel group. Name it something like “AI Traffic” so it is obvious in reports. Inside it, add a new channel, also named AI Traffic, and set the condition to Source matches regex, then paste one of the patterns above. Save the channel.
Now the step most setups miss: ordering. GA4 evaluates channel rules top to bottom and assigns each session to the first rule it matches. If your AI Traffic channel sits below the default Referral channel, AI sessions match Referral first and never reach your AI rule. Use the Reorder control and drag the AI Traffic channel above Referral. That single move is the difference between a populated AI channel and an empty one. Once it is in place, your reports will show AI Traffic as its own line you can segment, compare, and tie to conversions.
GA4 also rolled out a native “AI Assistant” channel group in 2026 that auto-detects ChatGPT, Gemini, and Claude. It is useful as a quick check, but it only captures sessions with intact referrer headers, so it inherits the same blind spot as the manual build. Use the native group for a fast read and the custom group when you need control over which engines you count.
Why does so much AI traffic still land in Direct?
A large share of AI sessions arrive with no referrer header, so GA4 cannot see where they came from and files them under Direct. Estimates put the missing share between 35 and 70 percent of AI referral sessions. The biggest cause is mobile apps. When someone uses the ChatGPT iOS or Android app and taps a link, the browser that opens often does not pass along where the tap originated, so the referrer is blank. Privacy settings, in-app browsers, and link handling all strip referrer data in ways that hit AI platforms harder than traditional search.
This means your AI Traffic channel is a floor, not a ceiling. The real number is higher than what the regex captures, and you should say so when you report it. Two practical ways to close part of the gap: watch for jumps in Direct traffic that correlate with AI citation wins, and add UTM parameters to any links you control that AI engines might surface, so those sessions carry attribution even when the referrer drops. Neither fully solves it, but both turn an invisible channel into a measurable trend. The honest framing for a client or a boss is that AI traffic is undercounted by default, the channel group recovers the visible portion, and the trend line matters more than the absolute number.
How do you connect AI traffic to AEO results?
Pair the GA4 channel data with citation tracking so you can see both the visits AI sends and the answers that send them. GA4 tells you how many AI sessions arrived and how they converted. It does not tell you which ChatGPT or Perplexity answer named you, or for which query. You get that from citation monitoring, the practice of checking which AI answers mention your brand and tracking changes over time. We cover the workflow in how to track when ChatGPT cites your law firm, and the principle applies to any business doing AEO.
Run them together and you have a closed loop: citation tracking shows you which answers you win, GA4 shows you the traffic and conversions those wins drive, and the combination tells you which AEO work pays back. That is the measurement layer most teams skip, and skipping it is why so many cannot tell whether their AI search investment is working. If you want the strategy behind the measurement, start with why press is the best AEO investment.
Frequently asked questions
Does GA4 track ChatGPT traffic automatically? Partly. GA4’s native “AI Assistant” channel group auto-detects ChatGPT, Gemini, and Claude, but it only catches sessions with intact referrer headers. A large share of AI sessions arrive with no referrer and land in Direct, so the automatic count undercounts. A custom channel group gives you more control but inherits the same blind spot.
Why is my AI traffic showing up as Direct? Because the referrer header is missing. Between 35 and 70 percent of AI sessions, especially from mobile apps, arrive with no referrer, so GA4 cannot attribute them and files them under Direct. Watch for Direct spikes that line up with AI citation wins, and use UTMs on links you control.
Where do I put the AI Traffic channel in the ordering? Above the Referral channel. GA4 assigns each session to the first rule it matches, top to bottom. If AI Traffic sits below Referral, AI sessions get claimed by Referral first and your AI channel stays empty.
What is the best regex for AI sources?
Start with chatgpt\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|chat\.openai\.com|bard\.google\.com|meta\.ai and extend it as new engines appear. Escape the dots, and keep the old OpenAI and Bard hostnames in for cached links.
Is AI traffic worth tracking if it is only 0.13 percent of sessions? Yes. It converts near the top of every channel, around 7.1 percent for ChatGPT and up to 23 times organic in some analyses, and it is growing fast. The volume is small now, the value per visit is high, and the trend line is what justifies your AEO spend.
Where to start
Build the channel group today, it takes five minutes, then watch the AI Traffic line for two weeks alongside your Direct traffic. Once you can see the channel, pair it with citation tracking so you know which answers are sending the visits. To see where your AI visibility stands now and where the gaps are, run our GSC analysis or book a call.
Tagged