Where AI Visits Show in Analytics

A common question is simple: how much of our traffic comes from AI? The honest answer starts with a split. Visits from Google’s own AI features and visits from other AI assistants are recorded in different tools under different rules, and neither set of reports shows the whole picture. This article sets out what Google’s help pages say, as fetched in October 2026, and where we are drawing our own conclusions.

Search Console: AI features sit inside Web search data

Google’s AI features guide says sites appearing in AI Overviews and AI Mode are included in the overall search traffic in Search Console, reported in the Performance report within the Web search type. The Performance report overview describes that search type filter, with a text-based option and a multimodal option for searches that start with an image, as one of the ways to see data for web, image, video or news searches. The pages we read do not describe a separate AI-only report or filter, so we do not claim one exists.

How clicks, impressions and position are counted

The Search Console page on impressions, position and clicks gives methodology for both features. For AI Overviews, clicking a link to an external page counts as a click, standard impression rules apply, and an AI Overview occupies a single position in which all its links are assigned that same position. For AI Mode, a click on a link to an external page also counts, standard impression rules apply, and position follows the same methodology as a Search results page. If a user asks a follow-up question in AI Mode, they are essentially performing a new query, and the data from the new response is counted against that new query.

Two consequences follow, and both are our reading rather than Google’s words. First, because every link in an AI Overview shares one position, position data cannot show where within the answer your link appeared. Second, because each follow-up counts as a new query, query counts in AI Mode are not counts of conversations. The same page also says Search Console does not include data from Search Labs experiments, as those are still in active development.

Google Analytics: AI Overviews are Organic Search, assistants are separate

Google Analytics classifies sessions with its default channel group. Two of its definitions matter here. Organic Search is the channel for users arriving via non-ad links in organic search results, including Google’s AI Overviews and AI Mode. AI Assistant is the channel for users arriving from sources like ChatGPT, Gemini, Deepseek, Copilot or Grok, and Google says it excludes Google’s AI Overviews and AI Mode.

The consequence is that the AI Assistant channel is not a total for “AI traffic”. Clicks from Google’s AI features land in Organic Search, alongside everything else from Google results. Adding the AI Assistant channel to Search Console’s figures would mix two different measurements, so we keep them apart.

How a visit becomes “AI Assistant”

The default channel group page sets out the rule. The medium must be exactly “ai-assistant”, and Analytics sets the medium to “ai-assistant” and the campaign to “(ai-assistant)” if the referrer matches a list of AI assistants. The page we read does not publish that list.

Our reading is that the channel counts what Analytics can recognise from the referrer, not necessarily every visit that began in an AI tool. A visit that arrives without a referrer, or from a source not on the list, will not be classified here. The same page defines the channels such a visit may land in instead. Direct is the channel for users arriving via a saved link or by entering your URL, and its rule matches a source of “(direct)” with a medium of “(not set)” or “(none)”. Referral covers non-ad links on other sites or apps. Unassigned is the value Analytics uses when no other channel rule matches the event data. Which one an individual AI visit falls into depends on the data Analytics receives, and the documentation does not detail that.

Why the two tools never match

Google’s page on using Search Console and Google Analytics data says the two tools use different metrics and systems, so the data will not match completely. It recommends comparing Search Console clicks with Analytics sessions as the most comparable pair, and says they are calculated differently, so you will likely see different numbers. That applies to AI features as much as to anything else: a difference between the two is expected before any AI-specific effect is considered.

The honest limits

Put together, the documented position has clear edges. Analytics shows only people who clicked, so it cannot show how an assistant described you when nobody did. Search Console describes appearances in Google, so it says nothing about what ChatGPT, Gemini or Perplexity show. The AI Assistant channel depends on referrer matching. The Google pages we read give site owners no data on how often a page is cited in other assistants’ answers, and we found no documentation that lets anyone attribute a change in AI visibility to a specific site change with certainty.

Google also suggests, in its AI features guide, tracking conversions and time spent on your site in tools such as Google Analytics, a reminder that visit counts are not business results. A report that says “AI traffic is X” without these caveats is claiming more than the documentation supports.

Where this fits at Cultured Digital: reporting what can be observed

Measurement is one of the four areas of our AI & Search Visibility service, and its guide page, measurement, covers AI referral traffic in analytics, repeatable prompt sets and tracking, and reporting limits stated plainly. We separate what was observed from what is inferred, what is actionable and what is unknown, and a claim that cannot be evidenced does not go in the report.

That sits alongside the visibility review, which records what the tools actually said with prompts and dates. The same attitude applies to ordinary SEO reporting; see unavailable data versus zero. If you are not sure what your current setup can and cannot show, that is a reasonable question to put to us.

Where AI-driven visits show up in analytics, and where they do not