Learning Center · Explain it to my boss · Measuring AI agent traffic
Our analytics can't see the AI agents visiting our website
Ask most businesses how many AI agents visited their site last month and they can't say. Tools like Google Analytics mostly can't see them: most agents never run the tracking tag, and known bots are filtered out on purpose. So we can't tell which assistants read our pages, which were blocked, or what it cost us.
What it costs the business
- Decisions are made on incomplete data, because our analytics can't see most AI agents.
- A rise in blocked assistant requests is a lost-sales signal, but filtered reports stay green while the journey breaks.
- Counting visits by agent name alone lets impostors inflate our numbers.
What to do
- Get access to our server or CDN logs, which record every request, from people and agents alike.
- Verify each agent against its operator's published addresses, to separate real agents from impostors.
- Track which agents visit, what they read and where they're blocked, week over week.
- Report AI agents as their own lines, not as bots, alongside visits and orders from AI assistants.
Who owns it: Bot protection or CDN adminEffort: Days for a first baseline
The detail is in Measuring AI agent traffic. Based on Why your analytics can't see AI agents, and how to measure agent traffic, How to explain agent readiness to your board, Agent traffic isn't bot traffic.