> For the complete documentation index, see [llms.txt](https://alhena.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alhena.gitbook.io/docs/dashboard/analytics.md). # Analytics Track and measure your AI agent's performance with comprehensive analytics. Understand how your AI is impacting customer satisfaction and revenue to make data-driven decisions. ## In This Section * [Agent Performance](/docs/dashboard/analytics/agent-performance.md) - Track conversation volume, AI vs. human handled interactions, and credit usage * [Trending Topics](/docs/dashboard/analytics/trending-topics.md) - Analyze conversation patterns by topic to understand what customers are asking about * [Revenue Impact](/docs/dashboard/analytics/revenue-impact.md) - Measure the revenue contribution of your AI agent with cart and GMV analytics * [CSAT Collection](/docs/dashboard/analytics/csat-collection.md) - Collect and analyze customer satisfaction feedback after AI interactions * [A/B Testing](/docs/developer-reference/website-sdk/ab-testing.md) - Run experiments to measure the impact of your AI agent on revenue --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://alhena.gitbook.io/docs/dashboard/analytics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.