> 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/documentation/zh/analytics/guides.md). # 指南探索使用分析来衡量和改进文档的指南使用分析功能了解你的文档，并将洞察转化为改进。这些指南涵盖站点分析、外部跟踪、自定义报告和贡献者活动。 #### 探索


	跟踪文档指标选择有用的指标，并将洞察转化为文档改进。	How to track documentation metrics
	使用 Google Analytics 跟踪文档分析连接 Google Analytics 以衡量流量和访客行为。	How to set up Google Analytics
	使用 Events Aggregation API 跟踪高级分析查询事件数据以构建报告和自定义仪表板。	How to track events with the Events API
	分析变更请求贡献者了解是谁在为你的文档做出贡献，以及他们如何工作。	How to use contributor insights

#### 快速指南

我如何使用站点分析？

在你的站点分析报告中查看流量、反馈、搜索、代理和 AI 助手活动。本指南展示如何筛选数据并识别内容机会。

我如何使用搜索和反馈数据？

搜索词和页面评分突出显示需要关注的内容。本指南展示如何发现差距并优先安排文档改进。

我如何使用 Google Analytics 跟踪文档？

连接 Google Analytics，以衡量超出 GitBook 站点分析范围的流量。本指南涵盖集成、衡量 ID 和数据收集。

我如何构建自定义分析报告？

使用 Events Aggregation API 在你自己的工具中分析文档行为。本指南涵盖事件数据、查询和仪表板报告。

--- # 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/documentation/zh/analytics/guides.md?ask=&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.

:chart-line:

跟踪文档指标

:google:

使用 Google Analytics 跟踪文档分析

:code:

使用 Events Aggregation API 跟踪高级分析

:chart-pie:

分析变更请求贡献者