> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/17.latest/marketers-and-editors/analytics/scroll-heatmap.md).

# Scroll Heatmap

Learn how you can use the Scroll Heatmap in Umbraco Engage to gather data on the behaviour of your visitors.

The Scroll Heatmap shows you how your visitors consume your content.

The feature gives a visual representation of the average scroll depth of your visitors on a specific page. This feature is only available within the Analytics Workspace View on an Umbraco page.

An advantage is that you do not need to integrate any 3rd-party tools. This will prevent additional load times and possible issues with data ownership.

![View a scroll heatmap on each published content item in the Content section.](https://1498851568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeiQnEGdbGIoA0IQ3nJUK%2Fuploads%2Fgit-blob-13a0a43b156ed7abd0dab9227a4de12b1ad58e7a%2Fengage-analytics-scroll-heatmap-v16.png?alt=media)

The heatmap only collects data if [the client-side script](/umbraco-engage/17.latest/developers/analytics/client-side-events-and-additional-javascript-files.md) is installed on your website.


---

# 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://docs.umbraco.com/umbraco-engage/17.latest/marketers-and-editors/analytics/scroll-heatmap.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.