Session recording is the practice of capturing every visitor's session on your store as a stream of compressed DOM events that can be played back in your dashboard. You watch a real visitor scroll, tap, hesitate, abandon — exactly as they experienced it. On Shopify specifically, a good session recording tool also lets you filter sessions by customer field, cart value, device, and UTM, and links each replay back to the actual order so support tickets become a one-click lookup instead of a screenshot scavenger hunt.
Heatmaps show you what. Session recordings show you why.
Most session recording tools give you a generic player and a flat list of sessions. Propel records the full session, summarizes it for you, and lets you slice the list by anything Shopify knows about your customers.
Replays captures every interaction as a stream of DOM events: clicks, taps, scrolls, mouse movement, viewport changes, page transitions. You scrub a session like a video, but it's a live DOM render, not a screen capture — text is selectable, the layout is pixel-perfect, and the whole thing is a fraction of a video file's size.
Rage-click and dead-click detection are baked in, and Propel's insight alerts proactively surface the day's biggest orders, biggest abandoned carts, and biggest abandoned checkouts — so you watch what matters first instead of scrubbing through hundreds of replays.
The honest reason most session recording tools fail is that nobody actually has time to watch the recordings. You install the app, accumulate 800 sessions in a week, watch four of them, then feel guilty for a month. Propel fixes this by writing a two-sentence narrative for every replay you open — what the visitor did, where they hesitated, whether they bought.
Skim a hundred summaries in fifteen minutes. Watch the ten that look interesting. Skip the ninety that read like "bounced after 4 seconds." This is the differentiator merchants notice fastest — it's the difference between session recording as a workflow and session recording as guilt.
"Show me every mobile session from a returning customer who reached checkout but didn't pay." That's a one-click filter in Propel; it's not a thing you can express in Hotjar at all. Filter by customer tag, total spent, order count, cart value, country, UTM source, device, browser, landing page, exit page, returning vs. new — and combine them.
Every replay also links back to the actual order in Shopify admin. Customer support emails saying their cart broke? Look them up by email, watch the session, ship the fix. The "in Shopify" advantage is small in any single moment and enormous over a year of these moments.
Hotjar, Lucky Orange, Microsoft Clarity, Smartlook, Mouseflow — they're all multi-platform tools. They work on Shopify the same way any JavaScript works on any page, but their filters don't know what a Shopify customer is. You can't segment sessions by order count, by total spent, or by customer tag. Their tracking scripts load through GTM or a hard-coded snippet, which is where the Lighthouse penalty comes from on a theme that's already fighting for speed.
Propel is built on Shopify primitives. The script ships as a theme app embed — Shopify injects it at the bottom of every page after the rest of your theme has loaded, async, with 0ms impact on Core Web Vitals. Customer fields, cart value, order tags, UTMs, and Shopify Markets all map cleanly into the session filter UI. Replays link back to actual Shopify orders in admin. We didn't port a generic session recording tool to Shopify; we built the tool we wished existed when we were running a Shopify store ourselves.
To be honest: if your store isn't on Shopify, this advantage doesn't matter and Microsoft Clarity is a great free option. We win when "in Shopify" is load-bearing.
Filter the session list to "reached checkout, didn't pay" and watch the next twenty replays back. The pattern usually shows up inside three sessions: a discount code that won't apply, a shipping zone with a confusing error, an Express Checkout button that flashes and disappears, a phone-number field that rejects the customer's format. You don't need a CRO consultant to read this signal — you need ten minutes and a session list.
A customer emails: "I tried to check out and nothing happened." The traditional reply is "can you send a screenshot?" The Propel reply is to look them up by email, find their session, watch the thirty seconds of frustration, and reply with a fix. Support tickets that used to take three back-and-forths take one. The customer feels heard, and you have the actual evidence — not a description of evidence.
New product launches, theme updates, and app installs are exactly when conversion regressions sneak in. Propel's product-page alerts flag significant drops in add-to-cart rates the day they happen, and insight alerts surface the day's biggest orders, biggest abandoned carts, and biggest abandoned checkouts so you can see, at a glance, whether high-value sessions are still completing. You go from "we found the bug a week later" to "we shipped the fix Friday afternoon, before the weekend traffic."
Honest comparisons — including the cases where the other tool is the right fit.
Install Propel Replays and watch your first session before lunch. Free up to 750 pageviews/mo. 7-day free trial on every paid plan.