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

# Path View

Follow how users move from scene to scene, see where each scene's traffic comes from and goes next, and see where users tap with the click heatmap.

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

**Path View** is the centerpiece of the Engaged section. It maps your playable scene by scene, shows how users flow between scenes, and shows where they tap.

### Reading the Path

Each scene appears as a card, connected by lines that follow the routes users take through your playable. The percentage above each card is the share of impressions that reached that scene. The first scene is always 100%.

### Scene Details

Click a scene to select it. The first scene is selected when the page opens. The panel shows that scene's numbers:

* **Impressions** – How many times users reached the scene.
* **Total Engagements** – Interactions recorded on the scene, including taps on layers that have no action.
* **Impressions Captured** – Impressions where users clicked a CTA on the scene.
* **Avg. Duration** – The average time users spend on the scene, in seconds.
* **Progress** – How far through the playable this scene sits, from the first scene to the end card at 100%.

### Scene Connections

With a scene selected, two tables show how users arrive and where they go next:

* **Incoming Connections** lists the scenes users came from, and the percentage that came from each.
* **Outgoing Connections** lists the scenes users went to next, and the percentage that went to each.

Each table adds up to 100%. The connecting lines on the path are labeled with the same percentages, so you can see at a glance which routes users take most.

### Click Heatmap

The preview beside the path shows the selected scene with a **heatmap** of where users tapped. Hotter areas got more engagements. The heatmap appears on the scene cards along the path too.

* **Hover** a hot spot to see its **Portrait Engagements** or **Landscape Engagements**, **Unique sessions**, and **Share of engagements** in that scene and orientation. Spots with less than 0.1% of the scene's engagements show **<0.1%**.
* **Heatmap** turns the overlay on and off. It's on by default.
* **Portrait** and **Landscape** switch between orientations, when users played in both. This changes the whole Path View, not just the preview.

Use the heatmap to check that users are tapping where you expect, find elements users mistake for buttons, and see whether your CTA gets attention.

{% hint style="info" %}
The heatmap needs a playable exported on or after **25 Sept 2026**. For older exports, the Heatmap switch is disabled. Re-export the playable to start collecting engagements.
{% 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/path-view.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.
