The Paths & Heatmaps view enables you to see the journeys your users took through your prototype. This includes where users clicked, which screens they visited and where they clicked or tapped.
The data shown on this view enables you to get a deep understanding of how your designs are performing, to identify user pain points and to validate your design before writing a single line of code.
Paths & Heatmaps are available on the individual response view as well as on the aggregate summary view.
Data available on Paths & Heatmaps
Misclicks | The percentage of clicks on a screen that weren't on a hotspot, which is an area of the screen or component that has prototype links |
Dwell time | The average time users spent on a particular screen |
Goal hit | The count or percentage of users who reached the goal screen or component |
Drop off | The count or percentage of users who left the prototype at that screen |
Heatmaps | A visualisation of the areas of the screen with the most clicks |
Clickmaps | A visualisation of the exact locations where users clicked on a screen |
Unique visitors vs total screen visits
You can customise the way that the screen-to-screen paths metrics are shown. Unique means that a user visiting a screen multiple times will only be counted once. Toggling Total will show the number of times users viewed a screen, even if they viewed it multiple times.
Why do my paths entering a screen add up to over 100%?
In cases where you have toggled the Unique metric and Percent unit, it is possible to see percentages add up to over 100% enter a screen. This is because this users can loop back again through a screen via different paths. This is the percentage of users who navigated from one screen to another.
Why is my hit-goal percentage different between path and summary view?
When the Total metric and Percent unit are toggled, the percentage that hit a goal could appear lower than in the summary view. This is because the summary counts the unique users who hit the goal, whereas the path stats you have selected are counting the percentage of times a user moved from one screen to hit the goal.
In the below example, it looks like only 50% of users hit the goal, but this is because 50% of the total events on this screen led to the user reaching the goal. The other 50% was the user navigating to another screen that looped them back. But, 100% of the users who viewed this screen did hit the goal.
How we display components on paths
This iteration of Paths & Heatmaps is intended to help you understand the journeys users have taken through the screens in your prototypes.
This means that interactive components like carousels, drop-down menus and modals aren't fully displayed on Paths & Heatmaps. Instead, these components sit static on the base screen they're shown. Any overflow beyond the edge of the base screen won't be visible on this view.
We are currently exploring the best ways to display interactive components on this view and we would love your feedback.