> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/study-basics/testing-prototypes/analyze-heat-maps-and-click-data.md).

# Analyze heat maps and click data

If you use a Figma prototype in a study and connect [your Figma account](/integrations/figma-integration/set-up-the-figma-integration.md), Dscout will generate heat maps for your prototype. Dscout will include heat map thumbnails of each frame that was visited by participants during the duration of the task.

{% hint style="info" %}
You can add Figma Make prototypes to studies by selecting the **Website** option under **Task URL**. However, Dscout does not generate heat maps for Figma Make prototypes. For more information on task question settings, see [Task questions](/study-basics/question-types/task-questions.md).
{% endhint %}

## Requirements to generate heat maps

* Heat maps only work with Figma prototype URLs.
* Heat maps are only available for [**task questions**](/study-basics/question-types/task-questions.md).
* Once a Figma prototype has been introduced to participants through a task question, all **subsequent tasks** where participants have access to the prototype will generate heat maps as long as at least one participant interacts with the prototype during the duration of that task.
* You must [connect your Figma account](/integrations/figma-integration/set-up-the-figma-integration.md) to Dscout to see heat maps.

## Viewing heat maps

If the above criteria are met, heat maps will be available **in the analysis for that task.** To view a heat map, select the **Heat maps** tab in your task analysis.

Here, you'll find thumbnails of each frame visited by your participants. If a frame was not visited by any participants during the duration of the mission, it will not be included in the heat map.

![](/files/0849a75f0983cac0454f7162e4192fb49ede0c91)

Clicking on a thumbnail will open up a modal that shows a heat map representing the density of clicks from all participants.

* Red = more clicks
* Lighter blue = fewer clicks

![](/files/9a5bac6a4e52abe2f1db3ce062fa1059a37ca97d)

## Navigating the heat map

Once you open a thumbnail to view the heat map, you can zoom in on the heat map and scroll to focus your view.

On the left sidebar, you can select a different heat map frame to view.

You can hover over an area of the heat map or on a click area in the **Click areas** sidebar to see the following details on the heat map: the click area outlined in blue, the click area title (Figma layer that was clicked), and the number of clicks across participants for that click area. The order of the click groups is determined by the Figma design file. Learn more about Click areas below.

You can filter the data being displayed in the heat map using the Filters icon. If filters are applied, the heat map will show the filtered participant view with an updated participant count (for example, 15/24 participants).

![](/files/963a812a8c1208907cc98e7eac9e304b1ad669c8)

### Click areas

Clicking on an area of a heat map or on a click area in the sidebar will bring that area into focus. In this selected state:

* The click area (in the right sidebar) will expand to show all participants who clicked in that area.
  * Clicking on a participant within a click area opens their session recording in a new tab at the moment of this click.
* The Heat map also highlights the click area(s). You can hover over the click areas to further explore the number of clicks by participant for that click area.

To exit the Click area focused view, click anywhere on the heat map, the “x” button on the click area label, or select a new click area in the sidebar.

![](/files/026b7d5239c112c4aa553356b5df4e0c13738486)

### Viewing click data in the Clicks tab

If you select a participant in the Click areas sidebar, you will be navigated to the participant’s full video session at the moment of that click. A **Clicks** tab will appear in the right sidebar with all of the click events from that prototype for that participant. The **Clicks** tab will show the timing of each click and the name of the Figma design element that was clicked. If you did not connect a Figma account prior to launching the mission, the clicks will be labeled “clicks,” and no specific element will be shown.

![](/files/e915cec4a42e659d4ced1f976629e959f9ba3dcb)

## Exporting your Heat maps

Heat map thumbnails can be exported as a PNG file using the export button on each thumbnail.

![](/files/7bf7060feb782144368bd72297ccc0f2f4ab30e2)

You can also export click data and task data from your usability test. For more information, see [Export usability test data](/usability-tests/analyze-a-usability-test/export-usability-test-data.md).


---

# 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://help.dscout.com/study-basics/testing-prototypes/analyze-heat-maps-and-click-data.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.
