Replays
Understand how Replays helps users watch real sessions, inspect friction, and validate what shoppers actually experienced.
The Replays page helps users inspect real storefront visits one session at a time.
Instead of relying only on summaries or charts, this page helps users review what an individual shopper actually did before dropping off, getting frustrated, abandoning the cart, or converting.
What It Does
Replays gives users a session-level investigation layer for DynoWeb.
It is best for answering practical questions like why shoppers hesitate on a product page, where mobile visitors get stuck, whether a CTA is being missed, or what happened right before a form abandonment or exit.
This page works especially well after Heatmaps, Journeys, Cart Overview, or Conversions point to a suspicious page, path, or interaction.
Users should think of the session list as the triage layer: find the visits most worth opening first, then move into the detailed replay view for closer inspection.
What To Look For
When watching a replay, users should focus on hesitation, repeated taps, dead clicks, abrupt exits, long pauses before important actions, and back-and-forth behavior that suggests confusion.
Those patterns usually explain the "why" behind weak scroll depth, cart drop-off, low CTA performance, or incomplete checkout progression.
It is also useful to compare frustrated sessions with successful sessions on the same page so users can separate normal browsing from real friction.
How To Use It Best
The best way to use this page is to start with a known problem instead of watching random sessions.
A weak CTA from Conversions, a suspicious path from Journeys, a product with strong cart intent but weak downstream progress from Cart Overview, or a friction hotspot from Heatmaps are all strong starting points.
From there, users should open a few representative sessions, look for repeated behavior patterns, and only then decide whether the issue is content clarity, layout friction, mobile UX, pricing hesitation, or something else.
This page also works well alongside Suggestions because Matching Replays can help users validate whether a recommendation reflects a real shopper problem.
Privacy Note
Session Replay is optional, replay inputs are masked by default, and merchants can limit capture to frustrated sessions only.
Good Help-Guide Positioning
"Replays lets users watch real storefront sessions, helping them understand why visitors hesitate, get frustrated, abandon the cart, or fail to convert."