Heatmaps and Page Engagement

Page Engagement shows where visitors reach, spend time and click on a tracked page.

Overview

Use Page Engagement to:

• see how far visitors progress down a page;
• identify sections where visitors spend more or less time;
• find concentrated click activity;
• compare desktop, mobile and tablet behaviour;
• compare prospects, identified visitors or all recorded traffic;
• review activity over 7, 30, 60 or 90 days; and
• export the selected page and overlay as a PNG image.

Page Engagement places aggregated behaviour data over a stored screenshot of the page. It is a page-level analysis, not a replay of one visitor’s session.

Access and scope

Page Engagement is workspace-, website- and page-aware.

• The active workspace controls which websites are available.
• The website selector contains only accessible websites in that workspace that have tracked pages.
• The page selector contains tracked URLs belonging to the selected website.
• Changing workspace reloads the available websites and pages.
• Markets are not used.

The selected page must remain in the active workspace. Wheremore checks this again when it loads the screenshot and each set of engagement data.

If a website or page is missing, check its workspace membership and its configuration in Manage Session Tracking.

Before you begin

You need:

1. A website in the active workspace.
2. The Wheremore pixel installed on that website.
3. Tracking enabled.
4. The page added as a tracked URL.
5. A stored screenshot for each device type you want to analyse.
6. Eligible visitor activity for the selected date, device and audience.

New activity can take time to pass through collection and background aggregation before it appears.

Quick start

1. Open Page Engagement.
2. Confirm the active workspace.
3. Select a website.
4. Select a tracked page.
5. Choose Scroll depth, Time spent or Click heatmap.
6. Select Desktop, Mobile or Tablet.
7. Choose a date range.
8. Select All traffic, Prospects or Identified visitors.
9. Scroll through the captured page and review the overlay.
10. Select the download button when you need a PNG export.

Select a website and page

The website and page appear in the dark context bar above the report.

Change website

1. Select the website name.
2. Search when the workspace contains many websites.
3. Select the website you want to analyse.

Wheremore then loads that website’s tracked pages and selects the first available page. Where possible, it remembers the last selected page for that website in the current browser.

Change page

1. Select Change page.
2. Search by URL when needed.
3. Select a tracked page.

The stored screenshot and current analysis reload for the new page.

The page selector is not a list of every live URL on the website. It contains pages configured in Manage Session Tracking.

Choose an analysis

The three tabs use the same selected page, device, date range and audience.

Scroll depth

Scroll depth shows how much of the selected audience reached each part of the page.

The page is divided into 2% vertical zones. Each zone label shows:

• the zone’s position on the page;
• the percentage of qualifying visitors who reached it; and
• the number of qualifying visitors represented.

The width and strength of each pink band communicate reach. Wider coverage means a larger share of the selected audience reached that part of the page.

Use Scroll depth to find:

• where reach begins to fall;
• whether important content appears below a major drop-off;
• whether calls to action are positioned before or after visitors leave; and
• differences between devices or audiences.

The percentage is calculated against the qualifying visitor baseline for the same page, date range, device and audience. A visitor represented at adjacent stored scroll percentages is counted once within each displayed 2% zone.

Time spent

Time spent shows average recorded attention within each 2% page zone.

Each zone label can show:

• the zone’s position;
• average time per qualifying session;
• the percentage of qualifying sessions represented; and
• the number of sessions.

The band width is relative to the zone with the highest average time in the current selection. A full-width time band therefore means “highest average time in this report”, not 100 seconds or 100% of total time.

Use Time spent to identify:

• sections that hold attention;
• sections visitors pass quickly;
• complex areas that may require unusually long reading time;
• content that receives little attention despite strong scroll reach; and
• device-specific reading patterns.

Longer time is not automatically better. It can reflect useful engagement, confusion, slow-loading elements or visitors leaving the tab open. Compare it with scroll depth, clicks and the page’s purpose.

Click heatmap

Click heatmap places aggregated click intensity over the stored page screenshot.

• Hotter areas represent more recorded clicks.
• Cooler or empty areas represent fewer or no qualifying clicks.
• Hover over a hotspot to see the available click count.
• The footer shows the total click count for the current selection.

Use Click heatmap to find:

• calls to action receiving attention;
• navigation items visitors use;
• non-interactive elements that appear clickable;
• important controls receiving few clicks; and
• differences between desktop, mobile and tablet layouts.

The heatmap combines qualifying clicks by their relative page coordinates. It does not identify an individual visitor or reproduce the exact click sequence from one session. Use Session Replay when sequence and context matter.

Apply the filters

Changing a filter reloads the current analysis.

Device

Choose:

• Desktop
• Mobile
• Tablet

Device selection affects both the engagement data and the screenshot used as the page background.

If a device screenshot is missing, that view cannot be represented accurately. Refresh the page capture in Manage Session Tracking and try again.

Date range

Choose:

• 7 days
• 30 days
• 60 days
• 90 days

The default is 30 days.

A longer range increases the available sample but can combine behaviour from different page versions. If a page changed recently, use a shorter range and confirm when its screenshot was captured.

Audience

Choose:

• All traffic: all qualifying recorded activity;
• Prospects: activity not marked as authenticated or identified; or
• Identified visitors: activity marked as authenticated or identified by the tracking configuration.

The default is All traffic.

“Identified” is an audience classification. It does not mean the report reveals a person’s private identity.

