See exactly what the user did.
Traceway captures ~10 seconds of user activity before every error. Clicks, scrolls, and form interactions are attached to exceptions automatically. No manual reproduction needed.
See exactly what the user did
Traceway captures ~10 seconds of user activity before every error. Clicks, scrolls, and form interactions are attached to exceptions automatically, with no manual reproduction needed.
- Pre-error activity capture
- Automatic attachment to exceptions
- Clicks, scrolls, and form interactions
- Page navigation timeline
Watch the moments before every error
Traceway records DOM changes in the browser, not screenshots. You can scrub through the timeline, pause on the exact moment things went wrong, and see the user's real interaction.
- Lightweight DOM snapshot recording
- Scrub through exact user timeline
- Console and network overlays
- Trace ID links every replay to the backend
Zero-config capture. Privacy-first by default.
Attached to every exception, automatically
No manual setup or reproduction steps. Every exception gets a replay attached automatically. Click into any issue and watch exactly what the user did in the ~10 seconds before things broke.
Built for privacy
Passwords and any element marked data-sensitive are masked by default. Need stricter control? Drop class="rr-mask" on any element to blank its text, or rr-block to hide it entirely. No SDK configuration needed.
Stop guessing. Watch it happen.
Session replay is included on every plan, on Cloud and self-hosted.
Questions about session replay
What is session replay?
Session replay records DOM changes in the browser. When an error occurs, Traceway captures approximately 10 seconds of user activity leading up to the exception: clicks, scrolls, form interactions, and page navigations. The replay is attached to the exception automatically, so you can see exactly what the user did without asking them to reproduce the issue.
How does session replay work?
Traceway records DOM changes in the browser (not screenshots). When an exception occurs, approximately 10 seconds of user activity is captured and attached to the error automatically. The trace ID is propagated to the backend, so the replay links directly to the server-side error.
Does session replay affect performance?
The recording adds minimal overhead. It runs a circular DOM buffer in the background and only the last ~10 seconds are retained. Data is sent only when an exception triggers capture, so there's no continuous upload.
What about user privacy?
Sensitive inputs are masked by default. Password fields, any data-sensitive element, and anything with aria-masked is never captured.
For element-level control, Traceway honors rrweb's standard class hooks: class="rr-mask" blocks all text inside the element (including children), class="rr-block" hides the element entirely behind a neutral placeholder, and class="rr-ignore" records input interactions without capturing the typed characters. No SDK configuration needed, just drop the class on the element.