Chapter 12
Measuring what nobody measures properly (yet)
Table of contents
"How much AI traffic do we actually have?" is a question that really breaks down into three different questions. Most store owners answer it with the tool that can only see one of them.
One question that is really three:
Am I being read at all? A crawler question, not a traffic question. The answer is in the server logs.
Does AI send me visitors? Partly measurable in GA4 – with four limitations that distort the picture.
Am I being mentioned without a click? No click, no referrer, no event. Not directly measurable with today's tools.
The consequence: you need three signal sources – server logs, GA4 including your own channel group, and the acceptance that part of it remains invisible.
Question 1: Am I being read at all?
This is not a traffic question but a crawler question. Search the server logs for the user agents from Chapter 2, separated into training and search crawlers. This check says nothing about visitor numbers. It tells you whether your store arrives at all in the raw data from which an AI answer is later generated.
Crawler access to your own store is therefore an important basic signal – but not proof that you are being cited, and missing access is not proof that your brand does not appear in AI answers. As Chapter 4 showed, visibility also arises through sources that do not belong to you at all.
Question 2: Does AI send me visitors?
A lot has improved here in 2026 – but not completely. On May 13, 2026, Google Analytics 4 added its own channel for AI assistants to the default channel group. Sessions from recognized assistants automatically get the medium ai-assistant and land in their own channel. No configuration needed; the channel was available across the board from early June.
Four limitations remain, and each distorts the picture:
No complete referrer list: in its documentation and announcement, Google only names examples – ChatGPT, Gemini, Claude, Copilot, DeepSeek and Grok. Perplexity does not appear in these examples. Which sources actually land automatically in the default channel at a given time therefore remains partly a black box.
AI Overviews are not counted: Google AI Overviews and AI Mode remain in organic search. You therefore have two separate views of AI traffic – a named one and an invisible one.
Only effective going forward: visits before May 13, 2026 remain in referral and direct retroactively. A year-on-year comparison is currently not possible via the default channel.
Referrer loss in mobile apps: when someone taps a link in an app, the operating system often removes the referrer completely. These visits land in direct – indistinguishable from someone who typed in your address.
The practical advice from all this: keep your own channel group, even though the native channel now exists. It can capture additional platforms based on available referrers and can also be applied to historical data – but it cannot reconstruct lost referrers either.
Question 3: Am I being mentioned without anyone clicking?
This is the most uncomfortable of the three questions. An AI system can name your store without a single click occurring. The user has read the recommendation, their perception of your brand may have changed – and no analytics tool shows it. No click, no referrer, no event.
A customer who researches with an AI and then types in your address directly or googles your brand name is an AI-referred customer. No report says so.
At arboro, we show AI visibility and AI traffic in client reports wherever the available tools allow – and the recurring point of explanation is exactly this: not every AI-referred purchase starts with a click from the AI answer.
What does this mean in practice?
Relying exclusively on GA4 gives only an incomplete picture of the actual AI impact. A reliable assessment needs three signal sources: server logs for the crawler level, a properly configured GA4 channel including your own addition for the measurable visitor level – and the acceptance that part of the impact remains fundamentally invisible.
Anyone who demands a single figure for "AI ROI" that covers all three levels exactly is demanding something that does not exist with today's tools. That is not an excuse, but the honest state of the art.
Our assessment
Individual weeks say little at the moment. Observe the development over a longer period and evaluate not only traffic, but also engagement, conversion and revenue of the recognizable AI visitors.
Keep an eye on your direct traffic anyway. If it rises in parallel with brand searches and growing AI visibility, that can be an additional indication. It does not prove the connection.
What you can set up today
Create your own channel group in GA4 that captures additional platforms on top of the native channel – and let it run in parallel to the default channel instead of deleting it.
Check a sample of your server logs from the last week to see how often the known AI crawlers actually accessed your store.
Mark May 13, 2026 as a cut-off date in your reports so that nobody accidentally compares periods that were recorded differently.
Frequently asked questions
Partly. Since May 13, 2026, recognized AI assistants automatically land in the medium ai-assistant. However, Google AI Overviews and AI Mode are not included, the channel does not work retroactively, and visits from mobile apps often lose the referrer.
No, not with today's tools. Mentions without a click leave no trace. A reliable assessment combines server logs, GA4 with your own channel group and observing direct traffic and brand searches over a longer period.
)