> 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/engagements-by-layer.md).
# Engagements by Layer
See which layers users interact with, as a total count or as a percentage of impressions.
**Engagements by Layer** breaks down *what* users interact with in your playable. Use it to see which elements perform well and which may need work. For example, see which answer users pick most in a quiz.
Use the dropdown to switch between:
* **Total Engagement** – How many times users interacted with each layer.
* **Percent of Sessions** – The percentage of impressions where users interacted with each layer.
Each tile is a layer with an action attached, listed alphabetically by name. Layers that share a name are combined into one tile, so give layers unique names when you want to track them separately. See [Analytics Best Practices](/analytics/analytics-best-practices.md).
### Other Engagements
The last tile, **Other Engagements**, counts interactions on layers with no action attached, like taps on a background image. Hover its info icon for the definition.
A high Other Engagements count can mean users are tapping elements they expect to do something. Check the [click heatmap](/analytics/analytics-dashboard/engaged/path-view.md#click-heatmap) to see where.
---
# 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/engagements-by-layer.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.
