Features

Session replay

On this page

Session replay records the visits that reach the pages you choose, by default /pricing and /checkout. Open a visitor's journey and press Watch to see how they scrolled, where they clicked and where they stopped, next to whether they paid. Recording is off until you turn it on, and it is part of the Growth plan.

What you see

WhereWhat
Visitor journeyA Watch button on each visit that has a recording. Customers rows open the same journey, so you can watch how a customer bought.
People listsA play button next to everyone who has a recording: Visitors, Journey, Customers, top customers, funnel and path people, error visitors and the live map. It opens their journey straight into the newest recording. Team members only.
PlayerThe visit's page loads in order (for example 1 /pricing 0:42, 2 /checkout 1:10); the next one plays when one ends. Play and pause (Space), speed 0.5× to 4×, and Skip idle.
MarkersAbove the scrubber: grey lines for page changes, dots for clicks, red dots for rage clicks (three or more clicks on the same element within 0.7 seconds) and, with JavaScript errors on, red triangles for errors. Click a marker to jump there.

There is no list of recordings and no heatmaps: recordings are found from the people in your reports.

Turn it on

  1. Open Settings → Tracking & install → Advanced → Session replay

    Admins and the owner can change it. On Starter the controls are locked; see Limits for the Growth allowance.

  2. Choose the pages

    Up to 10 paths. A visit starts recording on the first page whose path starts with one of them, the same rule as funnel page steps, and keeps recording for the rest of that visit (until 30 minutes without activity).

  3. Choose how many

    Every matching visit, Half, 1 in 4 or 1 in 10. The choice is per visit, so a sampled visit is recorded whole.

  4. Switch on Record visits that reach these pages

    Nothing changes on your site: the standard tracking script loads the recorder only for visits it records.

What is recorded

  • From the first matching page to the end of the visit. Earlier pages of the visit are not recorded.
  • The page's content and layout, scrolls, clicks, page changes and the viewport size.
  • Never: what people type (every field shows as ***), canvas drawings, cross-origin iframes such as Stripe or PayPal card fields, mouse-move trails, console messages or network requests.
  • Images, fonts and styles are not copied: the player loads them from your site when you watch.

Hide parts of a page

AddEffect
data-mr-maskOn an element: its text is recorded as ***, and so is the text inside it.
data-mr-blockOn an element: not recorded at all; the player shows a grey box of the same size.
data-mr-no-replayOn the <html> element: this page is never recorded. window.metricravenReplay = false before the script loads does the same.
Hide all textThe setting: all page text is recorded as ***, so prices and names don't show.

By default only visitors who accepted cookies are recorded: your banner calls window.analytics.setConsent(true) (see Consent). Recording starts on the next matching page after consent. If you turn Only record visitors who accepted cookies off, every matching visit is recorded; tell your visitors in your privacy notice and check that the law where they live allows it. Replay stores nothing in the browser: no cookie and no local storage.

Limits

LimitValue
PlanGrowth (including the free trial). Starter can't turn it on.
Recorded visits a monthYour plan's monthly events ÷ 100, between 1,000 and 50,000 (1,000 during the trial). Visits over it aren't recorded until the allowance resets.
Per visit2 MB compressed. Longer visits stop recording and say so in the player.
Per page load30 minutes.
Kept for30 days, then deleted.
RecorderAbout 26 KB compressed, loaded only for the visits being recorded.
BillingRecordings don't count toward your monthly events.

Privacy and deletion

  • All members of the website can watch recordings, like the journeys they belong to.
  • Share links, embedded dashboards, secret keys and the public demo never list or play recordings.
  • Erasing a person deletes their recordings; deleting the website deletes all of them.
  • Turning replay off stops new recordings; the ones already made stay until they expire after 30 days.
  • Recordings are stored compressed with our storage provider, not in the analytics database.

Troubleshooting

ProblemFix
No Watch buttonThe visit didn't reach one of your pages, sampling skipped it, the visitor hadn't accepted cookies, the monthly allowance was used up, or the page has data-mr-no-replay. Check the Session replay row in Settings. Visits recorded before you turned it on don't exist.
Styles or images missingThe player loads them from your site. Files behind a login, or blocked from other origins by your server's CORS rules, can't load.
Self-hosted proxyThe recorder loads from /js/addons/replay.js next to the script. Forward that path too, or set data-addons on the script tag (see Optional attributes). Without either it loads from metricraven.com; the managed proxy serves it already.
Content Security PolicyThe recorder comes from the same host as the script and sends to the same endpoint, so the usual directives cover it.
Nothing recorded in old browsersThe recorder needs CompressionStream (all current browsers have it); older ones are skipped.
A recording shows your page as the visitor saw it, so check that recorded pages don't display card numbers, health data or other sensitive details outside form fields, or hide them with data-mr-mask.