> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/platform-features/analytics.md).
# Overall Analytics Dashboard
Track usage, bounces & cost savings analytics
The **Analytics page gives** you a clear view of how your team is using Clearout over time, including **verifications completed, bounces detected, cost savings, and usage** by members or organizations. It’s designed to help you understand trends, optimize campaigns, and plan future budgets based on real performance data.
### What you can see
* Total usage across various tools and products performed in a selected date range.
* Bounces detected and estimated cost savings.
* Usage broken down by team members or organizations (for Team Accounts).
* Downloadable reports for further analysis or sharing with stakeholders.
### How to view and download analytics
1. Log in to your Clearout account.
2. Go to **Menu → Analytics**.
3. Choose the **date range** and optionally filter by **member** or **organization** (for team accounts).
4. Review the charts and numbers online, or click to **download** the report for offline analysis.
---
# 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://docs.clearout.io/platform-features/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.
