There are a number of reasons why using the Live heatmap favors the static heatmaps. Static heatmaps are a great representation of the exact way the website or app looked at the time the user viewed it, especially if dramatic changes have occurred from the time the user experienced your app or website and now.

Here are a few reasons why you might want to use the Live Heatmap as opposed to the static heatmap:

When seeking insights into the performance of Dynamic elements

Because Live Heatmaps work as an overlay on your live website they offer complete support for dynamic elements (such as Single Page Applications (SPA), Lazy Load, Drop Down Menus, Revolutions Sliders, Parallax Scrolling, and other dynamic technologies). This means that using Live Heatmaps you can now view all the dynamic content that can't be displayed on traditional static heatmaps.

Investigating Dynamic Content such as product pages and pages with filter options

Changing the content on your live site (eg. by adding products to a cart or checkout page) will update the data you see in the heatmap to reflect the content on the page.

This makes Live Heatmaps fully customizable, allowing you to navigate through your site as if you were testing the functionality - but you'll have the data from hundreds, or even thousands, of users, follow you as you go.

You can place 100 items in your cart and see how the heatmap conforms to this - how far down the page does the average user scroll? Does the ‘Next’ button disappear below the fold? Or you can filter for a specific category of products on your product page and see exactly where users are clicking or where their attention is focussed.

Arguing for design change

Heatmaps as an argument become even more relevant when you can show stakeholders the heatmap data and insights - directly on your live site.

Did this answer your question?