> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/analytics.md).

# Analytics

Explore your performance data in dashboards, understand how every metric is calculated, and create metrics of your own.

Analytics shows how shoppers interact with your site and your Crobox experiences, from traffic and engagement to revenue. It mirrors the **Analytics** section of the Crobox app: **Dashboards** for exploring your data, and **Metrics** for managing what your widgets measure.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Dashboards</strong></td><td>Open and manage dashboards, use filters and date ranges, and build widgets, including with AI.</td><td><a href="/how-to-guides/analytics/understand-your-analytics.md">Dashboards</a></td></tr><tr><td><strong>Metrics</strong></td><td>See how every metric is calculated, create your own, and combine group bys with aliases.</td><td><a href="/how-to-guides/analytics/metrics.md">Metrics</a></td></tr><tr><td><strong>Data Confidence</strong></td><td>Understand how Crobox keeps your analytics data reliable.</td><td><a href="/how-to-guides/analytics/data-confidence.md">Data Confidence</a></td></tr></tbody></table>

{% hint style="info" %}
Looking for Sagent performance? Sagent has its own analytics. See [Sagent Analytics](/how-to-guides/sagent/analytics.md).
{% endhint %}


---

# 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.crobox.com/how-to-guides/analytics.md?ask=<question>&goal=<user_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.