Articles on: Observe

Introduction to Heatmaps

Heatmaps

Heatmaps help you understand how people interact with your web pages by visualizing clicks, friction, and scroll behavior directly on top of the interface.

They are especially useful to uncover UX issues, understand where users struggle, and prioritize improvements with more confidence.

With Heatmaps, you can quickly spot:

  • highly clicked areas;
  • dead clicks and rage clicks;
  • low scroll reach;
  • differences across desktop, tablet, and mobile;
  • sessions related to a specific interaction;
  • AI-generated insights about behavior patterns.


Heatmaps depend on Session Replays. Without Session Replay data, Heatmaps cannot be generated.


Availability

Heatmaps are currently available in beta for Web.

They are accessible to these workspace roles:

  • Admin
  • Member
  • Editor

Mobile support is planned for a future release.


Because Heatmaps are still in beta, you may notice slower performance, missing UI elements in the rendered view, or temporary data adjustments while the feature evolves.


Requirements

To use Heatmaps, Session Replays must be enabled.

That can happen through your workspace replay configuration, including:

  • recording scopes;
  • general replay settings;
  • recording of sessions where observed messages were displayed.

Once Session Replays are active, Heatmaps are generated automatically from recorded page activity.


Where to find Heatmaps

Open Heatmaps from the main navigation:

  • Observe > Heatmaps



Caption: Open Heatmaps from the Observe section of the navigation.


How Heatmaps work

Heatmaps are built automatically from recorded page views and the sessions associated with those pages.

There is no page-by-page setup.

Screeb groups interactions by page, then lets you analyze them through two complementary views:

  • Heatmap for click behavior;
  • Scroll Map for scroll behavior.

For now, there is no minimum session threshold required for a page to appear, although available data still depends on your Session Replay volume and quota.


Heatmaps dashboard

The dashboard lists detected pages and helps you identify where to start your analysis.

Pages are ordered using:

  • number of sessions;
  • click rate.

For each page, Screeb highlights key indicators such as:

  • Sessions
  • Clicks
  • Friction
  • Last activity

You can also:

  • search for a page;
  • filter by date.



Caption: Review detected pages, traffic, and friction signals from the Heatmaps dashboard.


Dashboard highlights

At the top of the dashboard, Screeb surfaces notable page-level insights.

Page with the most friction

This identifies the page with the strongest friction signals, such as:

  • dead clicks;
  • rage clicks;
  • repeated interactions suggesting confusion.

Most visited page

This is the page with the highest number of recorded sessions during the selected period.

Lowest scroll rate

This highlights the page where users scroll the least on average, which can indicate that important content is placed too low or is not being reached.


URL normalization

To avoid duplicate entries caused by dynamic identifiers, Screeb normalizes similar URLs into a single pattern.

For example:

/org/123/survey/456/edit

and

/org/789/survey/999/edit

will be grouped as:

/org/:id/survey/:id/edit

This helps you analyze page templates instead of reviewing each dynamic URL separately.


Open a page analysis

Click Analyze next to a page to open its Heatmap analysis.

The analysis page includes:

  • Heatmap;
  • Scroll Map;
  • device filters;
  • date filters;
  • standard filters;
  • comparison mode;
  • AI Insights;
  • interaction metrics.



Caption: Analyze a specific page through clicks, scrolling, filters, and insights.


Reference rendering

The visual reference used for the analysis is selected automatically by Screeb.

You cannot change it manually.

Because the feature is in beta, some rendered elements may occasionally appear incomplete or slightly different from the live page.


Metrics

Each analysis page includes metrics to help you interpret behavior.

Page views

The number of recorded views for the page during the selected period.

Clicks

The total number of clicks captured on the page.

Dead click rate

A dead click is a click that does not trigger any visible action, navigation, or animation.

A high dead click rate often means users expect an element to be interactive or that an interaction is not behaving as expected.

Rage click rate

A rage click happens when someone clicks repeatedly in the same area within a short time.

This usually points to frustration, confusion, or a broken interaction.

Scroll rate

Scroll rate shows how far users scroll on the page on average.

It helps you understand whether important content is actually being reached.


Heatmap view

The Heatmap shows where users click.

Colors represent click intensity:

  • cooler areas indicate fewer interactions;
  • warmer areas indicate more interactions;
  • intense red areas indicate heavily clicked zones.

Use it to answer questions like:

  • Are users clicking the intended CTA?
  • Are they interacting with unexpected elements?
  • Are they clicking things that are not clickable?
  • Where does friction appear?



Caption: Use click intensity to identify highly engaged or problematic areas.


Scroll Map view

The Scroll Map shows how far users scroll on a page.

This helps you understand whether important content is placed too low or whether users stay mostly above the fold.



Caption: Measure how much of the page users actually reach.


The fold

The fold is the visible portion of the page before scrolling begins.

Content above the fold is immediately visible. Content below it requires scrolling.

This makes it easier to judge whether key information, CTAs, or messages are visible early enough.


Filters

