Where AI visits show up in GA4
GA4 sorts every session into a default channel. One of those channels is called AI Assistant. In Google's own definition it is the channel for users who arrive from sources like ChatGPT: a session lands there when its medium is ai-assistant, or when the referring site matches Google's list of AI assistants.
Inside the channel, the session source tells you which assistant sent the visit. In our checks the sources look like chatgpt.com, perplexity.ai, copilot.microsoft.com, gemini.google.com and claude.ai. Links people click inside ChatGPT answers often arrive tagged with utm_source=chatgpt.com, which GA4 reads as the source.
Not in this channel
Google's AI Overviews and AI Mode are not counted as AI Assistant. A click from an AI Overview arrives as a normal Google visit, in Organic Search, and Search Console does not split it out either.
The quick way: the Traffic acquisition report
- Open GA4 and pick the property.
- Go to Reports, then Acquisition, then Traffic acquisition.
- Set the date range. Use at least 28 days: AI visits are often small numbers that jump around day to day.
- Find the AI Assistant row in the table. If you do not see it, search the table for AI, or the property has had no AI assistant visits in those dates.
- Click the dimension menu above the first column and switch it to Session source / medium. Now each assistant has its own row.
- Add a comparison or a filter for Session default channel group equals AI Assistant to keep only these rows.
That answers how much and from where. It does not tell you which pages the AI sent people to, which is the more useful question. For that you need an exploration.
The full way: an exploration by assistant and landing page
- Go to Explore and start a Blank exploration.
- Under Dimensions add Session source, Landing page + query string and Session default channel group.
- Under Metrics add Sessions, Engaged sessions, Engagement rate and Key events.
- Drag Session source and then Landing page + query string into Rows, and the four metrics into Values.
- Add a filter: Session source matches regex, with the pattern in the box below.
- Name it something like AI visits by source and page, and save it.
The regex
chatgpt|openai|perplexity|copilot|gemini|bard|claude|anthropic|deepseek|meta\.ai|grok|mistral|you\.com|phind
Why a regex as well as the channel: it also catches older dates and any assistant Google has not added to its list yet. You can widen the pattern when a new assistant starts sending you visits.
Why some AI traffic still shows as Direct
GA4 can only name a source it is told about. When someone copies a link out of an AI answer and pastes it into a browser, or opens it from a desktop or phone app that sends no referrer, the visit arrives with no source. GA4 calls that Direct.
So the AI Assistant number is a floor, not the full count. A rise in Direct visits to deep pages, the kind nobody types by hand, at the same time as AI visits grow, is a hint that some of it is AI as well. It is a hint, not proof.
Doing this for many sites
An exploration lives in one property. If you run ten sites, you build and open it ten times, and you do it again every time you want a fresh read. We did exactly this for our own sites: a saved AI visits report in every one of our GA4 properties, opened one by one.
That is the job we built Site Insights for. Connect it to Claude or ChatGPT, then ask: How many visits did ChatGPT and Perplexity send each of my sites last month, and to which pages? The AI traffic tool returns the total, the share of all sessions, each assistant, the top landing pages and the weekly trend, with the change already worked out. The same tool covers all of your sites, and it also reads Search Console. Connecting it to Claude takes about two minutes.
What to do with the number
Look at the landing pages first. The pages AI already sends people to are the pages AI already trusts, and they tell you what kind of answer you get named in. Pages with traffic from Google but no AI visits at all are the gap.
Then check the engagement rate against your site average. Visitors who arrive from an AI answer have usually read about you already, so a low rate on those pages often means the page does not match what the AI said about it.
Getting named more often is a different job from measuring it. Our guide on how to get recommended by ChatGPT goes through what decides it.
Method. The GA4 steps and the AI Assistant channel definition were checked against Google's documentation and our own GA4 properties on 17 November 2026. Anything written as in our checks is what we saw in our own properties. GA4 menu names change from time to time; if a label differs in your property, look for the nearest match.