AI search

AI Referral Traffic in Google Analytics: A GA4 Guide

GA4 now groups visits from ChatGPT, Gemini, Copilot and similar assistants into an AI Assistant channel. Google AI Overviews and AI Mode clicks stay in Organic Search, and visits with no referrer show up as Direct.

By SEORecheck Research Team, SEO auditorsPublished 9 min read

Blue and amber visit tokens enter three compartments, illustrating AI referral traffic in Google Analytics.
AI visits sorted into analytics channels

AI search referral traffic in Google Analytics means visits that reach your site from a link in an AI answer: ChatGPT, Gemini, Copilot, Claude, Perplexity and others. Since May 2026, GA4 sorts most of these visits into a built-in AI Assistant channel. There are three gaps you should know about. Clicks from Google AI Overviews and AI Mode still count as Organic Search, some AI visits arrive with no referrer and show up as Direct, and AI crawlers never appear in GA4 at all.

This guide covers where each kind of AI visit shows up in GA4, how to build a report that holds up, and how to read the numbers without over-reading them.

Does Google Analytics track AI search traffic now?

Yes. According to Google's What's new in Google Analytics page, on May 13, 2026, GA4 started to "measure and analyze traffic originating from popular AI assistants" such as ChatGPT, Gemini and Claude. When the referrer matches a known assistant, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant), and the session goes into the AI Assistant channel.

Google's default channel group definitions describe the channel this way: users arrive "from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok. It excludes Google's AI Overviews and AI Mode." That exclusion matters more than anything else in this guide, and the sections below explain why.

Before this channel existed, visits from AI assistants usually showed up as ordinary Referral traffic, for example chatgpt.com / referral. Google's release note doesn't say that older sessions are reclassified. For months before mid-May 2026, look for them in Referral, or use a custom channel group (covered below), which GA4 can apply to past data.

Where does each AI platform show up in GA4?

AI visits land in four places: the AI Assistant channel, Referral, Organic Search and Direct. Which one depends on the platform and on whether the browser passes a referrer. Use this table as your map before you build any report.

Source of the visit Where it usually appears in GA4 Notes
ChatGPT (chatgpt.com) AI Assistant Named in Google's release note. Landing URLs often carry utm_source=chatgpt.com, so check your own landing-page data
Gemini app AI Assistant Named by Google
Microsoft Copilot AI Assistant Listed in the channel definition
Claude AI Assistant Named in the release note
DeepSeek, Grok AI Assistant Listed in the channel definition
Perplexity and smaller assistants Check: AI Assistant or Referral Not named in Google's examples. Confirm in your own property
Google AI Overviews and AI Mode Organic Search (google / organic) Explicitly excluded from AI Assistant
Desktop or mobile AI apps that strip the referrer Direct No referrer means GA4 can't attribute the visit
AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot) Not in GA4 Bots don't run your analytics tag. Use server logs

Google says the AI Assistant channel matches against "a list of AI Assistants", and that list can change. So treat the table as where to start, and check your own Traffic acquisition report against it.

How do I see AI Assistant traffic in GA4?

Go to Reports → Acquisition → Traffic acquisition. Make sure the primary dimension is Session primary channel group (Default Channel Group), then find the AI Assistant row. To see which assistants sent the visits, add Session source as a secondary dimension.

Here are three views worth saving:

  1. Assistant by source. Session primary channel group = AI Assistant, broken down by Session source. This shows which assistants send visits and how many.
  2. Landing pages. Go to Reports → Engagement → Landing page and filter to the AI Assistant channel. These are the pages AI answers actually link to. Usually that's a short list of guides, pricing pages and comparison pages.
  3. Outcomes. Add Key events and Session key event rate to the Traffic acquisition report. Compare AI Assistant with Organic Search on engagement rate and key event rate, not only on session counts.

When you compare engagement or conversions, use the same date range, the same key events and the same set of landing pages for each channel. AI visitors often land deep on a single answer page, so a raw comparison with sitewide organic traffic is rarely fair.

How do I build a custom AI channel group in GA4?

If Perplexity or another assistant still lands in Referral, or if you want your own definition, create a custom channel group. GA4 can apply custom channel groups to past data, so you can also rebuild the months before May 2026.

According to Google's custom channel groups help page, standard properties can have 2 custom groups and Analytics 360 properties can have 5. Each group holds up to 50 channels. Conditions can use source, medium, campaign name, campaign ID, source platform, manual ad content and default channel group, and they support "matches regex". Order matters: "Traffic is included in the first channel whose definition it matches", so put your AI channel above Referral.

Setup:

  1. Go to Admin → Data display → Channel groups → Create new channel group. Start by copying the default group so every other channel stays the same.
  2. Add a channel called "AI search & assistants".
  3. Condition: Source matches regex with a pattern like the one below. You can add an OR condition for Medium exactly matches ai-assistant.
  4. Drag the new channel above Referral and save. Then pick the group as the dimension in Traffic acquisition.
.*(chatgpt|openai|perplexity|claude|anthropic|gemini|copilot|deepseek|grok|you\.com|meta\.ai|mistral).*

Every few months, check what this pattern catches. Look at session sources in Referral and Direct for new assistant domains, and add them. Keep the pattern narrow, because a broad word like ai will also match unrelated referrers.

Why is my AI Overviews traffic not in the AI Assistant channel?

The AI Assistant channel leaves out Google's AI features by design. Clicks from an AI Overview or from AI Mode reach your site from google.com, so GA4 records them as google / organic, together with clicks on regular blue links. GA4 has no dimension that splits them apart.

