How We Track AI Traffic (ChatGPT, Perplexity, Claude) — Not in GA4

Direct answer

GA4 added a default "AI Assistant" channel on May 13, 2026 — it auto-classifies recognized sources (ChatGPT, Gemini, DeepSeek, Copilot, Grok) by rewriting medium to ai-assistant. But it misses Perplexity, which still lands in Referral, and one assistant's visits can fragment across AI Assistant, Referral and Unassigned. The reliable GA4 setup is still a custom channel group with a full-match regex over known AI referrer domains (chatgpt.com, chat.openai.com, perplexity.ai, copilot.microsoft.com, claude.ai, gemini.google.com), and referrer-stripped visits still land in Direct. We use AttriFast — full disclosure: it's built by ToolProven's founder — which breaks out visits per assistant and ties revenue to each channel out of the box.

Last verified

Aug 1, 2026

How we know

Desk-verified against primary sources

Note

Includes third-party reporting — flagged in text

Sources

4 linked

Evidence used

• Google added a native "AI Assistant" default channel to GA4 on May 13, 2026 (dated entry in Google Analytics' What's-new log). Its recognized source list — ChatGPT, Gemini, DeepSeek, Copilot, Grok — omits Perplexity, which still classifies as Referral; checked against Google's channel-group documentation Aug 1, 2026.
• Per-assistant referrer splitting and revenue attribution shown here are from a live AttriFast dashboard on one of our own sites (30-day window: 6,156 visitors, 109 — 1.8% — from AI assistants; ChatGPT 82, Copilot 10, Claude 6, Gemini 6, DeepSeek 2, Perplexity 2, Grok 1).
• DISCLOSURE: AttriFast is built by ToolProven's founder. This is a first-party explainer of our own stack, not an independent review — we say so wherever it matters.

How we checked this

• This page follows our disclosure rule in reverse: when the tool is ours, we tell you before the first claim, and we describe what GA4 can do fairly — including the manual route that costs nothing.
• GA4 guidance was re-verified against Google's own channel-group documentation and What's-new log on Aug 1, 2026. The ~70% referrer-stripped share cited below is a third-party industry estimate we have not reproduced, and it is labeled as such.

GA4's new AI Assistant channel — and why it still under-counts

Since May 13, 2026 GA4 ships a default AI Assistant channel that rewrites medium to ai-assistant for recognized sources: ChatGPT, Gemini, DeepSeek, Copilot, Grok. Perplexity is not on the list and still lands in Referral, referrer-stripped visits still land in Direct, and one assistant's traffic can fragment across three channels — so the custom channel group survives.

