GA4 now sorts traffic from recognized AI assistants into an “AI Assistant” channel automatically, added on 13 May 2026. It can undercount, so also build a custom channel group with a “source matches regex” rule for chatgpt.com, perplexity.ai, claude.ai, gemini.google.com and other assistants, placed above Referral. Some AI visits still arrive as Direct.
Key takeaways
- Since 13 May 2026, GA4 gives sessions from recognized AI assistants the medium “ai-assistant”, the campaign “(ai-assistant)” and the channel “AI Assistant”. Google names ChatGPT, Gemini and Claude.
- Not every AI visit gets tagged. Search Engine Journal found ChatGPT sessions split across AI Assistant, Referral and Unassigned.
- A custom channel group fixes most of the gap. Standard properties get two custom groups, and they apply to reports retroactively.
- Google AI Overviews and AI Mode clicks are not in this channel. They count as Google organic search.
- Review the source list every quarter, because new assistants appear.
Does ChatGPT traffic show up in Google Analytics?
Yes, when the visit carries a referrer. A user clicks a cited link in ChatGPT, the browser passes chatgpt.com as the referrer, and GA4 records the session with that source. Since Google’s 13 May 2026 update, GA4 also labels recognized AI assistant sessions with the medium ai-assistant and groups them in the new AI Assistant channel. Before that update, these sessions sat under Referral.
Visits without a referrer are the problem. If a user copies a link out of ChatGPT and pastes it into a browser, or opens it from a desktop app that strips the referrer, GA4 sees no source and files the session as Direct.
Why does the AI Assistant channel undercount?
In a July 2026 analysis, Search Engine Journal’s Itamar Blauer found sessions with the source chatgpt.com spread across three channels in the same property:
| Where the session landed | Medium | Why |
|---|---|---|
| AI Assistant | ai-assistant | GA4 recognized the referrer and tagged it |
| Referral | referral | Sessions GA4 did not tag, including those from before the channel reached the property |
| Unassigned | (not set) | The medium was lost, so no channel rule caught it |
So the AI Assistant row alone gives you a floor, not the full number. A custom channel group based on the source catches all three.
How do I make a custom AI traffic channel in GA4?
Google’s custom channel group help page walks through the steps, and even uses AI assistants as its example:
- Go to Admin, then Data display, then Channel groups.
- Click Create new channel group. GA4 copies the default group so you keep every other channel.
- Name the group (for example “Channels with AI”).
- Click Add new channel, name it “AI”, and add a condition: Source, matches regex, then paste the pattern below.
- Click Reorder and move the AI channel above Referral. Google says traffic goes into “the first channel whose definition it matches”, so order decides the result.
- Save. The group applies to past data as well, so you can see history straight away.
Starting regex (channel definitions are not case sensitive):
^(.*\.)?(chatgpt\.com|openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|chat\.mistral\.ai|chat\.deepseek\.com|grok\.com)$How it works: ^(.*\.)? allows an optional subdomain such as www, the list holds each assistant’s host, and $ stops the pattern from matching look-alike domains such as chatgpt.com.example.net. It works whether GA4 checks the full value or part of it. Do not add a bare word like google or gpt, which would catch normal search traffic.
Standard GA4 properties can hold two custom channel groups (360 properties get five), so keep one for this and leave the other free.
Where to see AI traffic once it is set up
- Reports, Acquisition, Traffic acquisition: switch the primary dimension to your new channel group and look for the AI row.
- Landing pages: add a filter for the AI channel to see which pages AI assistants send people to. Those are the pages they cite.
- Key events: compare signups or trials from AI against organic search to see whether the traffic converts.
Worked example: our own GA4 data
We checked aiseogazette.com for the 30 days from 22 October to 20 November 2026, using the source and medium report:
| Source / medium | Engagement rate | What it shows |
|---|---|---|
| chatgpt.com / ai-assistant | 68% | GA4 tagged ChatGPT visits with the new medium automatically |
| google / organic | 56% | Our main search channel for comparison |
| (direct) / (none) | 46% | Includes our own visits and any AI clicks that lost their referrer |
| perplexity.ai (any medium) | No sessions | No Perplexity referrals recorded in this window |
Two lessons. First, the native channel works for ChatGPT on our property, and those visitors engaged more than Google organic visitors in this window. Second, the absence of Perplexity sessions is a result to act on, not a tracking error: it tells us to check which pages Perplexity cites for our topics. We report rates rather than raw session counts here, and the window is short, so treat it as one site’s snapshot, not a benchmark.
Why is some AI traffic still in Direct?
No GA4 setting can recover a referrer that never arrived. Expect some AI visits in Direct when users copy and paste links, open links from apps that strip referrers, or type your brand name after reading about you in an answer. That last case is often the biggest, and it is why brand searches in Search Console and direct visits to your homepage are worth watching alongside the AI channel.
What about Google AI Overviews and AI Mode?
Those clicks do not come from an AI assistant domain. Google says traffic from AI Overviews and AI Mode is included in your overall search traffic in Search Console under the Web search type, and in GA4 it arrives as google / organic. There is no separate GA4 channel for it.
Where AI gets it wrong
Many AI-written guides still say “GA4 cannot track ChatGPT traffic” or tell you to build a regex from scratch as the only option. Both are out of date since the May 2026 update. The opposite mistake is trusting the native channel as the full number. Use both: the AI Assistant channel for a quick view, and your custom group for the full count.
Frequently asked questions
Is the AI Assistant channel turned on for every GA4 property?
Google added it to the Default Channel Group with no setup needed. If you do not see it yet, you may simply have no recognized AI sessions in the date range.
Can I track which ChatGPT answer sent a visitor?
No. GA4 sees the source domain, not the prompt or answer. Use the landing page report to see which pages AI assistants link to.
Will the custom channel group change my old reports?
Google says custom channel groups can be applied to reports retroactively, and your default group stays as it was.
How often should I update the regex?
Every quarter, or when a new assistant starts sending traffic. Check the Referral report for new AI domains and add them to the list.
Sources
- Google Analytics Help, What’s new in Google Analytics (13 May 2026 entry)
- Google Analytics Help, Custom channel groups
- Google Analytics Help, Default channel group
- Search Engine Journal (July 2026), GA4’s AI Assistant channel undercounts your AI traffic
- Google Search Central, AI features and your website
Related: LLM visibility, AI visibility tools and AI search statistics.
Part of our SaaS SEO guide for AI tools. More guides in Tool Owner Resources.
