Heatmaps and Page Engagement
Page Engagement shows where visitors reach, spend time and click on a tracked page. Use it to investigate overlooked content, attention around key sections and click activity before deciding what to improve.
Open CRO & UX → Page Engagement. The report combines recorded activity over a captured version of the page; it is not an individual session replay.
Before you begin
Choose the workspace containing the website you want to review. You need access to that website, a tracked page with captured HTML or a screenshot, and recorded activity for the period you want to analyse.
If the website or page is missing, check Manage Session Tracking. Tracking setup and page captures are managed there, rather than in this report.
Review a page
- Select the domain in the context bar above the report.
- Select Change page, search by part of the URL if needed, and choose a tracked page.
- Choose Scroll depth, Time spent or Click heatmap.
- Open Device and select Desktop, Mobile or Tablet.
- Open Range and select 7 days, 30 days, 60 days or 90 days.
- Choose All traffic, Prospects or Identified visitors from the audience menu.
- Scroll inside the page preview to review the overlay across the page. Hover over bands or hotspots for additional detail.
The page and analysis load automatically. Changing the device reloads the preview and data; changing the range, audience or analysis refreshes the overlay. You do not need to save or apply the filters.
The page picker lists tracked pages for the selected domain, not every URL on its live website. When you select a domain, the report restores its last selected page in this browser where possible, or selects the first available page.
Understand the page preview
The preview can use captured HTML or a screenshot, according to the page’s configured capture method and available assets. If the preferred asset is missing, the report can use the other available format.
Captured HTML displays the saved page content at the selected device width. Scripts from the original page do not run, so interactive menus, animations, forms and personalised content may behave differently or be absent. A screenshot is a static image of the captured page.
Scroll within the preview to move down the page. The HTML preview keeps a stable viewing height as you scroll, including on pages with sections designed to fill a browser window. A desktop layout can be wider than the available report area; use horizontal scrolling to inspect the rest of it. Selecting Mobile changes the device data as well as the preview width, so use it when you want to analyse mobile behaviour.
The preview is a visual reference, not a historical reconstruction for every visit. A page redesign, changing banners or different personalised content can affect the alignment of recorded activity. After an important layout change, update the capture in Manage Session Tracking and consider a shorter reporting range.
Choose an analysis
Scroll depth
Scroll depth divides the page into 2% vertical zones. Each band identifies the zone, its reach percentage and its recorded visitor count. Wider pink bands indicate greater reach within the selected report.
Use this view to check whether visitors reach important content or calls to action, and where recorded reach falls.
Reach is calculated relative to the zone with the highest recorded visitor count in the current selection. For example, if that zone has a count of 200 and another has 100, the second shows 50% reach. A value of 100% therefore means the zone matches this report’s baseline; it does not prove that every visitor to the website reached it.
Counts combine recorded aggregates across the selected period. They are not a deduplicated count of individual people across all dates. Do not add the zone counts together: the same activity can contribute to multiple zones.
Time spent
Time spent shows average recorded time within each 2% zone. Labels show the average in seconds and, where available, the session count and percentage. Hovering over a band can also show the zone’s share of total recorded time.
Band width is relative to the zone with the highest average time in this selection. A full-width band means the highest average in this report; it does not mean 100 seconds or all time spent on the page.
The average divides recorded time in a zone by that zone’s aggregated visitor count, displayed here as sessions. The session percentage uses the highest zone count as its baseline, just as Scroll depth does. Treat these as aggregate measures rather than a count of distinct individual sessions across the whole period.
Use this view alongside Scroll depth. A section with strong reach but little recorded time may be passed quickly. Longer time can indicate interest or difficulty; time alone does not establish whether the content helped someone complete their task.
Click heatmap
Click heatmap places recorded click activity over the page. Hotspots indicate concentrated activity. Hover over an area to see the available click count, and check the footer for the total recorded clicks in the selection.
Use it to investigate calls to action, navigation and areas that may look clickable. Hotspot intensity helps locate activity; use the counts when comparing selections, rather than colour alone.
Clicks are positioned using relative page coordinates. A hotspot does not independently identify the clicked control or confirm a successful conversion. Overlapping points can contribute to the count shown near the pointer. Use Session Replay to investigate the sequence behind a pattern.
Choose filters and compare results
| Filter | What it changes |
|---|---|
| Device | Selects Desktop, Mobile or Tablet activity and the corresponding preview width or screenshot. |
| Range | Selects activity from the last 7 days, 30 days, 60 days or 90 days. The initial selection is 30 days. |
| Audience | All traffic includes both audience classifications. Prospects selects activity recorded as unauthenticated; Identified visitors selects activity recorded as authenticated. |
Audience classification depends on how tracking records the visitor. Prospects does not establish sales qualification, and Identified visitors does not reveal names in this report. The selected audience chip and footer may display these labels as All Traffic and Identified Visitors.
For a useful comparison, keep the page, range and audience the same while changing device. Then compare audiences or ranges separately. Larger ranges can provide more activity but may combine different page layouts.
The footer repeats the domain, device, range and audience. Its count changes with the analysis: visitors for Scroll depth, sessions for Time spent, and clicks for Click heatmap. The visitor and session totals use the highest zone count as their baseline; they are not sums of every band. Small samples can produce large-looking changes, so check counts before acting.
Export an image
- Select the page, analysis and filters you want to share.
- Select the download icon, labelled Export Page Engagement image.
- Wait while the export is prepared. A PNG image downloads when it is ready.
Export requests a screenshot for the selected page and device and draws the selected engagement overlay onto it. This applies even when the on-screen preview uses captured HTML, so the exported background may look different from the preview. The request does not guarantee a newly refreshed capture.
The export includes the full-page screenshot where available, rather than only the part currently visible. Very tall captures can be scaled down and a large blank tail can be cropped. An available report chart can also be included.
Keep the downloaded PNG as a snapshot of the report. It does not update when new activity arrives.
Return to the report
Page Engagement is a viewing and export tool. It does not create a saved report when you change filters, and viewing it does not change your tracked page or conversion setup.
The last selected page for each domain is remembered in the current browser where browser storage is available. Check the device, range and audience each time you return; do not assume the previous filters have been restored.
Changing filters requests the available recorded data again. Reloading the report can retrieve updated data, but does not by itself guarantee a fresh page capture or newly processed activity.
If something does not look right
A domain or page is missing
Check the active workspace, your access to the domain and the page’s configuration in Manage Session Tracking. Search using part of the stored URL. Changing workspace reloads the available domains and pages.
No captured HTML or screenshot is available
Check the capture for the tracked page in Manage Session Tracking, including the selected device where applicable. Allow capture processing to finish, then return to Page Engagement. The report needs a usable visual reference as well as behaviour data.
The preview has missing content, incorrect sizing or awkward scrolling
Wait for the preview to finish loading, then reload the report. Scroll inside the preview and check whether horizontal scrolling is needed for the selected device width.
If the issue continues, review or refresh the page capture. Captured HTML cannot reproduce all scripted content, and missing fonts, images or styling can change its appearance. A screenshot capture can provide a different visual reference for pages that rely heavily on scripts.
The overlay is empty
Try a longer range, All traffic and another device. Confirm that tracking was enabled and recording eligible activity for that page. A visible page preview does not mean behaviour data exists for every filter combination.
Hotspots or bands appear in the wrong place
Check the selected device and whether the page changed during the selected period. Refresh an outdated capture and compare a shorter range. Relative coordinates and differences between page versions limit alignment; the overlay is not a pixel-perfect record of every historical visit.
Time or reach looks surprising
Check the counts, compare another period and review relevant sessions before drawing conclusions. Read reach against the report’s highest-count zone, and time-band width against its highest-average-time zone. Neither width is a conversion rate.
Export fails or no download appears
Wait for the current page to finish loading and retry the export. Check browser download permissions. Export requires the screenshot service to return an image even if the HTML preview works; a working preview alone does not guarantee a successful export.
Continue your investigation
Use Session Replay to examine individual journeys behind an aggregate pattern. Use Page Optimisation to investigate improvements to the page, and Manage Session Tracking for tracking settings and captures. Use Manage Conversions when you want to define the actions that count towards a conversion rather than infer outcomes from engagement alone.