First, a correction. The original July 2026 version of this page said GA4 ships no default AI channel — that was already out of date when we published it: Google had added a native AI Assistant default channel on May 13, 2026 (dated in the Analytics What's-new log), which auto-rewrites medium to ai-assistant and campaign to (ai-assistant) for recognized sources. We missed it, and we're saying so rather than quietly rewording.

The correction rescues nothing for Google, though, because the native channel's coverage is the story now. Its recognized list is ChatGPT, Gemini, DeepSeek, Copilot and Grok — Claude appeared on the initial list and was later removed — and Perplexity is not recognized at all, so perplexity.ai visits still classify as Referral. Worse, a single source can fragment: chatgpt.com traffic splits across AI Assistant (tagged), Referral (unrecognized surfaces) and Unassigned (missing medium). So the recommendation this page has always made survives the update, with a new reason: build the custom channel group not because no channel exists, but because the native one misses Perplexity and fragments the rest.

Why we bother at all: AI answers are becoming a real acquisition channel — the entire GEO playbook this site runs (llm-context manifests, quotable verified facts, publisher notes) exists to earn those citations. A channel you invest in but can't measure per-source is a channel you can't iterate on: knowing ChatGPT sends 82 visits while Perplexity sends 2 tells you exactly which engine is actually citing you.

How to track Perplexity and ChatGPT traffic in GA4

Fastest check: Reports → Acquisition → Traffic acquisition, switch the primary dimension to Session source, and search chatgpt.com or perplexity.ai — the sessions listed are that assistant's referrals. Permanent fix: a custom channel group whose AI rule uses a full-match regex over AI referrer domains, dragged above Referral so it wins classification.

To see ChatGPT referral traffic right now: open Reports → Acquisition → Traffic acquisition, switch the primary dimension to Session source, and type chatgpt.com into the search bar above the table. The sessions listed are ChatGPT's referrals — and because ChatGPT also appends utm_source=chatgpt.com to many cited links (coverage expanded through 2025, though not universal), filtering on source chatgpt.com catches both the referrer and the UTM-tagged cases. Repeat with perplexity.ai for Perplexity — the one major assistant GA4's native AI Assistant channel does not recognize, so filtering by source is the only way it surfaces at all.

For an ad-hoc multi-assistant view, use Explore → Free form with dimension Session source, metrics Sessions and Total users, and a filter of Session source → matches regex → the core pattern below. Know this before pasting anything: GA4 regex is full-match (RE2), so a bare token like chatgpt matches nothing — the alternations below work because Session source is the bare domain, with every dot escaped. (The inline pattern an earlier version of this page suggested — chatgpt|openai|perplexity|… — would have matched zero sessions in a full-match field. Corrected.)

The permanent fix is the custom channel group: Admin → Data display → Channel groups → create a copy of the Default group → add a channel named AI Assistants → condition Source → matches regex → paste the regex → drag the new channel above Referral and Organic (first match wins) → save. Two caveats stand from the original version of this page: the group applies forward-only from creation, and you must pick it as the report's primary dimension yourself, because it does not replace Default automatically.

• Core regex (the assistants people actually ask about): chatgpt\.com|chat\.openai\.com|perplexity\.ai|copilot\.microsoft\.com|claude\.ai|gemini\.google\.com
• Extended regex (adds legacy and secondary surfaces): chatgpt\.com|chat\.openai\.com|perplexity\.ai|copilot\.microsoft\.com|claude\.ai|gemini\.google\.com|bard\.google\.com|edgeservices\.bing\.com|m365\.cloud\.microsoft|chat\.deepseek\.com|deepseek\.com|grok\.com|meta\.ai|you\.com|chat\.mistral\.ai
• To also catch subdomain and path variants, wrap it: .*(chatgpt\.com|perplexity\.ai|copilot\.microsoft\.com|claude\.ai|gemini\.google\.com).* — and never use bare tokens like gpt, which false-positive.

What no regex can see: Direct, AI Overviews and the missing 70%

Any GA4 number for AI traffic is a floor, not a total. Third-party analyses estimate roughly 70% of AI-driven visits arrive with no referrer and classify as Direct, mentions without links send nothing measurable at all, and Google AI Overviews clicks arrive as google / organic — inseparable by any filter, forever.

The referrer-stripped share is the big one: 2026 industry analyses put around 70% of AI-driven visits arriving with no referrer at all — classified Direct — with only about 29% carrying a recognizable AI referrer. Those are third-party estimates we have not reproduced, but the mechanics behind them are verifiable: assistants' in-app browsers strip referrers, only ChatGPT reliably self-tags with a UTM, and Perplexity, Claude and Gemini ride on the referrer alone. Add the two structural losses — a brand mention without a link sends zero measurable traffic, and most AI answers satisfy the query with no click at all — and whatever your channel group reports is the measurable minimum, not the channel's size.

Google's own AI surfaces are the hardest case: clicks from AI Overviews and AI Mode carry no distinguishing referrer and land as google / organic, so no GA4 regex can ever separate them from classic search. The partial relief arrived June 3, 2026, when Search Console added Search Generative AI performance reports (announced on the Search Central blog) — dedicated views of your impressions in AI Overviews and AI Mode, broken down by page, country, device and date. Read them for what they are: impressions only — no clicks, no CTR, no position, no query breakdown — and a rollout that started limited (UK first). GA4 cannot see this traffic; GSC can only see the top of it.

What we use instead — disclosure first

AttriFast — built by ToolProven's founder, disclosed here and everywhere it appears. It splits AI traffic per assistant natively, ties revenue to each channel, and keeps the rest (entry pages, bounce, sessions, realtime) on one screen.

What it looks like in practice, from the live dashboard of one of our sites: a dedicated AI tab under the traffic panel lists each assistant with its visit count — ChatGPT 82, Copilot 10, Claude 6, Gemini 6, DeepSeek 2, Perplexity 2, Grok 1 — alongside the usual channels, with revenue attributed per channel ($1,150 across this 30-day window) rather than sitting in a separate reporting module. The number that changed our behavior wasn't the 1.8% share; it was the 40:1 ChatGPT-to-Perplexity split, which reordered where we spent citation-building effort.

The honest comparison: GA4 is free, immensely capable, and can be configured to approximate the AI split; AttriFast is the convenience-and-clarity trade — per-assistant tracking and revenue attribution working on day one, aimed at operators who'd rather read the answer than maintain the regex. Evaluate it the way we'd tell you to evaluate anything: on your own site, against your own GA4 property, with the same 30 days of data.

Related ToolProven pages