> 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

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.](/files/IKvvgOeEnsiM92uy7n6k)

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-engage/17.latest/marketers-and-editors/analytics/scroll-heatmap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.