Search Console is where you see Google's AI features. Google's AI features and your website page says sites appearing in AI Overviews and AI Mode "are included in the overall search traffic in Search Console" and are reported "within the 'Web' search type." Google then added dedicated Search Generative AI performance reports, which show impressions by page, country, device and date. Clicks are not listed as a metric there. The data also stays in the overall Performance report.

In practice, you can see that a page appears in AI Overviews or AI Mode (from Search Console impressions), and you can see what organic visitors do on that page (in GA4). What you can't do is count exactly which sessions came from an AI Overview link. For more on keeping eligible for these features, see Google AI Mode optimization.

Why do some AI visits show up as Direct?

Some AI visits arrive without a referrer. Desktop and mobile apps, links copied out of an answer and pasted into a browser, and some privacy settings can all strip the referrer. Without a referrer or UTM tag, GA4 counts the session as Direct, and no channel rule can recover it.

Signs that AI traffic is hiding in Direct:

  • Direct sessions rise on deep, long-tail pages (a specific guide or a comparison page), when Direct traffic normally lands on your homepage.
  • The rise lines up with a time when you started appearing in AI answers. Your brand mention tracking prompt log can confirm this.
  • Landing URLs carry tags such as utm_source=chatgpt.com while the session is still attributed to Direct. This can happen with consent setups or with redirects that drop the referrer.

You can't fully measure this hidden share. Report it as a range, not a number. For example: "AI Assistant: 420 sessions. A further unexplained rise in Direct on 12 guide pages."

Why don't AI crawlers show up in Google Analytics?

GA4 counts visitors whose browsers run your tracking script. AI crawlers fetch HTML and don't run it. OpenAI's crawler documentation says OAI-SearchBot is "used to surface websites in search results in ChatGPT's search features", and that ChatGPT-User fetches pages when a user asks for them, not as automatic crawling. Neither appears in GA4.

So a GA4 report can't tell you whether AI systems can reach your pages. That question lives in robots.txt, your firewall and your access logs. The server log analysis guide shows how to verify real AI bot hits, and AI crawler access explains which bots to allow. If you block OAI-SearchBot, OpenAI says your pages won't appear in ChatGPT search answers, apart from navigational links. In that case there's little referral traffic left to measure.

If AI referrals are flat or zero, check access first. A SEORecheck free audit reviews robots.txt rules for AI search, user and training bots, snippet controls, text that only appears after JavaScript runs, and Organization/sameAs markup, so you can rule out blocking before you blame demand.

How should I report AI referral traffic?

Report it as its own line, with context, once a month. AI referral traffic is usually small next to organic search, so share of total sessions misleads. Track the trend, the landing pages and the key event rate instead, and write down the gaps.

A simple monthly block:

Metric Source Why it matters
AI Assistant sessions, by source GA4 Traffic acquisition Which assistants send visitors
Top 10 AI landing pages GA4 Landing page, filtered Which content AI answers link to
Key event rate, AI vs Organic GA4 Whether the visits are worth it
AI Overviews / AI Mode impressions by page Search Console generative AI report Google AI visibility, without clicks
Unexplained Direct rise on deep pages GA4 Possible hidden AI traffic
AI bot hits and blocks Server logs, robots.txt Whether AI systems can reach you

Add notes whenever something changes the numbers: a site migration, consent banner changes, a robots.txt edit. For the wider picture of AI and classic metrics, see SEO vs GEO performance measurement. The sample report shows how GEO checks are presented as passed or failed rather than as a single score.

Common mistakes

  • Comparing AI Assistant data before and after May 13, 2026, without adjusting. Earlier AI visits sit in Referral. Use a custom channel group for a consistent series.
  • Reading Organic Search as "no AI". AI Overviews and AI Mode clicks are inside it.
  • Using a regex that's too broad. A pattern like .*ai.* matches mail, retail and dozens of other unrelated referrers.
  • Putting the custom AI channel below Referral. The first matching channel wins, so the AI channel never gets any sessions.
  • Treating zero AI traffic as zero visibility. Being cited without clicks, visits with no referrer and blocked crawlers all look like zero in GA4.

Key takeaways

  • Since May 13, 2026, GA4's AI Assistant default channel groups visits from assistants such as ChatGPT, Gemini, Copilot, Claude, DeepSeek and Grok.
  • Google AI Overviews and AI Mode are excluded. Their clicks count as Organic Search. Use Search Console's generative AI reports for impressions.
  • A custom channel group with a regex on Source, placed above Referral, catches assistants GA4 misses and can rebuild data from before May 2026.
  • Visits with no referrer go to Direct. Report them as a range, not a precise figure.
  • AI crawlers never appear in GA4. Check robots.txt, firewall rules and server logs to confirm AI systems can reach your pages.
All articles
Amber map pin above business facts illustrates AI search optimization for local businesses.

AI search

AI Search Optimization for Local Businesses: A Guide

For a local business, AI search optimization means accurate listings, matching facts on your site, crawlable service and location pages, AI crawler access and real reviews. There's no special AI trick on top of that.

10 min read

A blue scan illuminates pricing, features, integrations and docs, illustrating AI search optimization for SaaS.

AI search

AI Search Optimization for SaaS: A Practical Guide

AI search optimization for SaaS means making your marketing site, docs, pricing and integration pages crawlable, indexable and quotable, so AI assistants describe your product correctly when buyers compare tools.

9 min read

Products and data enter shopping results through a glowing gateway, illustrating AI search optimization for ecommerce.

AI search

AI Search Optimization for Ecommerce: A Store Guide

AI search optimization for ecommerce means making product data available through feeds, indexable pages and open crawler access so AI answers can show, describe and link your products accurately.

9 min read