ChatGPT traffic in Google Analytics 4 sits in the default AI Assistant channel, live since 13 May 2026: Reports, Acquisition, Traffic acquisition, the AI Assistant row, then the Session source/medium dimension. On visilay.com, from 29 July to 26 October 2026, that channel recorded 54 sessions, 9.3% of all measured sessions, but chatgpt.com turned up in our data under four different mediums.
So the AI Assistant row is where you start. It is not the total of your AI traffic.
Search Console taught you to expect stable numbers. Take Sunscape, which develops solar plants across Italy: in the six months from March 2026 its organic impressions went from 329 to 5,809 a month, and that curve reads the same today as it will in a year (the full story is in how long SEO takes).
AI traffic doesn't behave like that. The channel is five months old, labels the same source differently from one visit to the next, and leaves part of the clicks out.
The mistakes we see most often when a business opens GA4 to "see how much ChatGPT sends us":
- stopping at the AI Assistant row and ignoring chatgpt.com visits left in Referral, Unassigned or Organic Search;
- comparing May with October without knowing when the channel went live on their own property;
- counting key events instead of sessions, and reporting twice the enquiries they actually got.
Most guides show you where to click. Very few show what is inside a real property. We opened ours.
In this article:
- the path in GA4, with the channel rules taken from Google's own help pages;
- visilay.com's data: channels, sources, landing pages, countries and enquiries, in a table you can cite;
- why chatgpt.com lands in four channels and how to get the lost visits back;
- the regex for Perplexity and Claude, which the native channel doesn't guarantee;
- what GA4 can't see, from AI Overviews to cookie consent.
Let's start with the clicks.
Where to find ChatGPT traffic in GA4 (three clicks and one dimension)
ChatGPT traffic is in the Traffic acquisition report, on the AI Assistant row of the default channel group. Google announced it in the Analytics release notes of 13 May 2026: when the referrer matches a recognised assistant, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant).
The path:
- Reports, Acquisition, Traffic acquisition (described in Google's help page);
- primary dimension Session default channel group, AI Assistant row;
- secondary dimension Session source/medium, to split ChatGPT, Gemini and Copilot;
- a date range that starts after the channel went live on your property, not before.
Which assistants are included?
Google doesn't publish the full list. The traffic-source dimensions page gives ChatGPT, Gemini, Deepseek, Copilot and Grok as examples and refers to "a list of AI Assistants". Perplexity isn't among the examples. Claude was in the May announcement and isn't among today's examples.
The same page says something many people skip: Google's AI Overviews and AI Mode are NOT in the AI Assistant channel. They count as Organic Search, mixed in with clicks from the classic results.
On visilay.com the first AI Assistant session is dated 14 August 2026, three months after the announcement. On 15 May, two days after it, a visit from chatgpt.com was still landing in Unassigned.
What we found in visilay.com's GA4 (90 days, 54 AI sessions)
In the 90 days from 29 July to 26 October 2026 visilay.com's AI Assistant channel recorded 54 sessions, 9.3% of the measured total and 22 AI sessions for every 100 organic sessions. We pulled the data on 27 October 2026 from the site's GA4 property, Italian and English versions together.
| GA4 channel | Sessions | Share of sessions | Engaged sessions |
|---|---|---|---|
| Organic Search | 242 | 41.6% | 67.8% |
| Direct | 214 | 36.8% | 38.8% |
| AI Assistant | 54 | 9.3% | 63.0% |
| Paid Search | 36 | 6.2% | 50.0% |
| Referral | 27 | 4.6% | 59.3% |
| Unassigned | 6 | 1.0% | 0% |
| Organic Social | 3 | 0.5% | 100% |
Inside the 54 AI sessions:
- chatgpt.com sent 48, 89%; Gemini 5, Copilot 1;
- Perplexity and Claude: zero over the whole period, in any channel;
- 44 of the 54 sessions came in October: from 1 to 26 October the channel was 11.9% of sessions, against a single session in the whole of August;
- visitors came from 14 countries: Italy 17, United Kingdom 15, India 8.
And where do they land?
On 37 different pages, none with more than 3 sessions. Not the AI pages: our guide to AI visibility didn't get a single visit from the channel. They are vertical guides, such as SEO for therapists, restaurant SEO, Google Ads for restaurants, Shopify SEO, plus the Macropix and Valore Solare project pages. 32 sessions landed on the English site, 17 on the Italian one.
In plain terms: ChatGPT sends people to the page that answers a narrow question, not to the page about the topic in general.
Why chatgpt.com ends up in four different channels (and how many visits go missing)
GA4 assigns a channel by looking at source and medium together: if the source is chatgpt.com but the medium isn't ai-assistant, the visit goes somewhere else. Between March and October 2026, on visilay.com, chatgpt.com showed up with four mediums.
| Source / medium | Channel assigned by GA4 | When we saw it | Sessions |
|---|---|---|---|
| chatgpt.com / (not set) | Unassigned | 4 March and 15 May 2026 | 2 |
| chatgpt.com / referral | Referral | 3 May 2026 | 1 |
| chatgpt.com / ai-assistant | AI Assistant | from 14 August 2026 | 48 |
| chatgpt.com / organic | Organic Search | 21 October 2026 | 2 |
The first two rows are history: before the channel reached the property, ChatGPT was just another referral, or a source with no medium. The channel doesn't reclassify old data, so a chart from January to October shows "growth" that is partly just a change of label.
The last row is the sneakiest. Two visits on 21 October came from chatgpt.com but GA4 counted them as organic search, next to Google and Bing. Over the 90 days they are 4% of the ChatGPT visits we could identify: few, but you won't see them in the AI Assistant report.
We're not the only ones. In Search Engine Journal, in July 2026, Itamar Blauer documented the same split between AI Assistant, Referral and Unassigned. And Target Internet, on three months of its own site's data, counted 490 sessions in the channel against 594 real visits from assistants: 18% fewer, and 52% fewer for Perplexity.
How do you spot it on your own site?
In the Traffic acquisition report remove the channel filter and search for "chatgpt" in Session source/medium. Every row that doesn't end in ai-assistant is AI traffic counted somewhere else.
A miscounted channel moves budget to the wrong place.
You've just seen chatgpt.com split across four rows. If your monthly report reads only one of them, you undercount AI, inflate Direct and choose which pages to work on from a number that doesn't hold up. We rebuild the channels on your property, line them up with Search Console and tell you how much of each number is measured and how much is estimated.
Book a strategy callHow to add Perplexity and Claude to GA4 (a custom channel group with a regex)
To count the assistants the native channel doesn't guarantee, you need a custom channel group with an "AI" channel defined by a regex on the source. According to Google's help page on custom channel groups, a standard property can have 2 on top of the default one (5 on 360 properties), and they apply to data already collected.
That "data already collected" is the reason to do it today: the custom group recovers the March and May visits that the native channel leaves in Referral and Unassigned.
- Admin, Data display, Channel groups, then "Create new channel group";
- add an "AI" channel with two conditions joined by OR: session medium exactly matches ai-assistant, or session source matches the regex below;
- move the channel above Referral and Organic Search: GA4 assigns each visit to the first channel it matches, in list order;
- save, then pick the new group as the dimension in Traffic acquisition.
The regex we use, built on the sources in our own data plus the main assistants:
(.*\.)?(chatgpt\.com|openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|deepseek\.com|grok\.com|mistral\.ai)Three tips. No short tokens like "gpt" or "ai": they catch domains that have nothing to do with it. Add new sources as they appear in the report. And review the list every quarter: copilot.com, in our data, isn't the same domain as copilot.microsoft.com.
A longer version, with Meta AI, You.com and Phind, is in the GA4 section of our AI visibility guide.
The explorations to save: pages and enquiries (count sessions, not events)
To judge what AI traffic is worth you need two free-form explorations filtered on the AI channel: landing page with sessions and engaged sessions, then sessions with a key event. The second is the one everybody gets wrong.
Over our 90 days the AI Assistant channel shows 2 key events. That looks like two enquiries.
It's one.
A single session, arriving from ChatGPT on an English guide, sent the contact form. Our form fires two events marked as key, form_contatto_en and generate_lead, and GA4 counts both. If your tracking is built the same way, count enquiries as sessions with a key event, never by adding up events.
Counted properly, the share of sessions with an enquiry is 1.9% for the AI channel and 1.2% for organic search. So AI converts better? With one session in 54 you can't tell: one enquiry more or less flips the comparison. Quality reads better in engaged sessions, 63% against 67.8%, and you only confirm it with months of data.
We set up form and key event tracking this way in our tracking service. The problem is the same one we found with attribution models: with small numbers, a counting choice weighs more than the channel.
What GA4 can't see in AI traffic (AI Overviews, apps and consent)
GA4 only sees visits that arrive with a recognisable referrer and with consent to be measured. Three blocks of traffic stay out, and no regex brings them back.
- Clicks from AI Overviews and AI Mode. For Google they are organic search, in GA4 and in Search Console too, where the Search Central documentation places them in the Performance report under the "Web" search type. Since 31 August 2026 Search Console also has a generative AI report, but it shows impressions only: no clicks.
- Visits with no referrer. A link opened from the ChatGPT app, pasted into an email or typed by hand arrives as Direct. Direct is 36.8% of visilay.com's sessions: how much AI is inside it, GA4 won't say.
- Visits from people who refuse cookies. GA4 counts the sessions the banner lets it measure. How the modelled part works is in our guide to Consent Mode v2.
Then there's the case no analytics tool records: someone reads your name in the answer, doesn't click, and searches for you on Google two days later. That visit will show up as branded organic search. It's the mechanism behind zero-click searches, moved into a chat window.
For AI Overviews, the traffic side is covered in our piece on the impact of AI Overviews on SEO. For AI Mode, what you can track and with which tools is in our guide to tracking Google AI Mode.
Traffic measures clicks, not citations (what it means for AI visibility)
GA4 tells you who clicked through from an AI answer, not how often your brand appeared in answers. They are two different measures: the first is traffic, the second is visibility, and you measure it by asking ChatGPT, Gemini and Perplexity the same questions and counting mentions and cited sources.
The GA4 data does say something about which pages get used as a source and then clicked. On our site they are vertical guides with numbers for one specific sector, not the general pages. That matches what we see in our tests on AI citations and brand mentions: a page that answers a narrow question, with a figure you can't find elsewhere, has more chances of becoming the link under the answer. No guarantees: answers change from one run to the next, as we measured in our test on how accurate AI visibility data is.
For the part GA4 can't see we built ScryRank, the monitoring tool developed by Visilay: it asks the same questions on ChatGPT, Claude, Gemini, Perplexity and AI Overviews and keeps the history of mentions and citations. Put next to the AI channel in GA4, it tells you whether more citations bring more visits. We work on the pages in our GEO service and on measurement in AI Monitoring.
The 5 lines for your monthly report (and where to find them)
A report on AI traffic fits in five lines, as long as each one says where the number comes from. This is the table we start from.
| Report line | Where it comes from | What it tells you |
|---|---|---|
| Sessions from the AI channel (native + custom) | GA4, Traffic acquisition, custom group | How many clicks arrive from assistants with a referrer |
| AI sessions per 100 organic sessions | GA4, AI channel divided by Organic Search | The weight of AI against Google, net of seasonality |
| Landing pages from the AI channel | GA4, free-form exploration | Which pages the engines use and people click |
| Sessions with a key event | GA4, exploration, sessions with key event metric | Real enquiries, without double counting |
| Impressions in Google's AI features | Search Console, generative AI report | Presence in AI Overviews and AI Mode, without clicks |
Which visibility metrics to put next to traffic is in AI visibility metrics; how to lay it all out for a business or an agency with several clients is in the AI visibility report guide. The full picture of channels, with their weight on three Italian sites, is in our article on website traffic sources.
FAQ on ChatGPT traffic in GA4
Yes. Since 13 May 2026 GA4 has a default AI Assistant channel: you'll find it under Reports, Acquisition, Traffic acquisition. The Session source/medium dimension separates chatgpt.com from Gemini and Copilot. It only counts visits with a recognised referrer.
No. According to Google's Analytics help, AI Overviews and AI Mode stay in Organic Search. Their clicks appear in Search Console, in the Performance report together with web search; the generative AI report only shows impressions.
It depends: Google doesn't publish the full list of assistants and today gives ChatGPT, Gemini, Deepseek, Copilot and Grok as examples. To be sure you count Perplexity and Claude, create a custom channel group with a regex on the source, placed above Referral.
No. Visits from before the channel went live on your property stay in Referral or Unassigned. On visilay.com the first session in the channel is dated 14 August 2026. A custom channel group, on the other hand, applies to data already collected.
No. GA4 receives the source and the landing page, not the question asked in ChatGPT. To know which questions you appear for, you need a tool that asks AI engines the prompts and records mentions and citations.
In short
The AI Assistant channel has existed since 13 May 2026.
It isn't retroactive and doesn't include AI Overviews or AI Mode.
chatgpt.com can land in four channels: look for it in the source.
Perplexity and Claude need a regex, placed above Referral.
Count enquiries as sessions, not events.
One last thing, which our own data surprised us with. The useful question isn't "how much traffic does ChatGPT send us", which stays small on almost every site. It's which pages it lands on: that's the only place where GA4 shows you, from the outside, which of your pages AI engines picked as a source. If they're pages you'd never have put in your content plan, the plan needs rebuilding from there.
If you'd like to do it together on your property, get in touch. Speak soon!
