Watch it happen, then open the trace

The replay shows what the user did. The trace shows why it broke. One click takes you from one to the other.

The surface

The replay next to its console and network log

Console logs, network requests and errors play back on the same timeline as the user's clicks.

/replays session s_9f31 · 6:12

In motion

The user clicks Pay now, and each event appears alongside with its trace id.

replay · checkout flow LIVE

app.acme.com/checkout Chrome macOS Desktop

trace ↳ 9f3c · POST /api/pay 1.24s · 5 spans

edge 1.24s

api 180ms

payment-svc 880ms

stripe 690ms

postgres 85ms

1 session · 9 events · 2 errors trace-linked · 30d retention

What it does

Every event, in order: Clicks, inputs, console logs, network calls and errors in one timeline, each linked to its trace.
DOM replay: The SDK records DOM changes instead of video. Scrolling, hovers and typing play back exactly, at any screen size.
From a moment to a span: Pause on a failed click and open the request it sent.
Console and network, inline: Every request with its method, status and duration. A failed checkout shows up the moment it happens.
Masked before it leaves: Inputs and text are masked in the browser before anything is sent. You control sampling and masking in the SDK.

Keep going

Follow every request across services

Exceptions grouped into issues, linked to the span that threw them

Funnels, drop-off and paths on your events

Trace a failed checkout by its order id

One endpoint, one key. Traces, logs, metrics and sessions, linked from the first request.