Skip to content

Heatmaps

Heatmaps turn your recorded Sessions into a visual map of where users focus on each page — so you can spot the buttons everyone misses, the content nobody scrolls to, and the elements that draw rage clicks.

Heatmaps live under UX Research → Heatmaps, scoped to the Application you’re working in.

Each tracked page supports three heatmap types, shown as tabs in the viewer:

Type What it shows
Clicks Where users tap or click on the page.
Scroll Depth How far down the page users scroll.
Attention Where user attention concentrates across the page.

Every type is captured separately for three device variations, based on the viewport width recorded in each session:

Variation Viewport width
Desktop ≥ 1024 px
Tablet 640–1023 px
Mobile < 640 px

A page only appears under a given device tab if it has sessions recorded at that viewport. If a page has no data for the selected device, the viewer shows an empty state and prompts you to try another device or generate again after more traffic lands.

The heatmap viewer renders the overlay on top of a representative session’s page so the hotspots line up with the real layout. Around it you’ll find:

  • Page list — Every tracked page for the selected device, with its session count and which device variations it has data for. Selecting a page loads its heatmap.
  • Top Elements — A panel of the most-clicked elements on the current page. It stays visible across the Clicks, Scroll Depth, and Attention tabs, and surfaces signals such as dead clicks (clicks on non-interactive elements) and rage clicks.
  • Intensity legend — A Low → High gradient so you can read where interaction concentrates.
  • Pick preview session — Lets you pin a specific session as the backdrop the overlay renders against, in case the automatically chosen one isn’t representative.

Heatmaps are produced by a background aggregation job over your recorded sessions.

  1. Open UX Research → Heatmaps.
  2. If there’s no data yet, click Generate Heatmaps. Once data exists, use Regenerate heatmaps to refresh after more traffic accumulates.
  3. The job moves through a lifecycle while it runs — a banner reflects the current state and the page refreshes results when it finishes.
Status Meaning
Queued The aggregation job is waiting for a worker.
Active Marketrix is aggregating your session recordings — this can take a few minutes.
Completed Aggregation finished; the latest heatmaps are loaded.
Failed The job ended on an error. Try regenerating.