Session Replay for the One Bad Session Your Team Cannot Reproduce
Aggregate analytics are for trends. This page is about the opposite problem: one specific session behaved badly, a support ticket references it by ID, and someone has to reproduce it. XR session replay is the tool for that ticket — a scrubbable, three-dimensional reconstruction of exactly what that user did, on that headset, in that room.
Reconstruct one session, not a heatmap of a thousand
Open a session by ID and see it played back inside the scene the user was actually in: their head pose over time, both controllers or hands, every object they picked up, every UI element they looked at, and every comfort or hesitation marker the SDK fired. Scrub the timeline like a video, jump directly to a marker, or step frame-by-frame through the two seconds before a stability event. This is the view engineers open when a chart is not a repro.
The three-second-before problem
The hardest XR bugs — a discomfort spike, a controller lost mid-interaction, a scene freeze — are almost always explained by what happened in the three seconds before the event, not the event itself. Every flagged marker in a session is anchored to a timestamp, and the replay player defaults to opening three seconds earlier. Engineers stop asking 'where in the video is the freeze' and start asking 'what was the user reaching for'.
What is not stored
Session replay reconstructs behavior from the capture layer described at /track-xr-user-behavior — pose, interactions, derived markers. There is no video recording of the user's room, no microphone stream, no camera feed. The replay you watch is a rendered reconstruction inside your own scene assets, not a screen grab. Legal, compliance and IT teams comparing session-replay tools should read the /privacy page before any procurement conversation.
Shipping the clip
A replay range can be shortened to the interesting seconds, annotated by the researcher who found it, and shared as a link that opens back inside the same 3D player for the engineer who has to fix it. The clip carries the session's cohort context — build, headset, scenario, tags — so the person who receives it has enough metadata to file the ticket without a second meeting.
What you get
- Reconstruct a single session by ID inside your own scene
- Scrub, step frame-by-frame, or jump to any flagged marker
- Default to three seconds before the event, not on it
- Reconstruction from pose/interaction data — no room video, no audio
- Shareable annotated clips with full cohort/build context attached
This is not surveillance and it is not a heatmap. Session replay here is a debugging surface for the one session that matters right now — the ticket, the crash, the discomfort spike — reconstructed from behavior signals, not recorded from the headset's cameras.