Watch the session, not just the number
A bounce rate tells you people left. It never tells you they left because the submit button sat under a cookie banner on a 375px screen. Replay is how you find that out, and in Galytics it comes with the analytics rather than from a second vendor.
A video player for something that was never a video
A replay is not a screen recording. It is the DOM, rebuilt from a stream of mutations captured by rrweb, then played back in your browser. That means it stays sharp at any size, weighs a fraction of a video, and the page it reconstructs is the page that visitor actually saw, at their window size, with their content.
Mouse movement draws as a trail so you can follow attention rather than guess at it. Play at 1x when you are studying something and 8x when you are scanning, skip the gaps where nothing happened, scrub to a moment, or go full screen.
What visitors type never leaves their browser
Every form field is masked at the point of capture. Names, email addresses, phone numbers, card numbers, search boxes, textareas: the characters are replaced before the event is queued, so the values are not in the payload we receive and never reach our database. You see that a field was filled, how long it took and whether the visitor went back to it. You do not see what it said.
This matters more than it sounds. Session replay is the part of analytics most likely to turn into a data breach, because a recorder that captures keystrokes will happily record a customer typing their address into your checkout. Masking at capture is the only version of this that holds, since anything masked on the server has already been transmitted and stored.
Worth being precise: masking covers what a visitor types into form fields. The text of your own pages is recorded as written, because reconstructing the page is the entire point.
Recording everyone, not just the ones who said yes
Galytics sets no cookies, so replay does not sit behind a consent banner. Every session is recorded, including the visitors who would have declined.
That is not a small distinction. The usual replay tools need cookies to work at all, so their recordings only ever cover the share of your audience that clicked accept. People who refuse tracking are not a random sample of your users, which means the recordings you are studying are systematically not the sessions you most need to see. Compared with Hotjar, compared with Microsoft Clarity.
From a row in a table to the session behind it
Replays are not a separate silo you go browsing through. Open the sessions list, expand any session, and you get where they came from, their country, browser and device down one side, and every interaction in order down the other.
When a recording exists, the replay button is right there. So the path is: a number looked wrong, which sessions caused it, what did those people do. You end up watching the four sessions that matter rather than scrubbing through a hundred.
EU-hosted, and it is your data
Recordings are stored in the EU, on our own infrastructure, and they are not shared with anyone. We have no advertising business to feed them into, which is the honest reason we can say that and mean it.
Your data stays exportable, and clearing it is a button in settings rather than a support ticket.
What people actually use it for
Fixing the funnel
Everyone drops on step three. Ten minutes of replay usually shows you why, and it is rarely the reason anyone guessed in the meeting.
Reproducing bugs
A support ticket says "it didn't work". The replay shows the browser, the window size and the exact sequence, so you stop guessing at repro steps.
Settling arguments
Design disagreements end quickly when everyone watches five people fail to find the button.
Included on every plan
Session replay is not an upgrade tier. It is in the same script as the analytics, on every plan, from the smallest one. See pricing.
Start your 30-day trialNo credit card · Cancel anytime · Hosted in EU