> 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.md).
# Engaged
Understand how deeply users interact after load, with core engagement KPIs plus Path View and layer-level interaction insights.
The **Engaged** section provides deeper insight into how users interact with your playable after it loads. While the Impressions section tells you *who arrived*, the Engaged section tells you *who actually participates,* and how deeply.
This section provides a detailed view of **user intent and creative effectiveness**, helping you pinpoint friction points, validate design choices, and optimize scene flow.
By combining funnel metrics, Path View visualization, and element-level interaction data, the Engaged section makes it easy to understand not just *if* users engage, but *how* they engage, so you can confidently improve usability, pacing, and overall performance.
---
# 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.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.
