Analytics & Insights
Docsbook records every page view, search, AI question and feedback vote on your documentation, and reports them as answers to questions an owner actually asks — not as a wall of counters. Reading these reports costs nothing against your project's balance; only AI answers, translations, agent runs and the semantic index spend it.
Four questions the reports below are built to answer, with the report that answers each:
| Question | Where it is answered |
|---|---|
| Where do my readers come from? | Sources card — referrers, channels, UTM, Google Search queries — in the analytics overview |
| Which pages are dead, and which hold people? | Pages and Headings tabs, plus the read time report |
| Did readers reach the page that sells? | Conversion rate and CTA Clicks in the analytics overview |
| What was that worth? | Revenue, once a Call To Action URL and an Average Product Price are set in Branding |
| Did they do the specific thing I care about? | Goals and funnels — declare the outcome, and it is matched against history already recorded |
| Can I trust any of these numbers? | How measurement works — what a visitor is, how bots and your own team are excluded, and what is deliberately not collected |
Which pages are readers leaving without converting?#
Open the Pages card of the analytics overview and switch its tab to Exit. The Exit tab names the last page of each visit, so the pages at the top of it are where readers stop — and every row carries both figures at once, how many visitors it brought and what they were worth. A page high on Exit and low on CTA Clicks is a page readers finish and leave.
Hovering a row gives its visitors, revenue, revenue per visitor and conversion rate; clicking the filter button narrows the whole dashboard to that page, so you can read one page end to end. See Analytics overview for every card and tab.
What do readers do on the page, not just which page they opened?#
Docsbook tracks the actions, not only the views: AI chat opens, questions asked, code blocks copied, outbound links clicked, sidebar navigations, language switches, and which headings were actually scrolled into view. Heading views concentrated at the top of a long page mean readers are not reaching the rest of it.
The full list, with what each event means, is the tracked events reference.
Where are readers arriving from that you do not serve yet?#
The Countries report and the reader map pair each country of origin with the share of its readers who landed on a page in a translated language. A country that sends readers and gets none of them onto a translation is a market you are paying to attract and then losing at the language barrier.
See visitor countries report, and translation settings for turning a language on.
In this section#
cookieless visitor identity, two-layer bot filtering, the read-time clip, retention and privacy — the definitions every number below inherits
every figure, card and tab in the analytics panel, and what each one is not evidence of
all 36 docs.* events, what fires each one, and the payload it carries
what is metered, how a call is priced, and what your chat was asked and cost
declare what a reader should do, then measure whether they did
how time-on-page is measured, and the clip the figure rests on
where readers are, how reliably that is known, and which of them read a translation
Related#
- Branding — the Call To Action URL and Average Product Price that switch on conversion and revenue reporting
- Webhooks — get told about a traffic drop or an unanswered question instead of checking for one
- MCP tools reference — reading the same numbers from an agent