Session Replay

Session Replay reconstructs eligible visitor sessions so you can review page journeys, scrolling and clicks in context.

Overview

Use Session Replay to:

filter sessions by website, page and date;
separate prospects from identified visitors;
focus on human traffic or sessions containing rage clicks;
inspect conversion-path drop-offs;
review the referrer and page journey for each session;
replay recorded interactions at different speeds;
jump to points on the playback timeline;
inspect recorded engagement events; and
delete an individual stored session.

Session Replay depends on Manage Session Tracking. A website must have the Wheremore pixel installed, tracking enabled and at least one eligible tracked page before new sessions can appear.

Access and scope

Session Replay is workspace- and website-aware.

The active workspace controls which websites and sessions are available.
The website filter contains only accessible websites in that workspace.
A replay is available only when every website associated with the session belongs to the active workspace.
Changing workspace reloads the website and page filters.
Markets are not used. Session Replay is scoped by workspace, website and tracked URL.

If a website is missing, confirm that it belongs to the active workspace and is configured in Manage Session Tracking.

Before you begin

You need:

A website in the active workspace.
The Wheremore pixel installed on that website.
Tracking enabled.
One or more tracked URLs.
A suitable Cookie or Cookieless tracking configuration.
At least one eligible processed session.

New activity can take time to pass through ingestion and background session processing.

Quick start

Open Session Replay.
Confirm the active workspace.
Select a website or leave All Domains selected.
Optionally select a page and date range.
Choose Prospects, Identified Visitors or All Traffic.
Apply Human traffic only, Rage clicks only or a drop-off filter when useful.
Select Play beside a session.
Use the timeline, speed and playback controls to review the visit.
Open the engagement panel to inspect recorded clicks.

Filter the session list

Filters can be combined. The list reloads when a filter changes.

Website

Select All Domains to view eligible sessions across the active workspace, or select one website to narrow the report.

When only one accessible website is available, Wheremore can select it automatically.

Date range

Choose:

Today
Last 3 Days
Last 7 Days
Last 14 Days

The default range is Last 7 Days.

Audience

The audience filter defaults to Prospects.

Prospects: sessions not marked as identified or authenticated.
Identified Visitors: sessions marked as identified or authenticated by the tracking configuration.
All Traffic: does not apply the prospect/identified filter.

An identified visitor is a classification signal. The list does not reveal a person’s private identity unless another authorised feature has legitimately collected and exposed that information.

Human traffic only

Select Human traffic only to restrict the list to sessions classified as human traffic.

This is a screening signal, not a guarantee that every automated visit is removed or that every genuine visitor is retained.

Rage clicks only

Select Rage clicks only to show sessions marked as containing repeated rapid clicks on the same element.

A rage-click signal can indicate frustration, but it can also reflect an unusual interface or interaction pattern. Review the replay before drawing a conclusion.

Search

Use Search sessions to search the available session IDs and referrer values within the active filters.

Drop-offs only

The Drop-offs only control appears after selecting a page that belongs to at least one configured conversion path.

Select a website.
Select a page.
Enable Drop-offs only.
Select the relevant funnel step when the funnel selector appears.

Wheremore then looks for sessions that entered the path but did not reach the selected step or later qualifying steps, according to the selected drop-off context.

The entry step of a path cannot be treated as a preceding-step drop-off target.

Read the session table

Each session row includes:

Session ID: the stored session identifier;
Date / Time: when the session began;
Duration: elapsed time represented by the processed session;
Device: the recorded device class;
Browser: the recorded browser;
Rage: shown when the session contains the rage-click signal;
Play: opens the replay drawer; and
Delete: permanently removes that stored session data.

The journey beneath the main row shows:

ref: the first recorded referrer, or Direct;
p1: the first recorded page;
p2, p3 and later labels: subsequent recorded pages.

The sequence is a processed page journey. Missing page labels can reflect incomplete events, excluded pages or processing limitations.

Sort and paginate

Select a sortable table heading to change the order. Selecting the same heading again reverses the direction.

Use the controls beneath the table to move through the available session pages. The current implementation requests 20 sessions per report page.

Play a session

Select Play on a session row. Wheremore loads:

authorised interaction events;
the stored HTML representation for pages using HTML mode;
stored screenshots for pages using screenshot mode; and
the recorded device dimensions where available.

The player follows recorded page changes, scrolling, pointer movement and clicks supported by the stored events.

Playback controls

Play starts or resumes playback.
Pause temporarily stops playback at the current point.
Stop returns playback to its initial state.
Playback Speed changes speed from 0.25× to 4×.
Close closes the replay drawer.

Changing speed during playback keeps the current playback position.

Timeline

The timeline shows playback progress and recorded click markers.

Select a point on the timeline to move to that moment.
Drag across the timeline to scrub through the session.
Select a click marker to jump to that event.

Engagement panel

Select the eye control to open or close the engagement panel.

The panel lists recorded click events and their approximate timing and page position. Select an event to jump to it in the replay.

If the session contains no usable click events, the panel displays an empty state.

How replay rendering works

Session Replay is a reconstruction, not a video captured from the visitor’s screen.

