When I look at the same (or similar) metrics in Uberflip Analytics and legacy Metrics or the Hub dashboards, the numbers are different. Why?
The short answer is that these metrics are being collected not just differently, but in a way that is a lot more accurate.
Metrics are based on recording when and how events happen, for example page views. This done by an event collection system, which is responsible for recording and measuring these events, and generating data from them, i.e. metrics.
For Uberflip Analytics, we completely rebuilt our event collection system from the ground up. As a result, we're now able to test and audit all metrics, which means we can be confident that the numbers shown in Uberflip Analytics are accurate to a much greater degree than what was presented in legacy Metrics.
On top of this, there are also specific cases where the numbers are different by design. These include:
- Changes to how certain metrics are calculated: For example, legacy Metrics counted Embedded CTAs, while Uberflip Analytics does not.
- Changes to how date ranges work: When you select a date range in legacy Metrics, the period includes the end date, but in Uberflip Analytics it does not. For example, a date range of January 15 to February 15 would not include February 15 itself in Uberflip Analytics, but this date would be included in legacy Metrics.
- Availability of data: Some metrics in Uberflip Analytics only started to be collected after a certain date, so data from earlier than that date is not available. See this article for information about when data collection started for different metrics.