Chartbeat concurrents versus active users in Google Analytics Real-Time

For teams that are familiar with using Google Analytics Real-Time prior to gaining access to our Real-Time Dashboard, we frequently receive questions about discrepancies between visitor counts between the tools, specifically between Chartbeat's Real-Time Concurrents metric and Google Analytics Real-Time's Active User count. Both of these metrics aim to deliver users with a sense for the total number of current visitors to their site, but differences in our measurement methodologies can cause significant discrepancies between these real-time tracking systems. To better understand these differences, let's begin with the basic metric definitions.

Chartbeat Concurrents: The total number of people on your site at any given moment, as measured by the number of open browsing sessions to your site. Note that this number includes both engaged and non-engaged browsing sessions open to your site. An engaged session in Chartbeat represents an active user session where the visitor has directly engaged (clicking, scrolling, typing, mousing) with your page in the last 15 seconds. A non-engaged session represents an open browser tab to your site where the visitor has not shown any signs of engagement within the last 15 seconds. If an open browser session to your site shows no signs of engagement for two continuous hours, we will stop tracking the session as a concurrent at that point.

Google Analytics Real-Time Active Users: Google Analytics defines Real-Time active users as follows: a unique user who has triggered an event or pageview within the past 5 minutesIf a user has multiple pages open to your site in the same browser, these sessions will be counted as a single active user in Google Analytics Real-Time.

The key difference to understand most discrepancies between these systems boils down to these differences in real-time metric methodologies. Chartbeat tracking code checks in with each open session to your site, effectively asking each person on your site "where are you and what are you doing now?". This enables us to give a uniquely accurate assessment of how many active visits are occurring at any one moment in time as we know precisely when a given page session ends, whereas Google tracking does not capture this.

Google Analytics (GA) works differently. It simply receives data every time a page is loaded or a custom tracking event is triggered. From these pageview events, until the next page load on your site, Google is blind to what these visitors are doing on your site. This means they can have difficulty assessing what a user does after they reach a page, or if they are even still there at all.

In Google Analytics Real-Time, if a visitor leaves your site before 5 minutes by closing their current browser tab or returning to their previous referring website, Google will continue counting this visitor as an active user for the full five minutes. If a visitor stays on your site for longer than 5 minutes, they will vanish from Google's Real-Time user count, even if the visitor is still on your site.


What does this mean?

If Google's active users are greater than Chartbeat's concurrents:

This is probably because Google Analytics Real-Time is counting active users who are no longer on your site. If you have content that is only holding people for a short period of time, we'll remove these visitors from your total concurrent count immediately after they leave the page by closing their browser tab to your site or returning to their previous referring website like Google Search or Facebook. GA Real-Time always assumes these visitors are sticking for around 5 minutes. If 100 people visit a page but only 20 stay, Chartbeat will only show those 20 open browser sessions whereas Google Real-Time will show you 100. This can cause very significant discrepancies, especially for sites with high mobile and less desktop traffic, as mobile visitors less frequently leave open browser tabs to your site that Chartbeat would continue to count as non-engaged concurrents on desktop. 

If Google's active users are smaller than Chartbeat's concurrents:

This is less common, but if you experience this discrepancy, it's likely due to GA Real-Time dropping off visitor sessions after 5 minutes where in reality, some or all of these visitors are still on your site. Our tracking script allows us to continue tracking desktop sessions open to your site for visitors who continue to engage after GA's 5 minute limitation. If 100 people visit a page on your site with video and continue engaging past the 5 minute mark, they will vanish from Google's report after 5 minutes; Chartbeat will continue tracking these 100 sessions. The resulting discrepancy is more common for sites with large amounts of desktop traffic as these page sessions tend to last longer than mobile sessions.


Measure different. Know more.

At its core, the numbers can be different because what we are tracking is different. We believe the power of real-time data is that it allows you to understand what people are doing on your site, not just that they were there recently. Chartbeat is about people and their actions; today that's knowing why a page is working, tomorrow it's making it happen again.


NOTE: While it's more common that the differences in metrics between these systems as described above is responsible for publisher discrepancies, it's also possible that misaligned tracking implementations between these systems contributes to or is largely responsible for a discrepancy experienced by your team. Check to ensure that both systems are measuring the same platforms, and if not, consider adjusting your tracking strategy to ensure alignment across systems. The team(s) responsible for implementing Google Analytics and Chartbeat tracking at your organization are best suited to review these implementations and make changes if needed to bring the systems into alignment.

Chartbeat has distinct integrations available for standard websites (including webview-based apps), single page web apps, AMP pages, Facebook's Instant Articles, native app tracking for Android and iOS apps, and other sources of reader engagement which may not be tracked by other analytics systems (GA, Adobe).




Here are some ways to get in touch.