On this page
Use analytics to count visits and find the page or step that loses people, a heatmap to see where people click and how far they scroll on one page, and session replay to watch what happened in a single visit. Most questions need two of them in turn: analytics to find where people drop off, then replays of that page to see what visitors do there.
The three tools don't answer the same questions. Pick the wrong one and you'll stare at a chart that can't tell you what you need, or watch forty replays to learn a number one report would have shown you in a second.
Key takeaways
- Start from your question: analytics for how many and where, a heatmap for where on one page, a replay for what happened in one visit.
- Use analytics to find the page or step that loses people, then watch replays of that page.
- No heatmap tool? Tally clicks, scroll depth and exits across ten replays of one page; you keep the order of events a heatmap throws away.
- Check how often a problem happens in your analytics before you redesign around one memorable replay.
Start from the question
| Your question | Open this first | Why |
|---|---|---|
| How many people came, and from where? | Analytics | It counts visits and splits them by source, device and page |
| Which page or step loses the most people? | Analytics | Exit rates and funnels show the drop as one number |
| Where on this page do people click, and how far do they scroll? | A heatmap | It combines many visits to one page into one picture |
| Why do people leave this page? | Replays of visits to it | You see what they tried before they left |
| A customer says something is broken | Replays | You need that exact visit, not a total |
| Did my change work? | Analytics, then a few replays | The number says whether it moved; replays say whether it moved for the reason you think |
| What's happening during a launch, right now? | A live replay | You can watch visits live, a few seconds behind |
The loop that works for small sites uses two of the three, one after the other.
- Spot. Analytics shows where people drop off.
- See. Replays show what they do there.
- Change. Fix one thing based on what you saw.
- Measure. Analytics shows whether the number moved.
The loop works with or without heatmaps. Replays do the seeing and analytics do the counting.
What's the difference between analytics, heatmaps and session replay?
Analytics give you totals and trends across your site, a heatmap gives you one picture of where attention lands on a single page, and a session replay gives you one visit in the order it happened.
Analytics count
Analytics add up visits: how many people came, where from, which pages they saw and how many bought or got in touch, as trends over days and months. They're the fastest way to spot a change, like a sudden drop in sales from one traffic source, and to find the page or step where people leave.
Their limit is that everything is a total. A number can tell you that people leave your shipping page. It can't tell you what they were doing when they left. On Shopify that means its own reports and on a Wix site Wix Analytics, with Google Analytics 4 on either if you've connected it; Wix Analytics vs Google Analytics compares what each one shows.
Heatmaps sum up one page
A heatmap gathers clicks, taps or scrolling from many visits to a single page and paints them as colors, warm where attention landed and cool where it didn't. It shows which parts of a page draw clicks, which links get ignored and how far down people tend to scroll.
A heatmap has no order, though. It can't show what someone did before or after a click, or how they moved between pages, and pages that change as you use them, with pop-ups, opening menus or rotating banners, produce confusing maps. A page also needs steady traffic before the colors settle.
Replays show one visit
A session replay rebuilds one visit from the page's own structure and events, so you can watch the pages, clicks, scrolling and taps in the order they happened. How session recording works explains the rebuild.
Replays are the only one of the three that shows the story behind a number: where a visitor hesitated, what they tried first and what broke. The cost is time. Each replay is one person, and one memorable visit can feel more typical than it is.
Session recordings, private by default
What visitors type into form fields is masked in their browser before it's sent, and recording follows your cookie consent. Free forever.

