AI Referral Traffic in GA4: How to Report ChatGPT and Gemini Visits to Clients

Clients have started asking a new question in monthly calls: "Are we getting any visits from ChatGPT?" Until recently the honest answer was "probably, but it is buried in Referral", because Google Analytics 4 filed a click from a chatbot answer next to a click from any other website. That made these visits hard to find, easy to undercount and almost impossible to trend over time.

That changed on May 13, 2026, when Google added an AI Assistant channel to the GA4 default channel group. Visits from ChatGPT, Gemini and other assistants now have their own row, which means agencies can finally report them properly. This guide covers what the channel counts, what it leaves out, and how to present it so a client reads it as a growing source of qualified visits rather than a confusing new line in the monthly SEO client report.

Key takeaways

Since May 13, 2026, GA4 puts AI referral traffic in its own AI Assistant channel, with the medium ai-assistant.
The channel covers assistants such as ChatGPT, Gemini, Claude, Copilot, DeepSeek and Grok.
Google AI Overviews and AI Mode are excluded and still count as Organic Search.
Report AI sessions with engagement and conversions, compared period on period, not as a raw visit count.
Pair the GA4 numbers with AI visibility data so clients see mentions and clicks side by side.

What changed in GA4

GA4 now classifies sessions from AI assistants into a dedicated AI Assistant channel. According to Google's release notes, a session lands in this channel when its medium is ai-assistant, and GA4 sets that medium (with the campaign (ai-assistant)) when the referrer matches its list of AI assistants. In the channel order, AI Assistant sits after Organic Search and before Referral, so these visits no longer inflate the Referral total. The full rule is in Google's default channel group definitions.

Also read: Google Spam Update (September 2026): What Agencies Should Check and Tell Clients

Two related changes landed around it. On June 11, 2026, GA4 added a Source Group field that tidies messy source values and groups emerging sources such as ChatGPT and Perplexity. On September 9, 2026, it added Dashboards for building KPI views inside GA4. Both help analysts, but neither replaces a branded report the client actually opens each month. You can read every entry in Google's What's new in Google Analytics log.

What the AI Assistant channel counts, and what it misses

The channel definition names ChatGPT, Gemini, DeepSeek, Copilot and Grok, and Google's announcement also mentions Claude. If a user reads an answer in one of those tools and clicks a link to your client's site, that session should land in the AI Assistant channel. Perplexity is not named in the channel definition, so check where its visits land in your client's property before you tell anyone it is included.

What is excluded: Google AI Overviews and AI Mode. A click from an AI Overview is still Organic Search in GA4, so a client whose content is cited in AI Overviews will not see those clicks in the AI Assistant channel.

That exclusion is the part clients most often misread. Being mentioned in an AI answer and getting a click from it are two different measurements. GA4 only sees the click, and only from the assistants it recognises. It cannot tell you how often a brand appears in ChatGPT answers without a click, and it lumps AI Overviews clicks in with ordinary search. To show the whole picture you need mention data as well, which is what AI visibility tracking for agencies measures.

There is also the question of history. Google's documentation does not say the channel was applied to sessions before May 13, 2026. If you compare this quarter with the same quarter last year, the earlier period may show the same kind of visits under Referral. Compare periods that both fall after the change, or note the switch on the report so nobody reads a jump in AI visits as growth that is really a relabel.

How to find AI referral traffic in a client's GA4

Start with the standard acquisition reports and confirm the data is there before you design anything around it.

Open Traffic acquisition and make sure the primary dimension is Session default channel group. Look for the AI Assistant row.
Switch to Session source / medium and filter for ai-assistant. You will see which assistants sent visits, such as chatgpt.com / ai-assistant.
Check landing pages for those sessions. AI assistants tend to link to specific guides, pricing pages and comparison pages rather than the homepage.
Add key events to the view so you can see whether AI visitors convert, not just whether they arrive.

Also read: AgencyReportr vs AgencyAnalytics: Pricing, AI Tracking and Features Compared

