Traffic your analytics can't see
Requests per hour
Agents & botsSeen by Google Analytics
Who's really visiting
Unique visitors, by what they actually are
Agent journeys
Question parts answered per visit
Answer coverage
How much of what agents ask your site can answer
What agents read
Pages fetched by agents and bots
Live activity
Content gaps
What buyers' agents needed and your site didn't say
All questions
Every visitor, identified by behavior
Agents don't always say who they are. Headers, speed and JavaScript give them away.
Send an agent to Nimbo
It shows up on the dashboard within seconds.
MCP server · in Claude: Settings → Connectors → Add custom connector
Plain-language questions · any agent that can open a link
Prompt for GrokBot, Instinct, ChatGPT…
How it works
- Server-side loggingEvery request is recorded, JavaScript or not. That's why agents show up here and not in GA.
- Behavioral detectionA "Chrome" with no browser headers, three requests a second and no JavaScript is an agent.
- Agent endpointsllms.txt, /ask and MCP turn anonymous reads into questions in the buyer's words.
- Gap reportsAnswers say what isn't published and ask agents to report it.
- AttributionEvery answer carries a tracked trial link, so signups trace back to the agent conversation.
- Answer engine—