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

# Overview

Creative-level ANALYTICS that show how a single playable performs across impressions, engagement, and captures, from first view to conversion.

<figure><img src="https://3403191029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYsCUHima0FilwMqIJBnV%2Fuploads%2Fgit-blob-0be3ec6c626bcbb29604a5959d516635cc5a2dcc%2FHero%20-%20Side%20View.png?alt=media" alt=""><figcaption></figcaption></figure>

Click a creative in the [Listing View](/analytics/analytics-tab/listing-view.md) to open its Analytics Dashboard: a detailed view of how users experience that one playable, from the moment it's viewable to the moment they click your CTA.

The top of the page shows the project name, the variant name, and the dates you're reporting on.

### Filters

The header holds three filters that apply to everything on the dashboard:

* **Export** narrows the data to a single export of the creative. It defaults to **All Exports**. Each option shows the export date and its impressions, newest first. Use it to compare an updated version against an earlier one. Changing the date range resets it to All Exports.
* **Partners** narrows the data to the ad networks you choose. See [Partners](/analytics/analytics-tab/filtering-searching-and-sorting.md#partners).
* **Date Range** sets the time window. See [Adjusting the Date Range](/analytics/analytics-tab/adjusting-the-date-range.md).

### Sidebar

The sidebar on the left moves you around the dashboard:

* **Dashboard** shows the main view. Click **Summary**, **Impressions**, **Engaged**, or **Captured** to jump to that section.
* **Spreadsheet** switches to a day-by-day table you can download as a CSV. See [Export](/analytics/analytics-dashboard/export.md).
* At the bottom, **Created** and **Last Updated** show when the project was made and last changed. **Go to Project** opens it in PLAY in a new tab.

### Dashboard Sections

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><strong>Summary</strong></h4></td><td>A live preview of the playable beside its funnel: impressions, engaged, and captured, plus average progress and duration.</td><td><a href="/analytics/analytics-dashboard/summary.md">Summary</a></td></tr><tr><td><h4><strong>Impressions</strong></h4></td><td>Reach and traffic sources: total impressions, leading partner and platform, and trends over time.</td><td><a href="/analytics/analytics-dashboard/sessions.md">Impressions</a></td></tr><tr><td><h4><strong>Engaged</strong></h4></td><td>How users interact once they arrive: engagement metrics, Path View with a click heatmap, and engagements by layer.</td><td><a href="/analytics/analytics-dashboard/engaged.md">Engaged</a></td></tr><tr><td><h4><strong>Captured</strong></h4></td><td>CTA performance: capture metrics and captures by partner and platform.</td><td><a href="/analytics/analytics-dashboard/captured.md">Captured</a></td></tr></tbody></table>

{% hint style="info" %}
Hover any metric's value to see how it's calculated.
{% 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://help.craftsmanplus.com/analytics/analytics-dashboard/overview.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.