Heatmap utilizes advanced, asynchronous client-side tracking to collect user and revenue behavior on your website. This explains the core mechanisms behind our tracking methods, architecture and how we turn raw data into actionable insights.
Client-Side Tracking Basics
Heatmap's tracking operates entirely on the client side, meaning all data is captured directly from the user's browser. This approach is lightweight, flexible, and efficient, allowing for seamless integration into your website. Plus, it takes less than 5 minutes!
The key benefits of our tracking approach include:
Real-Time Data Collection: Data is captured and processed as users interact with your site, enabling up-to-the-minute insights.
No Website Performance Impact: Our asynchronous tracking snippets load in the background, ensuring no page rendering delay. Read this case study here, where we tested over $2m in a test with/without the heatmap snippet and proved zero difference in revenue performance!
Detailed Interaction Recording: Every user action - clicks, scrolls, hovers, or views - is tracked with precision, giving you a complete picture of how users engage with your site.
This method allows for granular data collection without relying on heavy server-side infrastructure, making Heatmap.com a versatile solution for e-commerce websites.
Data Collection Process
Heatmap.com can attribute revenue to each element on your website by assigning an anonymous User ID to every user that visits your website. The Header Snippet collects the behavior and interactions, and the Revenue Snippet ties these interactions to know if users purchased, how much, when, or if they did not purchase at all.
Heatmap.com does not collect personally identifiable information (PII), so it remains 100% compliant in any region worldwide. As it operates on anonymous User IDs, we can track behavior, revenue, and any metric related to a website interaction.
How Revenue is Tied to Elements
Because Heatmap.com’s User ID follows the visitor throughout the session, it knows where the user clicked, scrolled, or viewed and ties it to the revenue associated with that session.
The amount of revenue driven by an individual element is calculated using an aggregate model. The aggregate model combines the data from all users who clicked on an element and calculates them together.
The aggregate model does not give different “weights” or “contributions” based on different elements, as every element should be treated the same. This also means that revenue is attributed regardless of when in their sessions they interacted with specific elements in their session.
This also enables you to make cohorts (called Filters in-platform) per element, ranging from new vs returning users, traffic sources, purchasers vs non-purchasers, and an infinite number of custom filters you can build.
Read this article to learn more about each Calculated Metric per element inside heatmaps and recordings.
Need Help?
If you have questions or run into any issues while using Heatmap, our support team is here to help. Contact us anytime at Support@heatmap.com.