You can filter Heatmap data to focus on a specific audience or context.

Available filters can include:

  • date range;
  • device type;
  • user properties;
  • events;
  • behavioral filters;
  • Heatmap-specific filters.

Device filters

Switch between:

  • desktop;
  • tablet;
  • mobile.

This is useful when behavior varies by screen size.

Behavior filters

Focus on a specific interaction type:

  • clicks;
  • dead clicks;
  • rage clicks.

Event and property filters

Narrow the analysis to users who match specific criteria, such as people who:

  • belong to a segment;
  • triggered an event;
  • used a feature;
  • experienced a negative event;
  • followed a specific journey.


Hotspots and selectors

Each hotspot is linked to a selector, which identifies the page element that received the interaction.

That element can be a button, link, div, span, or another HTML element.

Clicking a hotspot opens a detail panel with information such as:

  • selected element;
  • selector;
  • click count;
  • dead clicks;
  • rage clicks;
  • related sessions;
  • probable next clicks;
  • replay access;
  • follow-up actions.

The selected element is highlighted in the rendered view so you can locate it precisely.



Probable next clicks

Probable next clicks show the interactions that most often happened after the selected click in past sessions.

This helps you understand common next steps in the user journey and whether people move toward the expected outcome.


Open sessions from a hotspot

From a hotspot, you can open the sessions related to that interaction.

Screeb automatically applies contextual pre-filters so you land directly on the most relevant Session Replays.

This is useful when you want to move from aggregate behavior to real user context without rebuilding filters manually.


View a replay

You can also open a replay directly from the hotspot panel to inspect what happened before and after the interaction.

This is often the fastest way to understand friction in context.


Ask a question

The Ask a question action lets you create a survey targeted at people who clicked a specific element or performed a specific action.

Use it when you want to validate a behavior with direct feedback, for example to learn:

  • what users expected;
  • why they clicked;
  • whether they felt blocked or confused.


Display a message

The Display a message action lets you show a message or tour to people who performed a specific interaction.

This is useful for:

  • clarifying a feature;
  • guiding users to the next step;
  • reducing friction in context;
  • improving onboarding.


AI Insights

AI Insights help you interpret the page faster by surfacing meaningful interaction patterns.

They can highlight:

  • areas with many rage clicks;
  • elements that appear confusing;
  • unusual click behavior;
  • possible UX issues.



Caption: Review automatically generated insights to identify likely friction areas faster.


Comparison

Use Comparison to analyze how behavior differs across contexts.

You can compare:

  • two populations or segments;
  • behavior before and after a release;
  • users with different attributes;
  • users who completed an action versus those who did not.

This helps you determine whether a pattern is general or limited to a specific audience or product change.



Common use cases

Identify UX friction

Look for dead clicks and rage clicks on important pages to spot misleading or broken interactions.

Improve conversion pages

Check whether users see and click key CTAs by combining Heatmap and Scroll Map analysis.

Compare by device

Switch between desktop, tablet, and mobile to uncover layout or usability issues tied to screen size.

Investigate drop-off

Review what users clicked before abandoning a page, then open related Session Replays for context.

Prioritize improvements

Use friction signals, AI Insights, and replays together to focus on the issues affecting the most people.


Best practices

  • Use a wide enough date range to collect meaningful data.
  • Start with pages that combine high traffic and high friction.
  • Review both click behavior and scroll behavior before drawing conclusions.
  • Use filters to isolate a specific audience or behavior.
  • Open related replays to validate what the aggregated view suggests.
  • Use comparison mode to confirm whether an issue is widespread or limited to a segment.
  • Because the feature is in beta, validate important decisions with enough traffic and supporting evidence.


FAQ

Why can’t I see Heatmap data?

Heatmaps require Session Replays to be enabled. Without replay data, Screeb cannot generate Heatmaps.

Who can access Heatmaps?

Admins, Members, and Editors can access Heatmaps.

Is Heatmaps available on mobile?

Not yet. Heatmaps is currently in beta for Web only.

Do I need to configure Heatmaps manually for each page?

No. Heatmaps are generated automatically from recorded page activity once Session Replays are enabled.

Is there a minimum amount of data required?

Not for now. However, available results still depend on your Session Replay volume and quota.

What is a dead click?

A dead click is a click that produces no visible response, such as navigation, animation, or another UI change.

What is a rage click?

A rage click is a series of repeated clicks on the same area within a short period, usually indicating frustration.

What is the difference between Heatmap and Scroll Map?

Heatmap shows where users click. Scroll Map shows how far they scroll.

What is a selector?

A selector identifies the page element associated with a hotspot or interaction.

Why open sessions from a hotspot?

Because it gives you the full behavioral context behind a specific interaction, with the relevant filters already applied.

Can I change the reference view manually?

No. Screeb selects it automatically.

What does Ask a question do?

It creates a survey targeted at the population that interacted with a selected element.

What does Display a message do?

It lets you show a tour or message to users who performed that interaction.


Updated on: 29/04/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!