How to Track AI Traffic (ChatGPT, Perplexity, Claude) in GA4
Visitors are arriving at your site from ChatGPT, Perplexity, Gemini, and Claude right now, and GA4, out of the box, files them under generic Referral or, worse, Direct. If you've noticed an unexplained rise in Direct traffic over the past year, a chunk of it is probably AI assistants sending you visitors with no label attached.
This matters more than the raw counts suggest: AI referrals are consistently reported to convert at multiples of organic search traffic (Adobe's research puts it around 4×, with far longer sessions), because someone arriving from an AI answer has already been pre-qualified by the conversation they were having. Here's the 10-minute setup, copy-paste regex included, plus the honest caveats about what GA4 can't see.
TL;DR
- GA4 has no complete built-in AI channel. Google added a native "AI Assistant" channel in May 2026, but it only recognises a handful of sources, Perplexity is notably missing, so a custom channel group is still the right setup.
- Fix: Admin → Data display → Channel groups → create an "AI Traffic" channel with a source regex (below), then drag it above Referral in the rule order.
- A large share of AI visits (estimates run 35–70%) arrive with no referrer at all and land in Direct, your custom channel is a floor, not a census.
- Traffic from Google AI Overviews can't be separated, it arrives bundled into google / organic. No GA4 configuration changes that.
Why AI Traffic Is Invisible by Default
Two separate problems stack:
- Classification. GA4's default channel rules predate AI assistants. A session from chatgpt.com matches the generic Referral rule, so it's lumped in with every other referring site. Nothing is lost, it's just unlabelled.
- Missing referrers. Many AI surfaces, native mobile apps, desktop apps, some in-conversation link-outs, pass no referrer header at all. Those sessions are indistinguishable from typed-in traffic and land in Direct. No GA4 setup recovers them; only landing-page patterns hint at their scale.
So the goal is honest: label everything that can be labelled, and know the blind spots.
Step 1: See What's Already There (2 Minutes)
Reports → Acquisition → Traffic acquisition → switch the primary dimension to Session source/medium → search for chatgpt, perplexity, claude, copilot, gemini. Whatever appears is your baseline, and it's already an undercount. Now let's make it a channel.
Step 2: Create the Custom "AI Traffic" Channel (10 Minutes)
Admin → Data display → Channel groups. Don't edit the Default Channel Group in place, click Copy to create new, name it something like "Channels incl. AI". Add a new channel named AI Traffic with the condition Session source → matches regex:
.*chatgpt\.com.*|.*chat\.openai\.com.*|.*openai\.com.*|.*perplexity\.ai.*|.*claude\.ai.*|.*gemini\.google\.com.*|.*bard\.google\.com.*|.*copilot\.microsoft\.com.*|.*deepseek\.com.*|.*grok\.com.*|.*x\.ai.*|.*meta\.ai.*|.*you\.com.*|.*chat\.mistral\.ai.*|.*poe\.com.*(GA4's channel-group regex requires a full match, hence the .* wrappers. If your regex field says "contains", drop them.)
Then the step everyone misses: drag AI Traffic above Referral (and above Organic Search) in the channel list. GA4 evaluates rules top to bottom and stops at the first match, if Referral sits higher, your AI rule never fires. Save. Revisit the regex quarterly; new assistants appear constantly.
A Note on GA4's Native "AI Assistant" Channel
In May 2026 Google added an AI Assistant channel to the Default Channel Group, sessions from recognised AI referrers get the medium ai-assistant automatically. Useful signal that Google now treats this as a first-class category; not sufficient in practice, because its recognised list is short (ChatGPT, Gemini, Copilot, DeepSeek, Grok among them) and does not include Perplexity, for many sites the single biggest AI referrer. Keep the custom channel group; treat the native channel as a cross-check.
Step 3: Build the Analysis View (5 Minutes)
Explore → Blank exploration, 12-month range:
- Dimensions: Session source, Landing page + query string
- Metrics: Sessions, Engaged sessions, Engagement rate, Key events, Session key event rate
- Filter: Session source matches your AI regex
This answers the questions that matter: which pages do AI assistants send people to, and do those visitors convert? The landing-page view is the strategic one, it shows which content AI systems consider citable. Those pages are your template for winning more citations.
The Blind Spots (Read Before Reporting Numbers)
- Direct-traffic leakage. The 35–70% of AI visits without referrers land in Direct. If Direct rose in lockstep with AI adoption and its landing pages skew to deep content URLs (not your homepage), that's the AI shadow. Report your AI channel as "at least".
- Google AI Overviews are unmeasurable in GA4. Clicks from AI Overviews carry standard google / organic attribution. Search Console doesn't split them out either. Any tool claiming to measure your AI Overviews traffic precisely is estimating.
- Zero-click exposure doesn't show up at all. When ChatGPT answers using your content without the user clicking through, no analytics tool sees it. Traffic is the tip; influence is the iceberg.
Frequently Asked Questions
How do I see ChatGPT traffic in GA4?
Filter Traffic acquisition by session source containing "chatgpt", or better, create a custom channel group with a regex covering all AI referrer domains (setup above) so every assistant rolls into one AI Traffic channel.
Why is my AI traffic showing as Direct?
AI apps (mobile and desktop) and some link-outs pass no referrer header, so GA4 can't attribute the session to a source. This is a technical limitation of the referrer mechanism, not a GA4 setting, expect your labelled AI channel to undercount.
Does GA4 track AI traffic automatically now?
Partially. Since May 2026, GA4's Default Channel Group includes an AI Assistant channel, but its recognised source list is incomplete (no Perplexity). A custom channel group remains the reliable approach.
Can I track traffic from Google AI Overviews?
Not separately. AI Overviews clicks arrive as regular google / organic traffic in both GA4 and Search Console. There is currently no way to isolate them.
Knowing Where AI Traffic Lands Is Step One
Being the site AI assistants cite is the game. Structured, machine-readable content is how you get picked.
LinkedIn