Session replay glossary
These entries define terms you will see in Replayly's product, docs, and compare pages. Each one links on to a feature or guide, and is long enough to be useful on its own.
Session replay
Session replay is a reconstruction of a user's visit to a website or app, built from events the page emitted — such as clicks, scrolls, and DOM changes — rather than from a camera or a screen-recording file. In Replayly, a lightweight tracker sends those events to ingest, and a player in the dashboard plays them back with speed controls, skip inactivity, and a metadata panel.
Heatmap
A heatmap is an aggregate visualization of user behavior on a page. A click heatmap shows where clicks and taps clustered. A scroll heatmap shows how far people typically reached. Replayly offers click and scroll heatmaps on Pro and Business, generated from the same recordings used for session replay.
Rage click
A rage click is a tight burst of repeated clicks or taps on the same element. It usually means the visitor expected a response — a page change, a menu, a submit — and did not get one. Replayly can mark and filter sessions that include rage clicks so you can review those visits first.
Dead click
A dead click is a click or tap that does not produce a meaningful response in the page — no navigation, no visible state change, no control firing. It is quieter than a rage click but often points to the same class of problem: the UI suggested that something was interactive.
Session recording
Session recording is a general term for capturing what happened during a visit so someone can review it later. In Replayly, session recording means event-based session replay: the tracker records interface events and the player reconstructs the page. It is not a webcam, a microphone, or a full raw video of the user's screen outside the page.
Input masking
Input masking replaces or hides the values a visitor types into form fields so those values do not appear as plaintext in a recording. Replayly masks input values by default, from the first snippet, rather than treating masking as an optional evening project after you already collected data.
Consent mode
Consent mode is a tracker setting that keeps Replayly from recording until your site says the visitor has agreed. Your page typically shows a banner or preference center, then calls a small JavaScript API such as the documented consent helper, after which the tracker may start.
Do Not Track
Do Not Track (DNT) is a signal a browser can send, usually as an HTTP header, to ask services not to track the visit. Support and enforcement vary across browsers and sites, but Replayly can respect the signal and avoid recording when it is present.