Session replay

Watch the second it went wrong, not the whole session

A replay is evidence. InsightClickIQ summarises it from the event timeline, marks the moments that matter, links every finding elsewhere in the product to the right second, and lets you comment on that second and share it.

AI insights & Ask Agents Journeys Heatmaps & zones Forms Replay Segments Reports MCP Mobile Experiments Surveys Comments & sharing AI agent analytics Data platform

Replay and summary

What they wanted, what they did, where it broke

One click turns a session’s timeline into a summary: the visitor’s intent, the outcome, the frustration (rage and dead clicks, errors, loops) and highlights. Each highlight seeks the player; the timeline beside it lists every click, form step, error and page.

Sessions carry a frustration score from 0 to 100, so the list can be sorted by it and filtered by frustrated, errors, converted, device, country, path, length or a saved segment.

Session replay of ‘Anonymous jq9scq’ (San Francisco, 43s) paused on the Northwind cart page with the ‘Apply coupon’ button, a timeline of events on the right, and an AI summary with seven timestamped highlights from ‘Filtered to Jackets’ to ‘Rage-clicked ‘Place order’’. — The AI summary covers the whole visit in one paragraph: the coupon button was ‘completely unresponsive’, then ‘every attempt to place the order failed with a JavaScript crash’. Each highlight (0:16 Coupon button dead, 0:37 Place order JS error) has a Jump link.

Recording

What is recorded, and how it is kept private

Setting	Behaviour
Loading	The rrweb recorder (~23 KB gzipped) is fetched only when replay is enabled and the session is sampled in
Sampling	A per-project sample rate, decided once per session
Inputs	Every input, textarea and select is masked by default
Text	Elements matching `[data-private]` (or your selector) are masked
Blocking	`[data-clickiq-block]` elements are not recorded at all, and send no clicks or form events
Storage	Chunks every 5 s or ~512 KB, gzipped into your own object store (S3, Blob, GCS, OCI, MinIO), not the database
Consent	`clickiq("consent", false)` stops recording, clears the queue and ids, and is remembered
Native apps	Masked screenshots instead of a DOM: text inputs, web views and private views painted black on the device before encoding

Comments and sharing

Pin a note to the second, then send exactly that

The Comments panel under the player holds threads stamped with the playhead. Each shows as a violet dot on the progress bar beside the error and rage marks, and its chip (“0:16”) seeks the player. Replies, markdown, @mentions, resolve and reopen; viewers can comment too.

Share creates a public, read-only link to this one session with the scopes you pick (replay, comments, AI summary) and an expiry from 1 to 90 days. The link is shown once, counts its views and can be revoked. The person you send it to sees the player, timeline, summary and comments without an account.

Comments and share links in detail →

A Northwind session replay paused at 0:17 on the cart page with the Apply coupon button under the cursor; violet comment dots and orange and red error and rage marks on the progress bar; the timeline highlights ‘Dead click on Apply coupon’; below, a Comments panel with 3 threads at 0:10, 0:16 (with a reply) and 0:37, each stamped with its moment. — Comments are pinned to a moment: the violet dots on the progress bar are the three threads, and a ‘0:16’ chip seeks the player to the dead coupon click. The reply under it closes the loop (‘the click handler was dropped in the v2.4 cart refactor’). New comments are stamped with the playhead (‘at 0:17’).

Native apps

The same player for an iOS or Android session

The iOS, Android and React Native SDKs record masked screenshots: on a screen change, after a tap, and at most once a second while the screen changes. The player shows them in a phone frame with tap rings, on the same timeline, with the same AI summary, highlights, ?t= links, comments and share links. The session list marks native sessions with replay with a phone icon.

Native replay and its privacy controls →

An iOS session replay for iLearnRight: a phone frame showing the Lessons screen at 0:15 of 1:08 (frame 6 of 28) with the search field blacked out, the note ‘Native replay: screenshots taken on screen changes and taps; text inputs and private views were blacked out before upload’, the event timeline, and an AI summary describing a quiz loop with eight highlights such as ‘Redirected back to LessonList (loop #1)’ at 0:14. — Native replay is a series of masked screenshots, 28 for this 68-second session. The AI summary reads the event timeline and found a loop: the learner answered the Fractions quiz five times and was sent back to the lesson list each time. Each highlight’s **Jump** seeks the frame player.

How it works

A replay summary: from the event timeline to a highlight that seeks the player

Summaries read the event timeline, not the video pixels, which keeps them fast and keeps masked content out of the model.

What you can ask

Questions this answers

Type them into Ask, give them to an agent as a goal, or send them through MCP from your own assistant.

Summarise this sessionIntent, outcome, frustration and highlights

Show the most frustrated sessions on /checkout this weekSessions sorted by frustration, replays first

Sessions with the error “reading 'days'”The sessions behind an error fingerprint

Investigate sessions that abandoned the cartThemes across up to 40 replays

Sessions from Germany on mobile that convertedA filtered list, savable as a segment

What did user 1234 do yesterday?Their sessions and events

Outcomes

What teams do with it

Minutes, not hours, of watching

Start at the highlight the summary marks; skip the rest.

Evidence in the ticket

A link to the replay at the exact second goes into the bug report.

Recording you can defend

Inputs masked by default, private text masked, blocked regions never recorded.

Where it stops. Native replay is a series of stills (at most one a second), not video. Summaries describe what the events show; they cannot see content that was masked or blocked. A public link shows the cached summary and never calls the model.

AI insights & investigations Comments & sharing Mobile apps Security & privacy Web SDK