PLATFORM / AGENT ANALYTICS
AI Agents Are on Your Site — See Who Arrives, at Log Level
GA4 either misses agent traffic or files it under 'other'. Agent Analytics classifies 27 bot signatures at log level — GPTBot, ClaudeBot, PerplexityBot and Google-Extended included — shows which of your pages feeds which model, and ties an agent visit to the human click that follows.
THE CHALLENGE
The Fastest-Growing Segment of Your Traffic Is Invisible
AI traffic never reaches your analytics
Bots do not execute JavaScript, so GA4 never fires for them. The visits exist — in your server logs — but every dashboard says zero.
You cannot tell which bot read what
GPTBot training crawls, Perplexity answering in real time, agents completing tasks: three different intents, one undifferentiated log line — unless someone parses it.
Citations appear with no visible cause
A page starts getting cited and nobody can say which crawl preceded it. Without the bot timeline, cause and effect stay disconnected.
Block or allow is decided blind
Teams block AI bots to “protect content” or allow everything by default — both without data on who visits and what they take.
HOW IT WORKS
From Logs to an Attribution Chain in Four Steps
Setup takes one of two routes: edge log forwarding or a one-line JS snippet.
Collect
Your Cloudflare, Vercel or nginx logs stream in; without log access, a lightweight JS snippet captures server-side hits.
Classify
Requests are split across 27 known agents by UA, IP range and behaviour signature; impersonators are filtered and unknown agents get a heat score.
Attribute
The chain agent visit → citation inside an answer → human click is built, showing which crawl produced real traffic.
Report
A per-page matrix of which model each page feeds, so robots and llms.txt decisions are made with data.
LOG LEVEL
Every Agent Visit, Line by Line
Agent Analytics parses your logs and separates AI agents from browsers: which bot, which pages, what status, at what frequency. The invisible layer becomes a timeline you can correlate with citations.
- Named agents: GPTBot, ClaudeBot, PerplexityBot, Google-Extended and more
- Per-page fetch history with status codes
- Crawl events correlated with citation changes
agent analytics — live log
WHY GA4 CANNOT SEE IT
Two Views of the Same Site
Analytics scripts run in browsers; crawlers never load them. The only place agent traffic exists is the server log — which is exactly where this module reads from. No tags, no client-side code.
- Log-level ingestion, not a tracking script
- Human traffic stays in GA4; agents live here
- Works alongside Search Console and GA4 views
WHAT GA4 SEES
WHAT LOGS SEE
WHY IT MATTERS
Crawl Budget Is Now Answer Budget
The Leading Indicator
If a model cannot crawl your site, it cannot cite it; agent traffic is the leading indicator of visibility.
Content Value Signal
Seeing which pages get crawled shows which content models consider worth reading.
A True Bot Inventory
Impersonator filtering also hands your security team a true bot inventory.
Page-level ROI
The attribution chain answers 'does AI traffic pay' at page level.
SAMPLE VIEW
Seven Days of Agent Traffic, Sample Account
Figures come from the sample account; your console shows them in real time.
WORKS WITH
The Modules That Feed and Use Agent Data
Agent Analytics is open in beta on Pro and above.
FAQ
Agent Analytics, Asked Directly
Which bots are identified?
The named AI crawlers and answer-engine fetchers — GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and others — plus a category for unverified agents.
How does setup work?
By reading server or CDN logs. Cloudflare users can connect log delivery directly; other setups ship logs via standard exports. No script is added to your pages.
Is any personal data processed?
The module analyses bot traffic. Human visitor analysis stays in your analytics tool; agent lines carry no personal profiles.
Can bot identity be spoofed?
User-agent strings can be faked, which is why verification also checks published IP ranges where vendors provide them, and flags unverifiable claims.
How does this connect to citations?
Crawl events are laid on the same timeline as your visibility measurements, so a citation change can be traced back to the fetches that preceded it.
Should I block AI bots?
It depends on strategy: blocking protects content but zeroes citation probability on that platform. The module gives you the per-bot data to decide deliberately.
Does it work with GA4 and Search Console?
Yes — it complements them. Human traffic remains theirs; the agent layer, which they cannot see, is what this adds.
Which plan includes it?
Agent Analytics ships with Growth and above.
See Where Your Brand Stands Today
The free audit takes about four minutes to set up. The result screen shows your score and the first three fixes.