Where do you view AI traffic in GA4?
In the AI Assistant channel of the default channel group in Google Analytics 4 (GA4). Google defines it as visits from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok, and it leaves out Google's own AI Overviews and AI Mode.
To see it:
- Open the Traffic acquisition report.
- Keep the default channel group as the primary dimension, and find the AI Assistant row.
- Switch the primary dimension to Session source / medium to see which assistant sent each visit.
When GA4 recognizes the referrer as an AI assistant, it sets the medium to ai-assistant and the campaign to (ai-assistant). You can filter reports and explorations on either value.
How does ChatGPT traffic show up in GA4?
With chatgpt.com as the source. OpenAI says ChatGPT adds utm_source=chatgpt.com to the links it shows, so GA4 can attribute the visit from the link itself.
OpenAI also tells site owners not to block its OAI-SearchBot crawler if they want their content in ChatGPT's search results. If your robots.txt blocks it, there may be little ChatGPT traffic to measure, so check that file before you read a low number as low interest.
Which AI traffic sources can GA4 miss?
Some AI traffic never reaches the AI Assistant channel, mainly from assistants that aren't on Google's list and from Google's own AI features.
- Assistants Google doesn't list. Google doesn't publish the full list behind the AI Assistant channel. Its downloadable list of sources and categories, checked on October 15, 2026, has categories for search, social, shopping, and video only. If sources such as perplexity.ai or claude.ai appear under Referral, the default channel isn't catching them.
- AI Overviews and AI Mode. Google excludes them from the AI Assistant channel, so their clicks count as Organic Search. Search Console includes them in its Web search totals.
| Source | In Google's AI Assistant definition? | Where to look |
|---|---|---|
| ChatGPT | Yes, named | AI Assistant channel, with chatgpt.com as Session source |
| Gemini, Copilot, Deepseek, and Grok | Yes, named | AI Assistant channel, by Session source |
| Perplexity | Not named | AI Assistant or Referral; add it to a custom group if it's in Referral |
| Claude | Not named | AI Assistant or Referral; add it to a custom group if it's in Referral |
| Google AI Overviews and AI Mode | Excluded | Organic Search in GA4, Web search totals in Search Console |
How do you build a custom channel group for AI traffic?
To track AI traffic beyond the assistants Google lists, copy the default channel group, add an AI channel above Referral, and match the AI tools and AI platforms by source with a regular expression. GA4 applies custom channel groups to your reports retroactively, so the new view covers your historical data too.
- In Admin, under Data display, open Channel groups. You need the Editor role or higher on the property.
- Select Create new channel group. GA4 starts the new channel group from a copy of the default group.
- Select Add new channel, name it AI assistants, and add a condition group: Source matches regex, with the pattern below. Then select Save channel.
- Select Reorder, drag the new channel above Referral, and select Apply. GA4 puts each visit in the first channel it matches, so the order decides where AI traffic lands.
- Select Save group, then choose the group as the primary dimension in the Traffic acquisition report.
A starting regex pattern for the five assistants in this post:
.*(chatgpt\.com|perplexity\.ai|claude\.ai|copilot\.microsoft\.com|gemini\.google\.com).*The backslash before each dot makes the pattern match a literal dot, and the vertical bars separate the domains. Add any other AI sources that show up in your Session source report. Google's help article on custom channel groups uses an AI assistants channel as its own example, with a broader pattern, and advises updating the regex when the list of assistants you want to measure changes.
Standard properties can have 2 custom channel groups and Analytics 360 properties 5, so plan which ones you need. If none are left, build a session segment for the same AI sources in an exploration instead. Segments work only in explorations, but they apply to past data too.
Check that it works
Ask an AI assistant a question that one of your pages answers, follow its link to your site in a private browser window, and check that the Realtime report in Google Analytics shows the visit with the assistant as its source. After a few weeks, compare your custom channel with the default AI Assistant channel. If the custom one is larger, the difference is AI-driven traffic from assistants that Google's list misses.
How much traffic do AI assistants send, and what does it do?
Check which assistants send visits, which pages those visits land on, and whether they turn into demo requests or sign-ups. Put landing pages and key events next to the AI channel to see all three.
A one-page monthly view for a B2B SaaS team covers:
- sessions and engaged sessions by assistant;
- the top landing pages for AI traffic, so you know which pages assistants link to;
- key events from AI visits, such as demo requests and sign-ups, next to the same figures for other channels;
- AI traffic as a share of all website traffic, month over month;
- anything that changed on the site that month, such as a robots.txt edit, a new page, or a pricing update.
To build it:
- In the Traffic acquisition report, keep your AI channel as the primary dimension and add Landing page as a secondary dimension.
- In an exploration, combine Session source, Landing page, and your key events, filtered to the AI channel or to the ai-assistant medium.
- Add the custom channel group to custom reports, or use it in audience conditions if you want to compare AI visitors with other visitors over time. Audiences only count from the day you change them, not retroactively.
Pick a date range of at least a full month, and read the numbers over months rather than days, since a few visits can swing the percentages on a B2B site. Turn on the comparison to the previous period in the date picker, so the monthly change sits in the same report. If AI traffic lands mostly on blog posts, check that those pages give a clear next step to the product or a demo.
What can't GA4 tell you about AI visibility?
Whether an assistant mentioned you without a click. Google Analytics only sees visits, so a buyer who reads your name in an AI answer and later finds you through a search engine or types your address shows up as organic traffic or direct traffic.
For Google's own AI features, Search Console is the closer view: Google includes traffic from AI Overviews and AI Mode in the Performance report's Web search totals.
To see the mentions themselves, check the answers: run a fixed set of buyer prompts on a schedule and record which assistants name you and which pages they cite. That is part of how AEO and GEO work is measured, alongside the referral traffic in GA4.
We report AI-referred visits for B2B SaaS clients as part of that work, so we have an interest in the topic.
Sources
- Google Analytics Help: Default channel group Accessed October 15, 2026
- Google Analytics Help: Custom channel groups Accessed October 15, 2026
- Google Analytics Help: Segment builder Accessed October 15, 2026
- Google Analytics Help: Analytics' list of sources and categories (spreadsheet) Accessed October 15, 2026
- OpenAI Help Center: Publishers and Developers FAQ Accessed October 15, 2026
- Google Search Central: AI features and your website Accessed October 15, 2026






