> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/analytics.md). # Analytics - [Setting Up Filters and Presets in Utilization](https://help.alternativepayments.io/analytics/setting-up-filters-and-presets-in-utilization.md) - [Who Can Access Analytics and How Permissions Work](https://help.alternativepayments.io/analytics/who-can-access-analytics-and-how-permissions-work.md) - [Client Trends Report - What It Shows and How to Use It](https://help.alternativepayments.io/analytics/client-trends-report-what-it-shows-and-how-to-use-it.md) - [How MRR Data Is Calculated and What Affects](https://help.alternativepayments.io/analytics/how-mrr-data-is-calculated-and-what-affects.md): MRR in Analytics is built from your PSA, not from your Alternative Payments billing. Your figures are only as complete as the agreements and costs configured in ConnectWise. - [Exporting Data and Sharing Reports](https://help.alternativepayments.io/analytics/exporting-data-and-sharing-reports.md): Download your Analytics data to share it with your team, and understand who in your organization can see Analytics today. - [Analytics FAQs](https://help.alternativepayments.io/analytics/analytics-faqs.md) --- # 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://help.alternativepayments.io/analytics.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.