For each tracked page, Wheremore uses the active stored representation:

HTML mode reconstructs the page from captured HTML; or
Screenshot mode displays the stored screenshot that best matches the recorded device type.

Wheremore then applies eligible recorded interactions over that representation.

This has several consequences:

the replay can differ from what the visitor saw if the page changed after capture;
third-party or personalised content may not match the original visit;
fonts, images or styles can be unavailable if their source blocks replay loading;
coordinates and scrolling are best-effort when layouts differ; and
an incomplete interaction stream can produce an incomplete replay.

Saved page scripts do not run

Captured page scripts are deliberately prevented from executing inside the replay frame.

This protects the Wheremore application and prevents a replay from:

submitting forms;
running live analytics;
loading arbitrary saved JavaScript;
changing external systems; or
behaving like the live website.

As a result, script-built widgets, consent tools, menus or forms may appear static or may not render exactly as they did during the original visit.

Delete a session

Select the delete control and confirm the prompt.

Deleting a session removes its:

stored interaction events;
associated conversion events; and
processed session summary.

It does not:

delete a live website page;
remove the tracked URL from Manage Session Tracking;
delete the page’s captured HTML or screenshots; or
turn off future tracking.

Deletion is permanent for the selected stored session.

Recommended workflow

Start with Prospects and Human traffic only.
Narrow to one website and a short date range.
Review session journeys before playing individual visits.
Use Rage clicks only to investigate possible friction.
Select a tracked page and use Drop-offs only for conversion-path investigation.
Compare several sessions before treating one behaviour as a pattern.
Use Page Engagement or the User Behaviour Dashboard to quantify a pattern.
Use Manage Session Tracking to correct tracking, consent or exclusion configuration.
Use Manage Conversions when the path or step definition needs changing.

What should I do next?

Use User Behaviour Dashboard to identify broader engagement patterns.
Use Page Engagement to measure behaviour on a specific page.
Use Conversions Dashboard to review conversion outcomes.
Use Manage Conversions to configure paths and steps.
Use Manage Session Tracking to add pages, change tracking mode or refine exclusions.
Use Page Optimisation when replay evidence identifies a page-level usability or content issue.

Troubleshooting

No websites appear

Confirm the active workspace.
Confirm the website belongs to that workspace.
Confirm your account can access it.
Confirm it exists in Manage Keywords and Manage Session Tracking.

A website appears but no pages are available

Confirm tracked URLs exist for that website.
Check whether the wrong website is selected.
Reload after changing workspace.
Review Manage Session Tracking for deleted or failed page records.

No sessions are found

Increase the date range.
Change Prospects to All Traffic.
Clear Human traffic, Rage clicks and Drop-offs filters.
Select All Domains and All Pages.
Confirm the pixel and tracking configuration in Manage Session Tracking.
Test using a new eligible visit.
Allow ingestion and background processing time.

A known visit is missing

Confirm the visitor opened a tracked URL.
Confirm tracking was enabled.
In Cookie mode, confirm accepted consent was present.
Check authenticated-user, URL-path and custom exclusion rules.
Confirm the visit belongs to the active workspace.
Check whether Human traffic only or the audience filter excludes it.

Drop-offs only does not appear

Select a specific page rather than All Pages.
Confirm that page belongs to a configured conversion path.
Confirm the path and its steps are active and accessible.

The replay opens but is blank

Allow the replay assets to load.
Confirm stored HTML or screenshots exist for the page.
Refresh the page capture in Manage Session Tracking.
Check whether external images or styles block replay loading.
Try another session to distinguish a page-capture problem from a session problem.

The page looks different from the live website

This is expected when the stored capture is older than the live page, the visit contained personalised content, or external assets are unavailable. Refreshing the tracked-page capture can improve future presentation but does not recreate the historical page exactly.

Saved page scripts do not execute in the replay. Interactive elements are visual context only.

The cursor or scroll position looks inaccurate

The player maps recorded coordinates onto stored page dimensions. Layout changes, missing assets and incomplete viewport data can reduce accuracy.

Rage clicks returns no sessions

No processed sessions in the active scope currently carry the rage-click signal. Increase the date range or clear other filters.

Deleting a session fails

Confirm the session still exists.
Confirm the active workspace contains every website associated with it.
Confirm you are signed in and the page is not using a stale request token.
Reload and retry.

Frequently asked questions

Is Session Replay a video recording?

No. It reconstructs stored interactions over captured HTML or screenshots.

Does replay execute the website’s JavaScript?

No. Saved page scripts are deliberately prevented from running.

Are markets used?

No. Session Replay uses workspace, website and page scope.

Why does the list default to Prospects?

It keeps the initial view focused on sessions not marked as identified or authenticated.

Does Human traffic only guarantee that every session is human?

No. It applies the available classification signal.

Does deleting a session stop future tracking?

No.

Can I replay activity from an untracked page?

Not reliably. The page must be eligible for tracking and have a usable stored representation and interaction data.

Why can a replay be incomplete?

Events, page captures or external assets can be missing, excluded, blocked or still processing.