Session replays

Session replays play a visit back the way the visitor saw it, beside a log of what they did: the pages they opened, what they clicked, how far they scrolled, which fields they used, and any goal reached or error raised on the way.

Open it from Analytics → Sessions, which opens on Session replays. The other two pages of Sessions are Heatmaps and Peak times.

Turn on recording

Recording is off until you add data-record to the snippet's <script> tag:

<script defer src="https://api.snowanalytics.app/sa.js" data-site="YOUR_SITE_ID" data-record></script>

Bare, it records every session. Give it a percentage to record a share, for example data-record="25" for about one visit in four. Each visit is decided once, when it starts, and the choice holds until the tab closes.

Pages without the attribute behave exactly as before and never fetch the recorder. With it, the tracker loads a second script, sa-replay.js, from the same address as sa.js, only for the visits it records.

A visit stops recording after 60 minutes or 5 MB. A tab hidden for more than 30 minutes pauses and picks up when it is shown again. Recordings are kept for at least 30 days, and longer while your workspace's storage has room. One with a tag is kept until its last tag is removed.

What is recorded

The recorder keeps what the page looked like and what the visitor did to it. It does not record:

  • What people type. Every input is masked, and password fields are never recorded.
  • Personal details in the page's text. Email addresses, card numbers, phone numbers and IBANs are starred out wherever they appear, in the page's text and in readable attributes such as title and alt, before anything leaves the browser. mailto: links lose their address.
  • Text and elements you mark. Put data-snow-mask on an element to replace its text with asterisks, and data-snow-block to leave it, and everything inside it, out of the recording. Markers you already use for another tool count too: data-sentry-mask, .sentry-mask, data-private, .fs-mask, .ph-mask and data-hj-suppress mask; data-sentry-block, .sentry-block, .ph-no-capture, .fs-exclude and data-hj-suppress block.
  • Query strings. They are stripped from the page's address and from links before anything is sent.
  • Canvas, fonts, and content from other sites' frames.

Do not rely on masking alone for anything a page shows that you would not want to see yourself: mark it with data-snow-block.

Visitors who send a Do Not Track or Global Privacy Control signal, or who have opted out with sa.optout(), are not recorded. Bots and traffic you exclude in Site settings are dropped too. See Cookieless & privacy for what recordings mean for your privacy notice.

The screen

  • Sessions lists the recordings of the period, newest first. Search visitor or page narrows it. Click a row to watch it; tick rows to select several. The panel collapses to give the player more room.
  • The player shows the page in a browser frame. Play and pause, drag the timeline or click a page name to jump, switch Skip idle to jump over quiet stretches, and change the speed. A quiet stretch is 5 seconds or more with no mouse movement, scrolling, typing or page load, the end of the recording included. The jump keeps a second at each side. Red marks on the timeline are rage clicks and errors.
  • Tag, in the player's header, pins a recording to the top of the list under a title you write, such as "Card declined at checkout", so a problem you found stays easy to find. Titles the site has used before are suggested as you type, and a recording takes up to five tags. Tagged recordings stay at the top whatever the date range, search finds them by title, and they are kept past 30 days until their last tag is removed. Members can add and remove tags; viewers can see them.
  • Activity lists the visit by page. The line for the moment on screen is lit, and clicking a line jumps to it.
  • Click the visitor's name to open their profile.
  • Ask Snowy opens Snowy about the recording you're watching. A question typed in the list's search field goes to Snowy too, about the recordings listed.

The page follows the date range and filters in the page header. Export saves the list as a CSV, with each recording's tags. A period with no recordings says No recordings in this period: visits are recorded as they happen, so try a longer period.

Before the first recording

Until a recording arrives, the page is the setup page. Turn on session replays shows your snippet with data-record added, with Copy snippet and Hand off to AI. The first recording shows up within seconds of a visit. To record only some visits, give the attribute a percentage: data-record="25".

Recording through a proxy

If you proxy the script from your own domain, the recorder needs two more routes next to the ones you have:

https://yourdomain.com/sa/sa-replay.js  →  https://api.snowanalytics.app/sa-replay.js
https://yourdomain.com/sa/api/frost     →  https://api.snowanalytics.app/api/frost

The recording is posted to frost beside whatever URL data-api-url names for events, so /sa/api/flake pairs with /sa/api/frost. Site settings → Installation → Ad-blocker proof generates all of these paths for you. See Bypass ad-blockers.

On this page