Start with one usability question
For an illustrative SaaS pricing page, the question might be whether mobile visitors understand the difference between two plans. Write down the observable behavior you want to investigate, such as repeated taps on a comparison label or leaving before reaching the plan details.
Keep the page version, device group, and time range clear. A mobile visitor using a compact layout may encounter a different problem from a desktop visitor. Mixing those experiences in one interpretation can produce a redesign that addresses neither group well.
Use a heatmap to identify an aggregate pattern
Clarity heatmaps aggregate interactions across page views and support different map types, including clicks and scrolling. They can cover a page or a group of pages, using the selected filters. Choose the map that answers the question rather than treating every bright area as the same kind of evidence.
For the pricing example, use a mobile click view to inspect the plan comparison label and a scroll view to investigate how far visitors reach. Repeated interaction with a label can suggest a useful question about its appearance. It cannot establish whether the visitor wanted help, expected expansion, or was simply comparing options.
| Question | Useful evidence | Interpretation limit |
|---|---|---|
| Where do visitors interact? | Click heatmap | Interaction is not automatically confusion |
| Do visitors reach the details? | Scroll heatmap | Reaching a section does not prove understanding |
| What happened before leaving? | Individual recording | One journey is not representative of everyone |
| Did a change help? | Consistent outcome measurement | A different audience can change the observed rate |
Inspect recordings around the pattern
Clarity recordings provide a session list, playback, and filtering tools for investigating individual journeys. Use a relevant subset to inspect what happened before and after the interaction. Keep notes about observed behavior separate from your explanation of it.
For the sample pricing page, review several journeys where a visitor tapped the label and several where they continued normally. Look for the sequence: arrival, plan comparison, attempted interaction, and next destination. Include a counterexample so the investigation does not become a collection of only the most dramatic sessions.
Check the page state represented by the map
Clarity's heatmap documentation describes limitations for dynamic content and notes that the screenshot depends on the selected playback state. A heatmap may not display interaction on a dynamically opened menu in the way you expect. Check the underlying page state before concluding that a control was ignored.
If the pricing comparison expands after a tap, use recordings to inspect that sequence and compare the visible state with the map. Keep distinct page revisions separate where possible. A map over a newer layout may be difficult to interpret if the interactions came from an older arrangement.
Verify masking before reviewing customer content
Clarity provides masking modes and element-level controls. Its documentation states that masking changes apply to new recordings and cannot retroactively change earlier captures. Review the setup using harmless test content before collecting pages that contain customer information.
For the pricing page, a simple public layout may be sufficient for the investigation. If you expand into an account or checkout journey, reassess what appears in the interface and links. Use the applicable collection and consent configuration for the site rather than assuming that hiding an input covers every displayed customer detail.
Turn the observation into one testable change
If the label resembles an expandable control but is plain text, propose a bounded change: make the interaction work or make the label's purpose clearer. State the expected effect and decide how to measure it alongside the journey evidence. Compare similar device groups and an appropriate observation period.
Review the resulting behavior and the customer outcome, such as reaching the intended plan or completing a valid next step. Keep uncertainty visible when the sample is small. Clarity is useful when it helps the team move from a visible pattern to a specific investigation and a result that can be checked.
Sources and editorial method
Official sources linked in this guide were checked on October 27, 2026. Product features, interfaces, and plan limits can change. The examples are proposed workflows, not reports of a hands-on benchmark or customer results. Confirm the documentation for your product version before implementing a workflow.