ScaleBun
Skip to article

Replays

Administrator

Replays in the Monitor area (Sessions) — route /monitor/replays.

Updated Reviewed

Replays lives in the Monitor area of the dashboard, under Sessions.

At a glance#

Dashboard route/monitor/replays
AreaMonitor (monitor)
GroupSessions
PlatformsAvailable for every app platform.

What it does#

Replays reconstruct a session from captured frames, touches, navigation, network activity and log breadcrumbs on one timeline. You watch what the user did, in order, alongside the errors and events that happened while they did it.

When to use it#

When you have a number you cannot explain. A funnel step with an unexpected drop-off, a crash you cannot reproduce, a support ticket that says "it didn't work" — replay is for turning those into something you can see.

It is a poor tool for measurement. One session is an anecdote; use Funnels or Performance for the distribution, then replay a session from the bucket you care about.

Workflow#

  1. Start from a signal, not the list

    Open replays from an error, a funnel drop-off or a bug report rather than browsing "all sessions". Unfiltered replay watching is slow and rarely representative.

  2. Watch the last 30 seconds first

    The cause is usually just before the symptom. Scrub backwards from the error marker rather than forwards from the session start.

  3. Check the network and log lanes

    A UI that looks frozen is often waiting on a request. The timeline shows both, which is the whole point of having them on one axis.

Limits and edge cases#

  • No frames at all is nearly always the missing optional peer dependency react-native-view-shot, or replay disabled by plan entitlement. See Session replay.

  • Masked regions are permanent. Masking happens on device before upload, so a masked screen cannot be un-masked later. That is the intended trade.

  • A session can look half-empty. The SDK maintains two session lanes and they are linked rather than merged, so track() events and replay frames land on different rows. See Core concepts.

Where the data comes from#

Frames come from the replay lane, which needs the optional react-native-view-shot peer dependency.

From the SDK

Served by

  • SDK ingestion

  • Replay redaction

Replays · Monitor · Dashboard · ScaleBun