> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/analytics/guides.md).

# Guides

Explore guides for measuring and improving your documentation with analytics

Use analytics to understand your documentation and turn insights into improvements. These guides cover site analytics, external tracking, custom reports, and contributor activity.

#### Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-chart-line">:chart-line:</i></h4></td><td><h4>Track documentation metrics</h4><p>Choose useful metrics and turn insights into documentation improvements.</p></td><td><a href="/docs/guides/docs-analytics/documentation-analytics.md">How to track documentation metrics</a></td></tr><tr><td><h4><i class="fa-google">:google:</i></h4></td><td><h4>Track documentation analytics with Google Analytics</h4><p>Connect Google Analytics to measure traffic and visitor behavior.</p></td><td><a href="/docs/guides/docs-analytics/track-documentation-analytics-with-google-analytics.md">How to set up Google Analytics</a></td></tr><tr><td><h4><i class="fa-code">:code:</i></h4></td><td><h4>Track advanced analytics with the Events Aggregation API</h4><p>Query event data to build reports and custom dashboards.</p></td><td><a href="/docs/guides/docs-analytics/track-advanced-analytics-with-gitbooks-events-aggregation-api.md">How to track events with the Events API</a></td></tr><tr><td><h4><i class="fa-chart-pie">:chart-pie:</i></h4></td><td><h4>Analyze change request contributors</h4><p>Understand who contributes to your documentation and how they work.</p></td><td><a href="/docs/guides/docs-analytics/analyze-change-request-contributors-with-gitbooks-api.md">How to use contributor insights</a></td></tr></tbody></table>

#### Quick guides

<details>

<summary>How do I use site analytics?</summary>

Review traffic, feedback, search, agent, and AI Assistant activity from your site analytics reports.

This guide shows how to filter data and identify content opportunities.

<button type="button" class="button secondary" data-action="ask" data-query="How do I use GitBook site analytics? Show me how to review the Traffic, Agents &#x26; MCP, and AI Assistant reports, including page feedback and search. Explain how to filter data and compare periods. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I use search and feedback data?</summary>

Search terms and page ratings highlight content that needs attention.

This guide shows how to find gaps and prioritize documentation improvements.

<button type="button" class="button secondary" data-action="ask" data-query="How do I use GitBook search and page feedback analytics to improve my documentation? Show me how to identify content gaps and prioritize updates. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I track docs with Google Analytics?</summary>

Connect Google Analytics to measure traffic beyond GitBook site analytics.

This guide covers the integration, measurement IDs, and data collection.

<button type="button" class="button secondary" data-action="ask" data-query="How do I connect Google Analytics to my GitBook docs site? Show me how to configure the integration, add a measurement ID, and verify data collection. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I build a custom analytics report?</summary>

Use the Events Aggregation API to analyze documentation behavior in your own tools.

This guide covers event data, queries, and dashboard reporting.

<button type="button" class="button secondary" data-action="ask" data-query="How do I build a custom analytics report for my GitBook docs site? Show me how to use the Events Aggregation API to query event data and create reports. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/analytics/guides.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.