> 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/engaged/engagement-metrics.md).

# Engagement Metrics

The core engagement metrics at the top of the Engaged section, and how each one is calculated.

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

At the top of the Engaged section, these metrics summarize how users interact with your playable. Hover any value on the dashboard to see its definition.

***

#### **Impressions Engaged**

The number of impressions where the user engaged with the playable. An impression counts as engaged when the user taps or clicks a layer that has an action attached, like a button that moves to the next scene or a CTA.

***

#### **Engaged Rate**

Impressions Engaged as a percentage of all impressions. It shows how compelling and intuitive the playable's first moments are.

{% hint style="info" %}
This definition of engaged applies to date ranges starting on or after **12 Sept 2026**, for playables exported on or after **4 July 2025**. For earlier ranges or older exports, an impression counts as engaged when the user interacted with the playable at least once, on any layer. The tooltip on the dashboard always shows the definition in use.
{% endhint %}

***

#### **Total Engagements**

The total number of interactions recorded across all impressions and scenes: every tap, drag, swipe, and hotspot activation, plus game inputs. This includes interactions on layers with no action attached, so it can be higher than the per-layer totals in [Engagements by Layer](https://help.craftsmanplus.com/analytics/analytics-dashboard/engaged/engagements-by-layer.md).

Interactions are counted once per session per millisecond, so a single tap that's reported more than once isn't counted twice.

{% hint style="info" %}
The [Spreadsheet](https://help.craftsmanplus.com/analytics/analytics-dashboard/export.md) view groups the same metric by day. Because each day is counted separately, its total can differ from this figure by a fraction of a percent.
{% endhint %}

***

#### **Avg. Duration**

The average amount of time users spend in the playable.

***

#### **Avg. Progress**

How far users get on average, from the first scene through to the end card.

***

#### **Most Engaged Scene**

The scene with the most engagements, not counting the first scene.

***

#### **Most Dropped Scene**

The scene where the most users leave the playable, not counting the first scene.

{% hint style="info" %}
*The **end card** having the highest drop-off is ideal, since users should leave after reaching the final step.*
{% 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/engaged/engagement-metrics.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.
