On May 13, 2026, Google quietly added a new traffic source called "AI Assistant" to GA4's Default Channel Group, reaching most properties by around June 7. The significance: AI-driven traffic used to scatter across Referral and Direct where you couldn't identify it; now GA4 finally pulls it into its own row. A frequently cited figure — visitors from AI tools spend 68% longer and convert at up to 15.9% higher rates than organic search. This traffic doesn't just exist; it often converts better than ordinary organic.
The change only makes sense in context. Over the past 12–18 months, AI search went from experiment to default: Google made Gemini-powered answers the default for all queries in July, with multiple studies reporting steep drops in top-page clicks; meanwhile assistants like ChatGPT and Perplexity began sending users straight to sites. The problem was that this traffic was a "dark number" — you knew people came from AI, but you couldn't see it in the report. GA4's new channel is the first time the platform formally acknowledges "AI Assistant" as its own acquisition source.
But look closer and the channel has a big hole. Per multiple hands-on tests, GA4's AI Assistant channel currently recognizes only five sources: ChatGPT, Gemini, Deepseek, Copilot, Grok. Claude and Perplexity are not on the list — their traffic still falls into Referral. And ChatGPT alone accounts for roughly two-thirds of all AI referrals, so the "AI Assistant" number you see is already truncated at both ends.
For Taiwanese SMBs and agencies, this means two things: you finally have official data to prove to a boss that "AI-driven traffic is worth investing in," and you can't look at only this row, or you'll badly undercount AI's real contribution. Below: how to read it, what to watch, and how to fill in the missing half of the report without a SaaS subscription.
How the Channel Actually Works
GA4's AI Assistant channel works by source-domain matching: when someone clicks through from chatgpt.com, gemini.google.com and similar domains, GA4 assigns that session to AI Assistant. To see it: open GA4 → Reports → Acquisition → Traffic acquisition, set the primary dimension to Session default channel group; if you've had AI traffic since the channel went live, "AI Assistant" appears as its own row.
Three technical limits to know:
- Referrer-only: if a user reads an AI answer, remembers your brand and later types your URL directly, that's counted as Direct, not AI — this "zero-click influence" is invisible to GA4.
- The list is hard-coded: Claude and Perplexity aren't included and land in Referral. You have to fish claude.ai and perplexity.ai out yourself.
- AI crawlers aren't traffic: AI fetching your content for training or retrieval is different from AI referring users; the former never shows in this channel.
Immediate Actions for Three Reader Types
- Brand owners/SMB owners: Have marketing pull the "AI Assistant" row monthly and compare it side by side with organic search and social. Watch conversion rate, not just volume — AI traffic is smaller but usually more intent-rich.
- Marketing/SEO operators: Build a custom channel group or exploration in GA4 that manually groups sources like claude.ai, perplexity.ai and chatgpt.com into one "AI (full)" bucket to patch the two Google left out. Track which pages this traffic lands on to reverse-engineer which content AI is citing.
- Developers/agencies: Set up custom channel rules and a UTM convention for clients, and export/compare periodically. This is packageable work you can bill today.
SaaS Tool Comparison
| Option | Captures | Misses | Cost |
|---|---|---|---|
| GA4 native AI Assistant channel | ChatGPT/Gemini/Copilot/Grok/Deepseek referrals | Claude, Perplexity, zero-click influence | Free |
| GA4 custom channel group (DIY) | Manually adds Claude/Perplexity | Zero-click influence | Free (setup time) |
| AI-visibility tools (Profound/Scrunch, etc.) | How often your brand is cited in AI answers | Not equal to real site traffic | From hundreds of USD/month |
| Server-log analysis (self-host) | AI crawler behavior + referral | Requires self-hosting and parsing | Server cost + time |
What They Won't Tell You
The pitch says "GA4 can measure AI traffic now," but two truths matter. First, the channel structurally undercounts AI: it only catches referrals, while AI's biggest impact is zero-click — "read it, remembered you, came later" — which always books as Direct. The number you see is a floor, not a ceiling. Second, "cited by AI" and "traffic from AI" are two different things: brands pay for visibility tools, see they're frequently mentioned by ChatGPT and celebrate — but if the AI answer has no clickable link, or users don't click, that "visibility" never becomes a GA4 session. Don't conflate the two metrics.
The No-SaaS Alternative
You can patch the missing half without buying a tool. Three steps: first, in GA4 → Admin → Channel groups, copy the default group and add a rule that routes source domains like claude.ai, perplexity.ai and chatgpt.com into a custom "AI (full)" channel; second, build an Exploration with source/medium dimensions filtered to those domains to see what Google left out; third, to approximate even zero-click, add an onboarding survey ("How did you find us?") with "AI recommendation" as an option to fill the gap with self-reported data. All free — only setup time. Business takeaway for ScriptWalker: this is exactly the kind of "AI traffic attribution setup pack" you can standardize into a consulting offer — half a day of work, a visibly upgraded report for the client.
FAQ
Why don't I see an AI Assistant row in my GA4 yet?
Two possibilities: your property hasn't had any matching AI referral traffic since the channel went live (around June), and with no data the row won't show; or you're viewing an old custom channel group. Confirm you're on the Default Channel Group and set the date range to after June.
Where does Claude and Perplexity traffic go now?
Into Referral. GA4's AI Assistant currently recognizes only ChatGPT, Gemini, Copilot, Grok and Deepseek. To see Claude/Perplexity, fish claude.ai and perplexity.ai out of Referral, or add a custom channel rule to group them.
Is AI traffic worth focusing on?
Yes. Volume is usually smaller than organic search, but studies show AI visitors stay longer and convert higher, signaling clearer intent. Rather than chase the traffic number, chase conversion and landing-page performance for this segment.
Do I need a tool like Profound?
Not necessarily. Those tools measure "how often you're mentioned in AI answers," which is not the same as "how much attributable traffic AI sends." SMBs should first fix attribution with GA4's free custom channels, confirm there's real traffic and conversion, then decide whether to add a paid tool.
My Take
The mainstream line is "buy an AEO/GEO tool now or fall behind." My call is the opposite: for the next 12–18 months, what most SMBs actually lack isn't a visibility tool — it's the basic hygiene of seeing and counting the AI traffic they already have. The real value of GA4's new channel is the reminder that even Google officially recognizes only half the sources, so you should set up your free attribution correctly before spending money. For ScriptWalker, this is a low-barrier, high-trust entry point: rather than sell clients an expensive AI marketing package, first clean up their GA4 AI attribution, prove value with real data, then move up to content and GEO. Get the accounting right first, and the decisions that follow have meaning.
Sources
First-party: - GA4 Default Channel Group — Google Analytics Help - GA4 Traffic acquisition report — Google Analytics Help
Third-party: - GA4's New AI Assistant Channel — Digital Applied - GA4 AI Traffic: ChatGPT Referrals — Nice Looking Data - Your AI Traffic Is Showing Up in GA4 Now — IncrementX