DOCS ANALYTICS
See how people and agents use your docs
GitBook shows who reads your documentation, what they ask, and where your content falls short. Human readers and AI agents are counted separately, so you can see what each one needs.
One view of everyone reading your docs
Each report covers one audience: readers, agents, and the questions both bring
FEATURES
Find out what to fix next
Analytics points to the specific page, topic, or audience that needs work, then helps you improve it
Agents & MCP
Track agent traffic, the pages agents read, and every MCP call they make. Plus, see which tools your users connect, what they search for through MCP, and which pages your product’s AI integrations rely on.
AI Assistant
Review user questions, answer quality, and source pages to understand what your docs cover — and what they miss.
FAQs
What is GitBook site analytics?
Site analytics show how your published documentation is used, split into three reports. Traffic covers human readers. Agents & MCP covers the LLMs, coding agents, and crawlers reading your site. AI Assistant shows what visitors ask GitBook Assistant and how well your content answers them.
Can I see how AI agents read my documentation?
Yes. The Agents & MCP report shows the pages agents read, their share of all reads on your site, and every call made through your site’s MCP server. It ranks the agents reading your site and shows which way they read it: Markdown, llms.txt, MCP, or regular page views.
How does GitBook separate people from agents?
Agent reads are counted in the Agents & MCP report, so the Traffic numbers reflect human readers. Crawler page views appear in their own Bots card. Clients that don’t identify themselves are grouped as “Unidentified.”
What does the AI Assistant report show?
It shows the questions visitors ask GitBook Assistant, how many were answered, how helpful readers found the answers, and how much support effort was likely avoided. Questions are grouped into topics, and for each one you can see the full conversation and the content the answer drew on.
How is “Savings” calculated?
Savings is an estimate based on the assumption that one in five answered questions would otherwise have become a support ticket. Admins can set their own cost per ticket or per support hour through the API. Treat it as an order of magnitude, not an exact figure.
Can I analyze a specific customer or segment?
Yes, if your site uses adaptive content. You can filter any report by the visitor claims you pass, like customer, plan, role, or feature access, to see how that segment reads your docs and rates your pages.
Can I export my analytics data?
Yes. Any card can be downloaded as a CSV, and the AI Assistant report can export a question summary or a detailed answer-level file. To build your own reports, use the Events Aggregation API.
Who can see site analytics?
Anyone with access to the site can view its analytics, including readers, reviewers, and editors.







