LogClip
Platform/Analyze
Session Replay

Watch real visits, pixel for pixel.

Replay any visit like you were sitting beside them. LogClip reconstructs every click, scroll, and stumble — then drops you straight onto the moments that cost you conversions.

/sessions/b8c8ca3e
Session Replay in the LogClip console
Before you press play

Every visit, tagged before you open it

Recordings arrive already marked — errors, rage clicks, an abandoned cart, a slow LCP on mobile — each with a friction score out of 100 and a one-line read of what happened. Sort by friction and the worst visits come to the top; the row of filters above turns tens of thousands of recordings into the handful you care about.

/sessions
Every visit, tagged before you open it — the LogClip console
Inside the player

Everything the player does.

7 stops, each one a real screen from the console.

Search

Find the visit in one bar

One search bar filters recordings across ten dimensions — behavior, your tags, metadata, pages, signals, conversions, device, browser, country and user — and free text matches error messages, URLs and AI titles. Each suggestion shows how many recordings it would leave.

Type a word, pick a dimension, keep narrowing
Counts update as you go, so no filter lands on zero
Save any combination as a segment
/sessions
Session Replay — Find the visit in one bar
Player

Three ways to watch

The same recording, at the level of detail the moment needs. Product managers watch it like a video; engineers open the inspector and the seven-lane timeline underneath.

/sessions/b8c8ca3e
Session Replay — Three ways to watch — Watch

Full-stage replay with a slim scrubber — errors and rage still marked on it.

Navigate

Jump, don't scrub

⌘K opens a palette of the moments that matter in this recording: the next problem, the first error, every failed request with its time. Markers on the ruler do the same with a click, and idle stretches are skipped for you.

Next problem / previous problem from the keyboard
Every 5xx, rage burst and conversion listed with its timestamp
Playback speed, frame-step and fullscreen without touching the mouse
Share

Clip the twelve seconds that matter

Set a start and an end at the playhead, loop it, and copy a link. Whoever opens it lands on that clip with the same event selected in the inspector — no “skip to 4:32 and look at the network tab”.

Copy a link to the exact moment you're paused on
Clip links open with the selected request already expanded
Clips play in the embeddable player widget too
Session AI

The bug report writes itself

Every recording opens with a one-line synopsis and the moments behind it. Press Report bug and the session becomes a ticket: a title, a severity, steps to reproduce, and evidence with timestamps that link back into the replay. Or generate a Playwright test instead.

Title, severity, steps and evidence from the session itself
Open it in GitHub or Linear, or send it to a Slack webhook
A Playwright test that replays the failing path
Session Replay — The bug report writes itself
Identity

Know who it was

Call identify() once and every recording carries the person and whatever you attach — plan, order count, account. The visitor card shows their visit history, timezone, location and device, and one click filters to everything else they did.

Your metadata, shown on the recording and searchable
Returning vs first-time, with the visit count
Find a session from a support ticket by user id
Session Replay — Know who it was
Segments

Watch a cohort, not a session

Save a filter as a segment — “frustrated mobile visitors who didn't convert” — and see the match count live. Press Play and the matching recordings queue up beside the player; with autoplay on, each one advances to the next.

/segments
Session Replay — Watch a cohort, not a session — Segments

Saved segments with live match counts — build once, reuse everywhere.

Everything under session replay

Replay real sessions and land on the exact moment someone struggled — filtered by rage clicks, errors, and frustration.

01

Rage & dead-click detection

Every frustrated burst of clicks, and every click that did nothing, is flagged and jump-linked.

02

Friction score

One 0–100 number per visit, built from rage, errors, failed requests and slowness. Sort by it.

03

Seven-lane timeline

Chapters, interactions, console, network, errors, long tasks and Web Vitals on one synced ruler.

04

Network inspector

Headers, payload, response and timing for every request — WebSocket frames included.

05

DOM & state at any moment

Pause anywhere and inspect the page as it was, not as it is now.

06

Backend trace behind a failed call

A 500 in the replay opens the server-side trace that produced it.

07

Live sessions

Follow a visit as it happens and jump back to the live edge.

08

Auto-skip idle

The minutes where nothing moved are skipped for you; playback speed and frame-step are a key away.

09

Privacy at capture

Inputs and text are masked before they leave the browser; per-site rules decide what's kept.

10

Long and stitched sessions

Multi-hour visits play back; same-device returns within 30 minutes can join one recording.

11

Mobile replay

React Native sessions replay screenshot-first, with taps, rage taps and dead taps flagged.

12

Export & bulk actions

Tick rows, or keep your filters, and export the list as CSV or JSON — or delete what you don't want kept.

Session Replay

Why it matters.

01

Land on the struggle, not the noise

Filters surface the sessions with rage clicks, errors and failed requests, so you skip the happy paths and watch what hurts.

02

Privacy by default

Text and form inputs are masked at capture. You see behavior and intent — never passwords, card numbers or personal data.

03

Live and retroactive

Watch sessions stream in live, or replay any visit from the past with the full console, network and event timeline attached.

How it works

Minutes, not quarters.

Step 01

Drop in the snippet

One lightweight script captures sessions with under 2% overhead — no sampling.

Step 02

Sessions stream in

Visits are reconstructed in real time and auto-tagged with friction signals.

Step 03

Filter & replay

Pick a signal, hit play, and watch the exact moment of struggle.