Replay Atlas

Patterns we look for in every review

A shared vocabulary for session replay insight. Use it to brief your squad — or ask us to run a lab against these themes on your journeys.

Team mapping ideas during a product workshop
  1. Rage and dead clicks

    Repeated taps on non-interactive chrome, disabled buttons, or decorative elements. Often signals missing affordances or slow feedback after a successful click.

  2. Form hesitation loops

    Cursor wandering, field revisits, and abandon after validation. We note which label, helper, or error message sits nearest the stall.

  3. Scroll abandonment cliffs

    Users who reach a mid-page block then leave without hitting a primary action. Useful when funnels show a drop with no clear event cause.

  4. Device and orientation friction

    Layouts that work on desktop but trap thumbs on common phone widths — clipped CTAs, overlapping sticky bars, or keyboards covering submit.

  5. Latency theatre

    Spinners, blank states, or silent waits long enough that people refresh or leave. Replay timestamps make these visible when aggregate metrics only show bounce.

  6. Path confusion after success

    Sessions that complete a goal event then reverse into help pages or cancel flows — a sign the confirmation state failed to reassure.