FAQ: What do the numbers at the bottom of Dynamic Heatmaps and Form Analytics mean?

When looking at a Dynamic Heatmap or Form Analytics report, you’ll see numbers at the bottom of the page. This may look like:

  • 710 of 750 clicks from 193 of 208 recordings
  • 50 of 61 moves from 200 of 233 recordings
  • 30 of 32 scrolls from 542 recordings

So what do these numbers mean, and why isn’t it 100%?

Lucky Orange is one of the few heatmapping tools in today’s market to include exactly what data you’re seeing in your Dynamic Heatmap or Form Analytics report. Other tools show you general pageview data, but Lucky Orange shows you more. With Lucky Orange, you’re seeing how many sessions were recorded AND how many clicks (or taps), moves or scrolls (depending on the heatmap you’re using) were generated from those recordings.

So why isn’t it always showing 100% of data?

  1. You have your data segmented. By default, your heatmap or form analytic data will be filtered to show desktop traffic. If you change or add segments, this will automatically exclude any of the data that was captured. You will see a blue Segmented tag popup in the lower left corner of the page.
  2. You have bounce traffic. This is especially true for moves and clicks/tap heatmaps. If a visitor comes to your website but doesn’t engage, it will be counted as a session recording but won’t produce any viable clicks or moves.
  3. Your traffic navigated to other pages using elements above the fold. In this situation, scroll heatmaps will show fewer scrolls. Since we know that not all visitors may scroll down a page, it would be worth switching to click heatmaps to see where they’re clicking instead. For pages with clicks but no scrolls, it’s more likely they are navigating away from the page with the top navigation and/or using elements above the fold. 
  4. Your visitor’s browser malfunctioned (rare). In this situation, Lucky Orange receives the data but the browser didn’t pass it through correctly. As a result, we can show that the click, scroll or move was captured but won’t be able to attribute it properly by device breakdown or through any meta data.  As a result, the Dynamic Heatmap or Form Analytics data won’t match one-to-one.