ERROR-SESSION REPLAY
See the page as it broke.
Only when something breaks.
Most sessions never need a recording. Dozenfold keeps the last minute in the shopper’s browser and uploads it only when an error happens, masked, next to the issue it explains.
The minute before, the moment it failed.
A masked reconstruction, opened 10 seconds before the error, with the session’s steps beside it.
DF-1842 · RECOMMENDED OCCURRENCE · MOBILE SAFARI
Masked replay, opened 10 seconds before the error.
- Recording bufferLast minute kept in the browser
- Delivery option changedCaptured storefront action
- Cart update failedPOST /cart/update · upload starts
- Shopper idle 5 minRecording ends · buffering resumes
Record only what you will watch.
Turn replay on in Settings and choose a sample rate. The recorder keeps a rolling minute in the browser; sessions without an error upload nothing. When an error happens it uploads that minute and records the rest of the session until the shopper is idle, for up to 30 minutes. A later error starts a new recording.
Start from an issueOpen it where the question is.
An issue’s recommended occurrence is one with a replay, and playback starts 10 seconds before the error with the error marked. Sessions carry a Replay badge and a “Has a replay” filter, and a session names the issues its replay recorded. Each browser tab records separately.
Follow the sessionKnow why one is missing.
When an occurrence has no replay, the issue says why: replay was off, the session was outside the sample, the visitor did not allow analytics, the recording had ended or did not reach us, or it was older than 30 days. Settings shows seven days of replay reach, so you can see what limits coverage.
Take it to your developerA LITTLE MORE DETAIL
Good questions.
Useful answers.
What is masked?
Form fields are always masked. The default, “Mask all text and inputs”, also hides page text so replays show layout and interactions only. “Mask inputs only” keeps product names and prices visible.
Does replay slow the store down?
It loads as a separate script only when replay is on, the session is sampled and analytics is allowed. It stops recording on a flood of DOM changes or a collector rate limit instead of slowing the page, and shares a capped page-exit request budget with the core script.
How long are replays kept?
Thirty days, stored privately and deleted with the store’s data.
How is this different from Hotjar or LogRocket?
They record every session and leave you to find the broken one. Dozenfold records only sessions with an error and opens each replay from the issue it explains, with the journey, environment and revenue impact beside it.
CONNECTED PRODUCT WORKFLOWS
Follow the next connection.
An issue, a journey, a page or a release. Each view gives you a way into the next.SEE IT ON YOUR STORE
Bring a real problem to the demo.
Bring the journey you want to improve and the person who ships your changes. We’ll look at your first evidence together.
Book a demo Estimate your price and contact us · Guided setup