Guide · 9 min read
ChatGPT traffic in GA4: how to find it, group it and measure it
Finding ChatGPT traffic in GA4 takes a few minutes once you know where to look, and grouping it properly takes a few more. This tutorial walks through the reports that already show it, the AI Assistant channel Google added in 2026, a custom channel group that also covers Perplexity, Claude and Copilot, an exploration for landing pages and key events, and the limits you should know before you report any number.

What GA4 can and cannot tell you about AI assistants
GA4 sees a visit from an assistant only when a person clicks a link in an answer and lands on your site. It does not see the answers where you were mentioned without a click, and it does not see answers where a competitor was recommended instead of you.
So treat this data as one half of the picture. The other half, what assistants actually say about your brand, needs a separate method, which we cover in how to measure AI visibility. That guide touches on GA4 briefly; this one goes step by step.
Step 1: find ChatGPT traffic in GA4 in the reports you already have
Open Reports, then Acquisition, then Traffic acquisition. The table defaults to Session primary channel group. Change the primary dimension to Session source / medium using the dropdown above the first column.
Now type chatgpt in the search box above the table. Depending on the date range and your property, you may see rows such as these:
- chatgpt.com / referral, typical for visits recorded before GA4 added its AI channel.
- chatgpt.com / ai-assistant, the medium GA4 assigns now when it recognises the referrer as an AI assistant.
- chatgpt.com / (not set) or other combinations, which can appear when a link carries a UTM source but no medium.
The source value chatgpt.com is no accident. OpenAI's publisher FAQ states that ChatGPT adds utm_source=chatgpt.com to the links it shows in search answers, so publishers can identify that traffic in analytics tools. That tag only works if OAI-SearchBot can crawl your pages, which is covered in our guide to robots.txt for AI bots.
Repeat the search with perplexity, gemini, copilot and claude. Write down every exact source value you see. You will need that list in step 3.
Step 2: check the built-in AI Assistant channel
On 13 May 2026 Google announced a new AI Assistant channel in the Default Channel Group. According to Google's default channel group definitions, visits get the medium ai-assistant when the referrer matches a list of recognised AI assistants, and the description names ChatGPT, Gemini, Deepseek, Copilot and Grok as examples. Google's AI Overviews and AI Mode are explicitly excluded and stay in Organic Search.
To see it, switch the primary dimension back to Session primary channel group and look for an AI Assistant row. If you have one, that is the quickest view of ChatGPT traffic in GA4 with no setup at all.
Two caveats at the time of writing. Google has not published the full list of referrers it recognises, so you cannot be sure which smaller assistants are included. And the default channel group cannot be edited, so you cannot add a source that Google misses. Both are reasons to build your own group as well.
Step 3: build an AI assistants custom channel group
A custom channel group lets you decide exactly which sources count as AI assistants. Google's help page on custom channel groups says they apply retroactively to existing reports, which means you can compare months before and after May 2026 with one consistent definition.
- Go to Admin, then Data display, then Channel groups. You need the Editor role or higher.
- Click Create new channel group. Start from a copy of the default group so you keep every other channel. Name it something clear, for example Channels with AI.
- If the copy already contains an AI Assistant channel, edit that one instead of adding a duplicate. Otherwise click Add new channel and name it AI assistants.
- Add a condition: Source, matches regex, and paste the expression shown below.
- Add a second condition joined with OR: Medium, exactly matches, ai-assistant. This keeps everything Google recognises, plus your own list.
- Save the channel, then save the group.
A starting regex for the Source condition: .*(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai).*
The dots are escaped so they match a literal dot, and the leading and trailing .* let the pattern match values such as www.perplexity.ai. Standard properties can have two custom channel groups, so use them deliberately.
The referrer domains, assistant by assistant
Each domain in the regex is the web address where that assistant runs. Whether a visit arrives with that value depends on the browser, the app and the link, so confirm each one against the list you wrote down in step 1.
- ChatGPT: chatgpt.com, which OpenAI also uses as the utm_source value. Older sessions may show chat.openai.com, the previous address.
- Perplexity: perplexity.ai, sometimes recorded as www.perplexity.ai.
- Gemini: gemini.google.com. Do not add a bare google pattern, or you will pull in organic search.
- Microsoft Copilot: copilot.microsoft.com for the consumer version. Copilot inside Microsoft 365 or Edge may arrive with other values; add them only after you see them in your data.
- Claude: claude.ai.
Google's own example regex on the custom channel group page is much broader. It includes patterns such as .*gpt.* and an alternative that matches any source containing ai, which also catches values like email or mail. We prefer a short, explicit list that you extend when your data shows a new source.
Step 4: place AI assistants above Referral
GA4 assigns each session to the first channel in the list whose conditions it matches. If Referral sits above your new channel, chatgpt.com / referral sessions will be counted as Referral and never reach AI assistants.
- Open your custom group from Admin, Channel groups.
- Click Reorder.
- Drag AI assistants above Referral. Google notes you can also place it above Organic Search.
- Click Apply and save.
Then go back to Traffic acquisition, click the dropdown on the first column and choose your custom group. You now have a single row for assistant traffic, which you can compare with Organic Search or Paid Search over any date range.
Step 5: an exploration for landing pages and key events
The acquisition report tells you how much ChatGPT traffic in GA4 you get. An exploration tells you where it lands and what it does. Open Explore and start a Free form exploration.
- Under Dimensions, import your custom channel group, Session source / medium and Landing page + query string.
- Under Metrics, import Sessions, Engaged sessions, Key events and Session key event rate. Add Total revenue if you sell online.
- Drag Landing page + query string into Rows and Sessions, Key events and Session key event rate into Values.
- Add a filter on your custom channel group: exactly matches AI assistants.
- Add Session source / medium as a second row dimension, or as columns, to split ChatGPT from Perplexity and the rest.
Look for three patterns. Pages that receive assistant traffic but no organic traffic are pages assistants value on their own. Pages with high traffic and a low key event rate may answer the question but fail to offer a next step. And pages missing from the list entirely may be ones you expected to be cited and are not, which is worth checking with prompt research.
Key events: decide what counts before you judge the channel
Key events are what GA4 now calls the events you mark as important, previously called conversions. Without them, every channel looks equal and you can only compare sessions.
Mark the actions that represent real interest: a form submission, a booking, a purchase, a click on your phone number. In Admin, Data display, Events, click the star next to an existing event. Google's help says you need the Editor role, and standard properties can have up to 30 key events.
Visitors from assistants often arrive with a specific question already answered, so their behaviour can differ from search visitors. Compare the key event rate per channel rather than raw totals, and look at several months before drawing conclusions, since volumes are usually small.
Limits of ChatGPT traffic in GA4
Every number you get from this setup is a floor, not the full count. Keep these limits in mind when you present it:
- Visits from mobile and desktop apps can arrive without a referrer. If the link also lacks a UTM tag, the session lands in Direct and no rule can recover it.
- Copied and pasted links behave the same way. A user who copies your URL from an answer and pastes it into a browser is recorded as Direct.
- Clicks from Google AI Overviews and AI Mode are counted as Organic Search. GA4 cannot separate them from ordinary Google results. See how to appear in AI Overviews and our guide to Google AI Mode.
- Referrer lists change. Assistants launch apps, rename domains and change how links open. Review your source list every few months.
- Being cited without a click leaves no trace in GA4. A brand can gain visibility in answers while this channel stays flat.
Looker Studio: an optional dashboard
If you report to someone who does not open GA4, Looker Studio can show the same data. Use the Google Analytics connector, add a time series of sessions by your custom channel group and a table of landing pages filtered to AI assistants. Keep the regex in the GA4 channel group, not in the dashboard, so both always agree.
What to do with the numbers
ChatGPT traffic in GA4 is a useful signal, not a verdict. Rising sessions to a page tell you assistants trust it; a high key event rate tells you the visitors they send are worth having. Flat numbers do not prove you are invisible, given the limits above.
Pair this data with a record of what assistants say for the questions your buyers ask. Together they show both sides: whether you are recommended, and whether those recommendations turn into business. That is the loop a GEO strategy is built on, and a free GEO audit is a quick way to see where you start.
Frequently asked questions
Does GA4 show ChatGPT traffic automatically?
Partly. Since May 2026 GA4 assigns the medium ai-assistant and an AI Assistant channel to visits whose referrer it recognises, with ChatGPT among the examples Google names. Visits without a referrer still land in Direct, and Google has not published its full list of recognised sources.
Why does chatgpt.com appear as a source in my reports?
OpenAI says ChatGPT adds utm_source=chatgpt.com to links in its search answers, and the referrer domain is also chatgpt.com. Either way, GA4 records chatgpt.com as the session source for those visits.
Do I still need a custom channel group if the AI Assistant channel exists?
It is optional but useful. A custom group lets you include sources Google may miss, keep one definition across older and newer data, and decide whether to place the channel above Organic Search as well as Referral.
Can I see traffic from Google AI Overviews in GA4?
No. Google's channel definitions place AI Overviews and AI Mode in Organic Search, and GA4 has no dimension that separates those clicks from ordinary results.
How much ChatGPT traffic in GA4 is normal?
There is no reliable benchmark, and volumes vary widely by sector and by how often assistants cite a site. Compare your own trend month to month and look at the key event rate, which says more than raw sessions.


