Using the replay player

Click a session to open the player.

Playback controls

• Play/pause and a timeline scrubber to seek anywhere.
• Speed — 1x, 2x, 4x or 8x.
• A current-time / total-duration readout.

Activity timeline

A histogram shows event density across the session — click any point to jump there. Colour-coded markers flag navigation, clicks, errors, rage clicks, network requests and console logs.

Event list

A chronological list of everything captured (navigations, clicks, inputs, custom events, scrolls, resizes, errors…). The active event highlights as playback progresses, and you can click any entry to jump to it.

Console & Network panels

• Console — captured log/info/warn/error messages with timestamps, colour-coded by level.
• Network — requests with method, URL, status code (colour-coded), duration and time within the session.

Session details

The side panel summarises the session: when it Started, its Duration, Device, and counts of Events, Errors and Rage Clicks. From there, View in Error Logs jumps straight to the error's entry in Logs to see how often it happens across every session.

Arriving mid-session

Replay links from elsewhere in Spectry — a rage-clicked element, an abandoned form, a survey drop-off, a funnel step — open the player at the moment in question rather than at the start. If a link drops you into the middle of a session, that's deliberate: scrub backwards for the lead-up.

Getting value out of replays

• Watch in batches. One session is an anecdote. Five sessions with the same filter start to show a pattern.
• Play at 2x and slow down at the interesting part. Most of a session is reading and scrolling.
• Start from a number, not from the list. Come in from a heatmap hotspot, a funnel drop-off or an error — watching random sessions is absorbing and rarely conclusive.

Replay tells you why; the aggregate reports tell you how often. Confirm anything you see in a replay against a funnel or a heatmap before rebuilding a page around it.