It's common to notice that the session counts in your heatmap.com data are lower than those reported by your site analytics tools like Google Analytics. While this can be concerning, it's often due to differences in data collection and processing methods rather than an error. Let's explore why this happens and what it means for your analytics.
Common Reasons for Discrepancies
Different Definitions of Sessions
Sampling and Data Processing
Tracking Code Implementation
Filters and Segmentation
Bot Traffic Handling
Page-Specific vs. Site-Wide Tracking
Understanding the Differences
1. Different Definitions of Sessions
Site Analytics: Tools like Google Analytics often define a session as a group of user interactions within a given time frame, typically 30 minutes.
Heatmap.com: May use a different definition for sessions, focusing on specific page interactions or using a different time frame.
2. Sampling and Data Processing
Site Analytics: Large websites often use data sampling to estimate total traffic, which can lead to inflated numbers.
Heatmap.com: Typically processes all collected data without sampling, providing more accurate but potentially lower numbers.
3. Tracking Code Implementation
The placement and loading priority of tracking codes can affect data collection.
If the heatmap.com code loads after other analytics scripts, it might miss some quick bounces or rapid page changes.
4. Filters and Segmentation
Heatmap.com: Offers advanced filtering options. Ensure you're not applying filters that exclude certain traffic.
Site Analytics: May have different default filters or segmentation options.
5. Bot Traffic Handling
Site Analytics: Some tools may count bot traffic, inflating session numbers.
Heatmap.com: Uses advanced techniques to filter out bot traffic, resulting in lower but more accurate human visitor counts.
6. Page-Specific vs. Site-Wide Tracking
Heatmap.com: Often focuses on specific pages or sections of your site.
Site Analytics: Usually provides site-wide data by default.
How to Address Discrepancies
Check Tracking Code Installation
Verify that the heatmap.com tracking code is correctly installed on all pages.
Ensure it's placed high in the
<head>section of your HTML for optimal data capture.
Review Filters and Segments
Compare the filters and segments applied in both your site analytics and heatmap.com.
Adjust as needed to ensure you're comparing similar data sets.
Understand Data Collection Periods
Ensure you're comparing data from the same time periods in both tools.
Remember that heatmap.com may require a minimum number of sessions (typically 50) before displaying data.
Consider Traffic Sources
Some analytics tools might count internal traffic differently.
Check if you've excluded any traffic sources in either tool.
Examine Bot Filtering Settings
Review bot filtering settings in your site analytics if available.
Understand that heatmap.com's stricter bot filtering may lead to lower, but more accurate, human traffic counts.
Use Custom Tracking When Necessary
For single-page applications or sites with dynamic content, you may need to implement custom tracking events.
Consult heatmap.com's documentation or support for guidance on tracking complex site structures.
When to Be Concerned
While some discrepancy is normal, significant differences (e.g., more than 20-30%) might indicate an issue. If you notice a large gap between your heatmap.com data and site analytics:
Double-check all implementation steps mentioned above.
Compare trends rather than absolute numbers. Do both tools show similar patterns of increase or decrease in traffic?
If the discrepancy is substantial and unexplained, contact heatmap.com support for further investigation.
Conclusion
Remember, the goal of using multiple analytics tools is to gain comprehensive insights rather than to have perfectly matching numbers. Heatmap.com provides unique, actionable data on user behavior and revenue attribution that complements your general site analytics. Focus on the trends and insights each tool provides to make informed decisions about your website's performance and user experience.
If you have any further questions or concerns about data discrepancies, don't hesitate to reach out to our support team. We're here to help you get the most accurate and valuable insights from your heatmap.com data.