The classification depends on the Cookie or Cookieless setup, authenticated-user rules and exclusions configured in Manage Session Tracking.

Read the status bar

The footer beneath the page shows the active:

• website;
• device;
• date range; and
• audience.

Its right-hand value changes with the selected analysis:

• Scroll depth shows qualifying visitors.
• Time spent shows qualifying sessions.
• Click heatmap shows recorded clicks.

This is the sample represented by the current view. Small samples should be treated cautiously.

Export the report

Select the download button to create a PNG image of the current Page Engagement view.

The export uses:

• the selected page;
• the selected device;
• the active analysis;
• the selected date range;
• the selected audience; and
• the corresponding engagement overlay.

The exported image is built from a full-page screenshot where supported. Very long pages can be scaled, and a large blank tail can be removed from the final image.

Export can take longer than changing an on-screen filter because Wheremore must prepare the screenshot and draw the current overlay into the image.

If the download does not appear:

1. Wait for the export message to finish.
2. Check whether the browser blocked the download.
3. Confirm the page has a valid screenshot for the selected device.
4. Retry after the current page view has fully loaded.

How the screenshot affects interpretation

Page Engagement uses a stored page screenshot as the visual reference. It does not load the live website into the report.

This means:

• the screenshot can be newer or older than some activity in the selected range;
• content or layout changes can affect alignment;
• personalised or third-party content may differ;
• cookie banners and dynamic widgets can be absent or appear differently;
• mobile, tablet and desktop require their corresponding captures; and
• a very long or incomplete screenshot can affect lower-page alignment.

The behaviour data remains scoped to the tracked page, but the overlay is only as visually accurate as the screenshot and recorded relative coordinates.

Refresh the stored capture after an important redesign or layout change.

Recommended workflow

1. Start with Desktop, 30 days and All traffic.
2. Review Scroll depth to find the main reach drop-offs.
3. Review Time spent at those same page sections.
4. Review Click heatmap for calls to action and misleading visual cues.
5. Repeat the review for mobile and tablet.
6. Compare prospects with identified visitors.
7. Check that the sample is large enough before acting.
8. Use Session Replay to understand the sequence behind a pattern.
9. Use Page Optimisation when a specific section needs analysis.
10. Use the Conversions Dashboard when the question concerns business outcomes.

What should I do next?

• Use Session Replay to inspect individual journeys behind the aggregate pattern.
• Use User Behaviour Dashboard to compare behaviour across pages.
• Use Page Optimisation to investigate content or structural problems.
• Use Link Management when click behaviour points to navigation or internal-link issues.
• Use Manage Session Tracking to refresh screenshots or change tracking, consent and exclusion settings.
• Use Manage Conversions and the Conversions Dashboard to connect engagement with outcomes.

Troubleshooting

No websites appear

• Confirm the correct workspace is active.
• Confirm the website belongs to that workspace.
• Confirm you have access to it.
• Confirm at least one tracked page exists for the website.

No pages appear

• Open Manage Session Tracking.
• Confirm the URL is listed under the correct website.
• Confirm the tracked page has not been deleted.
• Search using part of the stored URL.

The page says no screenshot is available

• Confirm the selected device.
• Refresh the page capture in Manage Session Tracking.
• Allow screenshot processing to finish.
• Reload Page Engagement.

The overlay is empty

• Increase the date range.
• Switch to All traffic.
• Check another device.
• Confirm tracking was enabled during the selected period.
• Confirm the pixel and consent configuration allowed the activity to be recorded.

Reach used to show more than 100%

The corrected report counts the stored visitor total once per date, device, audience and 2% display zone. Reach is also capped at 100%. Values above 100% indicated duplicate aggregation and should no longer appear.

Scroll percentages fall sharply

This can be genuine, especially on long pages or small samples. Compare:

• the visitor count;
• another date range;
• another device;
• Time spent; and
• relevant Session Replays.

Time spent looks unusually high

• Check the number of sessions.
• Compare a shorter date range.
• Consider whether visitors may leave the tab open.
• Review Session Replay for loading, hesitation or interaction problems.

Click hotspots do not align

• Refresh the stored screenshot.
• Confirm the correct device is selected.
• Check whether the page layout changed during the date range.
• Remember that relative coordinates are aggregated and visual alignment is best-effort.

Export fails or no file downloads

• Let the screenshot and overlay finish loading.
• Check browser download permissions.
• Confirm the screenshot exists.
• Try a shorter page or another device.
• Retry after any background screenshot capture has completed.

Frequently asked questions

Is Page Engagement a session replay?

No. It aggregates behaviour from qualifying activity and displays it over a page screenshot.

Does Page Engagement use markets?

No. It uses workspace, website, tracked page, device, date range and audience.

Is a 100% scroll value an error?

Not necessarily. It means the zone was reached by the full qualifying baseline in the selected scope.

Does a wider Time spent band mean more visitors?

No. Its width represents average time relative to the highest-average zone in the current report. Read the session count in the label as well.

Are click heatmaps exact?

They are aggregated relative coordinates placed over a stored screenshot. They are directional rather than a pixel-perfect historical record.

Does Identified visitors reveal names?

No. It filters by the stored authenticated or identified classification.

Does changing device only resize the screenshot?

No. It also filters the underlying engagement data by device type.

Does export download the live webpage?

No. It creates an image from the available page capture and the current engagement overlay.