# Docs analytics - [Documentation analytics: which metrics to track and how to measure success](https://gitbook.com/docs/guides/docs-analytics/documentation-analytics.md): Still figuring out the best way to prove success with your user-facing documentation? This guide will help you figure out what to track and how to analyze the data. - [Track documentation analytics with Google Analytics](https://gitbook.com/docs/guides/docs-analytics/track-documentation-analytics-with-google-analytics.md): Learn how to install and configure the Google Analytics integration so you can track detailed analytics from your docs site - [Track advanced analytics with GitBook's Events Aggregation API](https://gitbook.com/docs/guides/docs-analytics/track-advanced-analytics-with-gitbooks-events-aggregation-api.md): Master GitBook’s powerful events aggregation endpoint to create custom analytics dashboards, understand user behavior patterns, and make data-driven decisions about your documentation strategy. - [Analyze change request contributors with GitBook’s API](https://gitbook.com/docs/guides/docs-analytics/analyze-change-request-contributors-with-gitbooks-api.md): Track creators, reviewers, and contributors with GitBook’s API to understand how your team collaborates --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://gitbook.com/docs/guides/docs-analytics.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.