Insight

Your analytics cannot see AI assistants. Here is what to measure instead.

Assistants do not run scripts, so client-side tracking misses them entirely. The server-side view, and what it changes about reporting.

Robin Brown · 2026-08-06 · 7 min · Marketing and BD, IT, risk and compliance

What you will learn

  1. Why GPTBot, ClaudeBot and PerplexityBot never appear in the usual analytics suite.
  2. What still gets counted when a person clicks through from an assistant.
  3. How to report the server-side view without pretending the dashboard is complete.

Why does analytics miss AI traffic?

Because measurement runs in JavaScript and the crawlers do not. GPTBot, ClaudeBot and PerplexityBot fetch the HTML and never execute the page, so they appear in server logs and nowhere in the analytics dashboard. Referred visits from a person who clicked through from an assistant do get counted, but the far larger signal, which pages the assistants are reading and quoting, exists only in the logs. A firm relying on its dashboard alone is measuring the small visible end of something considerably bigger.

More common questions

Do referred visits from assistants show up in analytics?

Often yes, when a person clicks a link and lands with a referrer the suite can see. That is only the visible end. The larger signal, which pages assistants fetch and quote, exists in server logs and is invisible to client-side scripts.

Should we replace our analytics suite?

Not necessarily. Add the log view rather than discarding the dashboard. Partners need both: what humans do after a click, and what assistants read before anyone clicks.

Is this only an AI problem?

No. Zero-click search already shrinks what dashboards see. Assistants make the blind spot sharper because they never execute JavaScript at all.

Written for