Heatmap-style answers from ten replays
You can answer the main heatmap questions by hand, with one advantage: you keep the order of events. Ten visits to one page fit in a short sitting with idle time skipped.
- Pick one page with a job to do, such as your best-selling product page.
- In Session Recordings, open visits from All visits and keep ten that reach that page. A visit that landed there starts with a Page view row for its address, such as /product-page/linen-apron; for the rest, play at 4x until the page comes on screen.
- Copy the column headings from the table below into a spreadsheet, one row per visit.
- Start each replay where that page comes on screen and watch until the visitor leaves the page.
- Fill in the row, then move to the next visit.
Phone visits play back in the phone's shape, so the Device column takes a glance. Here is a filled-in example for a made-up apron shop.
| Visit | Device | Tapped photos | Picked a size | Opened size guide | Reached reviews | Added to cart | Went next |
|---|---|---|---|---|---|---|---|
| 1 | Phone | Yes | Yes | No | No | Yes | /cart-page |
| 2 | Phone | Yes | No | No | No | No | /shipping-policy |
| 3 | Computer | Yes | Yes | Yes | Yes | Yes | /cart-page |
| 4 | Phone | Yes | Yes | No | No | No | /shipping-policy |
| 5 | Phone | No | No | No | No | No | Left the site |
| 6 | Computer | Yes | Yes | No | Yes | Yes | /cart-page |
| 7 | Phone | Yes | No | No | No | No | /shipping-policy |
| 8 | Phone | Yes | Yes | No | No | Yes | /cart-page |
| 9 | Computer | No | Yes | No | Yes | No | Left the site |
| 10 | Phone | Yes | No | No | No | No | Left the site |
How to read it
Count each column first, then look at who did what.
- Photos get used. 8 of 10 tapped them. Nothing to fix there.
- Reviews are out of reach on phones. 3 of 10 reached the reviews, and all three were on a computer. None of the 7 phone visits got that far. Move a rating summary up near the price.
- Delivery cost is a question the page doesn't answer. 3 of 10 went to the shipping policy, all on phones, and none of them added to cart. Put the delivery cost on the product page.
- The size picker gates the cart. All 4 visitors who added to cart had picked a size, and none of the 4 who never picked one added. All 4 non-pickers were on phones, so check that the size options are visible without scrolling on a small screen.
- The size guide is a lead, not a pattern. 1 of 10 opened it. Note it and watch for it next time.
A simple rule keeps ten visits honest: when 3 or more of 10 do the same unexpected thing, test a fix; when 1 or 2 do, note it and keep watching. Don't read anything into 6 of 10 against 7 of 10, which is noise at this size. Before you redesign, check your analytics to see whether the page's exits really lean toward phones.
Mistakes to avoid
- Treating one replay as a trend. A single visit is a story. Check how often the same thing happens before you redesign around it.
- Reading a heatmap across a redesign. If the page changed during the period, old and new layouts blend into one confusing map. Start a fresh map after each change.
- Chasing a number without looking. A drop can come from a broken button, a slow page or a change in traffic. A few replays tell you which.
- Expecting any of them to explain why. All three show behavior. For reasons in visitors' own words, ask a one-question survey or reply to your order emails.
If you can only start with one
Start with the analytics that came with your site, so you know where people come from and where they leave. Add replays when you need to see why a number looks the way it does. For a small site, heatmaps can wait: they need steady traffic to a page before the picture settles, and ten replays answer most of the same questions.

Frequently asked questions
What is the difference between a click map and a scroll map?
A click map shows where visitors click or tap on a page, with warm colors on the busiest spots. A scroll map shows how far down the page visitors get, with colors fading where fewer people reach. Both are kinds of heatmap that combine many visits into one picture of a single page, and neither shows the order of events in a visit.
Are session recordings qualitative or quantitative data?
Mostly qualitative. A recording shows how one visit unfolded: where the visitor hesitated, what they tried and what broke. Analytics give quantitative data such as counts, rates and trends. Heatmaps sit in between, turning many visits into a picture of one page. Use the numbers to decide where to look, and recordings to understand what you find there.
Can session recordings tell you why visitors leave?
Not on their own. A replay shows what a visitor did before leaving, such as opening the shipping policy or tapping a button that did nothing. The reason stays a guess until other visits show the same thing or a visitor tells you. Pair replays with a one-question survey or a reply to your order email to hear reasons in visitors' own words.
Try it on your site
Session Recordings replays individual visits with idle time skipped and every click listed in order, which is all the ten-visit tally needs. See session replay for Shopify and Wix.



