Satelo / AI search / How to Track ChatGPT and AI Traffic in GA4

Ai search

How to Track ChatGPT and AI Traffic in GA4

To check ChatGPT traffic in GA4, open Reports, then Acquisition, then Traffic acquisition, and look for the AI Assistant row in the session default channel group: since May 2026 Google Analytics sorts visits from recognized AI assistants there automatically. For assistants GA4 doesn't recognize, or for a cleaner breakdown by tool, add a custom channel group with a regex rule. This guide covers both, plus where AI visits still hide and what the numbers can and can't tell you.

Published: 2026-10-16 · 7 min read · Satelo

How to Track ChatGPT and AI Traffic in GA4

What changed in 2026: GA4 now has an AI Assistant channel

For a long time, visits from ChatGPT and other assistants landed in Referral (when the browser passed a referrer) or Direct (when it didn't), and the only way to separate them was a custom regex. That's no longer the whole story.

In its release notes dated May 13, 2026, Google Analytics announced a new AI Assistant channel in the default channel group, naming chatbots like ChatGPT, Gemini and Claude. Three things happen when the referrer matches a recognized AI assistant:

Medium is set to ai-assistant.
Default channel group is set to AI Assistant.
Campaign is set to (ai-assistant).

The default channel group documentation describes the channel as visits from sources like ChatGPT, Gemini, Deepseek, Copilot or Grok, and states that it excludes Google's AI Overviews and AI Mode. Google doesn't publish the full list of recognized assistants on that page, which is why a custom group is still worth setting up (see below).

Step 1: Check the built-in AI Assistant channel

In GA4, go to Reports → Acquisition → Traffic acquisition.
Make sure the table's primary dimension is Session default channel group.
Find the AI Assistant row. Click the "+" next to the dimension and add Session source as a secondary dimension to see which assistants sent the visits.
Set a date range that starts after mid-May 2026 if you want a clean comparison. Before the channel existed, the same kind of visits sat in Referral or Direct, so a range that crosses the change mixes two classifications.

If you see no AI Assistant row at all, that may simply mean no recognized assistant sent a visit in that period. Small sites often see very few, which is normal.

Step 2: Do a quick source/medium check for assistants GA4 misses

Some assistants may not be on Google's list, and new ones appear often. A two-minute check:

In the same Traffic acquisition report, switch the primary dimension to Session source / medium.
In the search box above the table, type parts of known assistant domains one at a time: chatgpt, openai, perplexity, gemini, copilot, claude, deepseek, grok.
Anything that shows up with medium referral instead of ai-assistant is AI traffic that the default channel isn't catching.

If that list is empty, the built-in channel may be enough for you. If it isn't, build a custom group.

Step 3: Build a custom channel group (copy-paste regex)

Custom channel groups let you define your own channels with rules, and per Google's custom channel groups help page they apply to reports retroactively. The same page lists the limits: standard properties can have 2 custom groups besides the predefined one, and each group can contain up to 50 channels.

Go to Admin → Data display → Channel groups.
Click Create new channel group. GA4 starts you with a copy of the default group, so the built-in AI Assistant channel is already in it.
Name it, for example "Channels with AI detail."
Click Add new channel, name it "AI assistants (extended)," and set the condition: Source → matches regex → paste the pattern below.
Add a second condition with OR: Medium → exactly matches → ai-assistant. This keeps everything the built-in channel already recognizes.
Click Reorder and drag your new channel above Referral (and above the built-in AI Assistant channel, if you want one combined row). Save.

Regex for the Source condition (domains as of October 2026; add new ones as they appear):

Order matters. Google's help page says traffic is included in the first channel whose definition it matches, given the current order. If Referral sits above your AI channel, Referral wins.

A note on Google's example regex

Google's help page includes its own AI assistants example. It works as a starting point, but its first alternative, ^.*ai, matches any source containing the letters "ai," which can pull in unrelated sources such as email or "daily" newsletters. Listing the actual domains, as above, is more predictable. Whichever pattern you use, check the source list under your new channel after a few days and fix anything that doesn't belong.

Step 4: Analyze AI visits in Explorations

Standard reports show volume. Explorations show behavior. A simple setup:

Go to Explore → Free form.
Import dimensions: Session default channel group (or your custom group), Session source, Landing page + query string.
Import metrics: Sessions, Engaged sessions, Engagement rate, Key events.
Rows: Landing page. Columns: channel. Filter: channel exactly matches AI Assistant (or your extended channel).

Now you can answer the useful questions: which pages AI tools send people to, whether those visitors engage, and whether any of them convert. Pages that keep showing up are the ones AI tools cite; keep them accurate and current.

Where AI traffic still hides

Even with a dedicated channel, GA4 will undercount AI-driven visits. Plan for that instead of trusting a single number.

Situation	Where it shows up in GA4	What you can do
Link opened with no referrer passed (some apps and privacy settings strip it)	Direct	Nothing reliable; treat Direct growth after AI mentions as a hint, not proof
Google AI Overviews and AI Mode	Organic Search (excluded from AI Assistant by Google)	Use Search Console for Google's AI features
Assistant not on Google's list	Referral	Custom channel group with regex
User reads the AI answer, later types your URL or searches your brand	Direct or Organic Search	Watch branded search queries in Search Console
Ad blockers or rejected consent	Not recorded, or Direct	Accept a gap; compare with server logs if you need a sanity check

Google's article on (direct) / (none) traffic lists the general causes: links without UTM parameters, redirects or shorteners that strip source data, typed URLs and links in documents, and ad blockers.

A related point: AI crawlers fetching your pages are a different thing from people clicking through from an answer, and this report is about the people. To see whether assistants can reach your site at all, check your robots.txt and server logs (our guide on AI crawlers and robots.txt explains which bot does what).

Step 5: Use UTMs where you control the link

You can't tag links that AI tools generate, but you can tag links you place yourself, and those links are often what AI tools pick up and repeat:

Links in your profiles on directories, communities and partner sites.
Links in your newsletter, documentation or downloadable PDFs (otherwise those land in Direct).
Links you share in AI-indexed places such as public forums, if the platform allows it.

Use a consistent scheme, for example utm_source=partner-name&utm_medium=referral&utm_campaign=profile, so these visits don't get confused with assistant clicks. Don't tag internal links on your own site; that overwrites the original source.

What to do with the numbers

Track the trend, not the absolute. Since part of AI traffic hides in Direct and Organic, the visible AI channel is a floor. Month-over-month direction is more meaningful than the raw count.
Look at landing pages. The pages AI assistants send people to tell you what they trust you for. Improve those first: clear answers near the top, sources, up-to-date facts.
Compare engagement. If AI visitors engage more or less than organic visitors on the same pages, that tells you whether the AI answer set the right expectation.
Connect it to visibility work. If you get no AI traffic at all, the issue is usually upstream: being crawlable, indexed and cited. Start with our guides on getting indexed by ChatGPT and getting cited by ChatGPT.

Checklist

Traffic acquisition report checked for the AI Assistant row, with Session source as a secondary dimension.
Source / medium searched for assistant domains still classed as referral.
Custom channel group created, AI channel placed above Referral, OR condition on medium ai-assistant.
Free-form exploration saved: AI channel by landing page, with engagement and key events.
UTMs on links you control; none on internal links.
Date ranges compared only after mid-May 2026 for the built-in channel.

What to do next

GA4 shows how many people arrive from AI tools, but not how your site looks to the systems and people deciding whether to reference it. Run your domain through Satelo's free site check to see a 0 to 100 Quality Score built mostly from open data, with the evidence behind each number, in about 30 seconds. It's a quick way to spot weak points (indexing, traffic signals, trust basics) before you work on AI visibility. For more on traffic measurement without paid tools, see how to check website traffic for free.

FAQ

How do I see ChatGPT traffic in Google Analytics 4?

Open Reports, Acquisition, Traffic acquisition and look for the AI Assistant row in the session default channel group. Add Session source as a secondary dimension to see ChatGPT separately. Google added this channel in May 2026.

Why does ChatGPT traffic show as referral or direct in GA4?

Before May 2026, GA4 had no AI channel, so assistant visits with a referrer were classed as Referral. Visits without a referrer, for example from some apps, still land in Direct, because GA4 can't tell where they came from.

Does the GA4 AI Assistant channel include Google AI Overviews?

No. Google's documentation says the AI Assistant channel excludes Google's AI Overviews and AI Mode. Those clicks are counted under Organic Search.

What regex should I use to track AI traffic in GA4?

List the assistant domains explicitly, for example a Source condition matching chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com and claude.ai, and place the channel above Referral. Review the matched sources after a few days.

Do custom channel groups work on historical data?

Yes. Google says custom channel groups can be applied to reports retroactively. Audiences are the exception: changes there apply only going forward.

Is GA4 AI traffic data accurate?

It's a floor, not a full count. Visits without a referrer, later branded searches and Google's AI features all land in other channels. Use it for trends and landing-page insights, not as an exact total.

Satelo team
We build Satelo, a network where small websites promote each other. About us