In May 2026, Google Analytics finally gave AI tools their own channel. Open your GA traffic acquisition report today and you may see a new row called AI Assistant, sitting next to Organic Search and Referral.
That is good news. But if you take that row at face value, you are probably undercounting the visitors who found you through ChatGPT, Gemini, Claude or Perplexity. A large share of them never reach that channel. They land in Direct, or even in Organic Search, and look like something else entirely.
This matters because AI-referred visitors tend to be some of the most qualified people arriving on your site. Here is what changed, where the missing traffic goes, and a short audit you can run this week.
What GA changed
On 13 May 2026, Google announced an “AI Assistant” channel in GA’s Default Channel Group. No setup is needed. Sessions whose referrer matches a recognised AI assistant (Google names ChatGPT, Gemini and Claude as examples) are now separated from generic Referral traffic, with the medium set to ai-assistant.
Three limitations are worth knowing:
- The list of AI platforms is not published. Smaller or newer assistants may still fall into Referral.
- It only works when a referrer is sent. If the visit arrives without one, GA has nothing to match.
- It can quietly change existing reports. Segments or filters such as “medium does not contain cpc” will now also include or exclude these sessions differently. Check any dashboard that relies on medium.
Where the rest of your AI traffic goes
A visit only lands in the AI Assistant channel if the browser tells GA where it came from. In practice, that often doesn’t happen:
- Mobile apps and in-app browsers. Links opened from the ChatGPT or Claude mobile apps frequently arrive with no referrer, so GA records them as Direct.
- Copied links. Many people copy a URL from an AI answer and paste it into a new tab. That is a Direct visit by definition.
- Google AI Overviews. Clicks from AI Overviews carry a normal google.com referrer, so they are counted as Organic Search, not AI.
- Consent banners. In markets with strict consent rules, visitors who decline analytics cookies are not tracked at all, whatever channel they came from.
How big is the gap? Loamly, an AI attribution vendor, found that 70.6% of the 20,428 AI visits it tracked arrived with no referrer at all, so GA recorded them as Direct. Loamly measured this with its own detection tool, so treat the exact figure as an estimate. The direction is clear, though: the new channel is a floor, not the full picture.
Why it matters for your numbers
AI search is still a small share of total traffic for most sites. Visionary Marketing’s 2026 AI referral study, based on 14.7 million AI-attributed sessions in its own tracking data, put AI search at 1.84% of organic traffic in March 2026, up from 0.21% in early 2024. But the quality of that traffic stands out:
- In the same Visionary Marketing data, AI referrals converted at 4.21%, against 1.94% for Google organic search.
- Microsoft Clarity’s study of more than 1,200 publisher and news sites found visitors from AI assistants signed up at 1.66%, against 0.15% from search: roughly 11 times higher.
These studies come from different companies using different methods, so treat the exact figures with care. The direction is consistent, though: AI visitors arrive later in their decision and convert better. If most of them are hidden in Direct, two things go wrong. You under-invest in the content that AI tools cite, and your Direct channel looks healthier and more “brand-driven” than it really is.
A 5-step AI traffic audit
1. Check the new AI Assistant channel
In GA, open Reports → Acquisition → Traffic acquisition and set the primary dimension to Session default channel group. Note sessions, key events and revenue for AI Assistant, and compare its conversion rate with Organic Search.
2. Catch the AI tools Google misses
Create a custom channel group (Admin → Data display → Channel groups) with an “AI tools” channel placed above Referral, matching session source against a list of AI domains, for example chatgpt.com, perplexity.ai, gemini.google.com, claude.ai, copilot.microsoft.com. Review the list every quarter, because new assistants appear quickly.
3. Look inside Direct
Real direct traffic usually lands on your homepage or brand pages. AI-referred visits often land deep: a specific guide, comparison or pricing page. Build an exploration of Direct sessions by landing page. A rise in Direct traffic to deep content pages since 2024 is a strong signal of hidden AI traffic.
4. Compare with your server data
Your server or CDN logs see requests that GA never records, including visits from users who declined consent and the AI crawlers that read your pages. If you use server-side tagging, compare its event counts with GA to estimate how much your client-side setup is missing.
5. Change how you report it
Stop reporting AI traffic as one exact number. Report a range: the AI Assistant channel as the confirmed minimum, plus an estimate from deep-page Direct traffic. Add AI-referred conversion rate next to organic in your monthly dashboard, so leadership sees the quality, not just the volume.
Final thoughts
GA’s new channel is a useful first step, not the full answer. The visitors coming from AI tools are among your most valuable, and most of the tools still hide them. A few hours spent on channel rules, Direct traffic analysis and server-side data will give you a far more honest view of where your best leads come from.
Sources
- Google Analytics Help, “What’s new in Google Analytics” (13 May 2026)
- Loamly, AI traffic attribution study (updated February 2026)
- Visionary Marketing, “ChatGPT & AI Search Referral Statistics 2026” (May 2026)
- Microsoft Clarity, “AI Traffic Converts at 3x the Rate of Other Channels (Study)” (November 2025)
How Gmetrics can help
Our Analytics & Insights team audits GA channel rules, Direct traffic and server-side data so you can see how much AI traffic your reports are missing. Explore our Analytics & Insights service to learn how we approach this with clients. To talk through your setup, contact Gmetrics.
