> 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/summary.md).

# Summary

A live preview of the playable beside its performance funnel, with average progress, average duration, and integrated partner data.

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

The **Summary** is the fastest read on how a playable is doing. It puts the creative itself next to its key numbers.

### Playable Preview

On the left, the playable runs right in the dashboard, so you can see what users see while you read the numbers. It starts muted.

* **Mute** and **Unmute** turn the sound on and off.
* **Restart** plays the creative again from the first scene.
* **Portrait** and **Landscape** switch orientation. These only appear when the creative supports both.

### Funnel

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

The funnel shows how many users make it through each stage:

* **Impressions** – How many times the playable was viewable. This is the top of the funnel, at 100%.
* **Engaged** – Impressions where users engaged with the playable, with the percentage of impressions.
* **Captured** – Impressions where users clicked a CTA at least once, with the percentage of impressions.

Below the funnel:

* **Avg. Progress** – How far users get, on average, from the first scene to the end card.
* **Avg. Duration** – The average time users spend in the playable.

See [Engagement Metrics](/analytics/analytics-dashboard/engaged/engagement-metrics.md) for exactly what counts as engaged.

### Integrated Partners

When a creative runs on a partner connected to CRAFTSMAN+, a row of partner cards shows that partner's own data. Use the arrows to move between cards.

* **AppLovin** shows **Impressions**, **Clicks**, **CTR**, and **Cost** as reported by AppLovin, for creatives uploaded through [AppLovin Direct Upload](/company-settings/partner-integrations/applovin.md).
* **Digital Turbine** shows the **Campaign ID** and **Deal ID** the creative runs under.

Partner cards follow the Partners filter. A partner's numbers come from that partner and can differ from CRAFTSMAN+'s own counts.


---

# 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/summary.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.
