Skip to main content

Session Replay

Session Replay lets you see exactly what your users experienced — every screen transition, tap, scroll, network request, and error — reconstructed from real session telemetry.

What Session Replay Shows​

Each replay reconstructs the user's journey with:

  • Screen transitions — Every screen the user visited, in order
  • Interaction timeline — Taps, scrolls, and gestures overlaid on the session timeline
  • Network requests — HTTP calls with status codes, latency, and payload size
  • Errors and exceptions — Crashes, ANRs, JS errors, and non-fatal exceptions with stack traces
  • Performance markers — Slow renders, frozen frames, layout shifts
  • Device context — Device model, OS version, network type, battery level

Accessing Session Replay​

You can reach session replays from multiple entry points:

  • Session Explorer — Browse all sessions with filters
  • Anomaly Investigation — Jump to affected sessions from any anomaly
  • Interaction Detail — View sessions that completed or failed a specific interaction
  • PulseAI — When PulseAI identifies a root cause, it links to relevant session replays

Filtering Sessions​

The Session Explorer supports filtering by:

FilterExamples
Time rangeLast 1h, 24h, 7d, or custom
DeviceSamsung Galaxy S24, Pixel 8
OS VersionAndroid 14, iOS 17.2
RegionCountry, state, city
NetworkWiFi, 4G, 5G, specific carrier
App Versionv4.2.1
Error typeCrash, ANR, JS exception
Interaction outcomeCompleted, failed, abandoned
User IDSpecific user identifier

Privacy and Data Masking​

Pulse automatically masks sensitive information in session replays:

  • Text input fields — Form inputs (passwords, credit cards, personal data) are masked by default
  • Configurable masking — Define custom rules to mask specific views or data
  • No screenshots — Replays are reconstructed from telemetry events, not screen recordings, giving you context without capturing visual PII

Best Practices​

  • Start from an anomaly — Don't browse sessions randomly. Use anomaly detection to find affected sessions, then replay them with context.
  • Compare sessions — View a successful and a failed session for the same interaction side by side to spot the difference
  • Use user ID filtering — When investigating a user-reported issue, filter directly to their sessions

Next Steps​