If the AI Assistant row is missing, check three things before concluding there is no traffic. The report may be using a custom channel group that predates the new rule, in which case switch back to the default channel group. The date range may end before May 13, 2026. Or the site may genuinely have no AI referrals yet, which is common for small local businesses and is itself a useful finding to report.

How to report AI referral traffic so clients understand it

Raw numbers are the trap. A client who sees "AI Assistant: 14 sessions" next to "Organic Search: 2,300 sessions" will conclude AI does not matter. The useful story is in quality and direction, so build the section around four figures and one table.

Metric	What it tells the client
AI sessions	How many visits AI assistants sent this period, against the previous period
Engagement rate	Whether AI visitors read the page or bounce, compared with other channels
AI conversions	Leads, sign-ups or sales that started with an AI answer
Conversion rate	How valuable each AI visit is compared with search and social
Source / medium table	Which assistants sent visits, and to which pages

Then add the context only an agency can give. Explain that AI visits are small for most sites today but tends to be highly engaged, because the visitor already read an answer that recommended the client. Show which pages AI assistants link to, since those pages are the client's strongest assets in AI search. And put the mention data next to the click data, so the report answers both "are we being recommended?" and "are people clicking?". If you build these reports by hand, scheduled branded PDF reports keep the section consistent every month without rebuilding it.

In AgencyReportr, the SEO report already carries an AI assistant traffic section built from the client's GA4 property: AI sessions, engagement rate, AI conversions and conversion rate, with a source and medium table underneath. The same report includes AI visibility across ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews, so mentions and clicks sit on the same page under the agency's own brand, next to the daily keyword rank tracking and traffic they relate to.

Also read: AgencyReportr vs Whatagraph: Pricing, AI Tracking and Features Compared

Mistakes that make AI referral traffic look wrong

Promising AI Overviews clicks from this channel. Clients often assume the AI Assistant row includes Google's AI answers. It does not. Set that expectation in the first report, or the next question will be why their AI Overviews citations show no traffic.

Comparing across the May 13 change. A year-on-year comparison that crosses the date can show AI visits appearing from nowhere and Referral shrinking at the same time. Annotate the change, or compare only periods after it.

Reporting sessions without outcomes. Small session counts with no conversion data invite the client to dismiss the channel. Always pair sessions with engagement and conversions, even when conversions are zero, because a zero is also an answer.

Leaving it out because the number is tiny. A section that appears only when the number is large teaches clients that AI does not matter until it suddenly does. A steady, always-present section shows the trend from the first visit, which is exactly what a white label client report should do for a new channel the client keeps hearing about.

Show clients their AI traffic and AI mentions in one report

Connect a client's GA4 and Search Console, and AgencyReportr adds AI assistant traffic and AI visibility to a branded SEO report. Start with a $1 trial.

Start $1 trial See SEO pricing

7-day trial · Cancel any time

AI Referral Traffic FAQ

What counts as AI referral traffic in GA4?

Sessions that arrive from an AI assistant such as ChatGPT, Gemini, Claude, Copilot, DeepSeek or Grok. Since May 13, 2026, GA4 gives these sessions the medium ai-assistant and groups them in the AI Assistant channel of the default channel group, instead of mixing them into Referral.

Does the AI Assistant channel include Google AI Overviews?

No. Google's channel definition excludes AI Overviews and AI Mode, so a click from an AI Overview is still counted as Organic Search. Report AI Overviews separately, from Search Console data and AI visibility tracking.

Why does my client's GA4 show no AI Assistant channel?

Usually because no AI assistant sent a visit in the selected period, or because the report uses a custom channel group that has no AI Assistant rule. Switch the report to the default channel group, widen the date range past May 13, 2026, and check the source/medium report for ai-assistant.

Is AI referral traffic worth reporting if the numbers are small?

Yes, if you report it with context. Show sessions next to engagement rate and conversions, compare it with the previous period, and pair it with AI visibility data so the client sees both how often they are mentioned and how many people click through.

Can I compare AI referral traffic with months before May 2026?

Be careful. Google's documentation does not say the AI Assistant channel was applied to older sessions, so earlier months may show the same visits under Referral. Compare periods that both fall after May 13, 2026, or add the old AI referrer domains together by hand.