Reference: Differences Between Uberflip Analytics and Legacy Metrics

Follow

A reference guide to the data points that appear in both Uberflip Analytics and Legacy Metrics, and how they differ.


Info

Uberflip Analytics is in ongoing development, and data points may be added or changed at any time. This article is intended to be a living document that will be updated and added to as the Uberflip Analytics product evolves.

 

Usage

Uberflip Analytics (UFA) and Legacy Metrics use a number of "shared" data points, in the sense that these data points have the same name in both systems, and represent the same type of metric. However, if you compare these data points between the two systems, you will usually find that the numbers don't match. The reason for this is that UFA and Legacy Metrics each have their own, separate methods for measuring or calculating data points — including those that have the same name in both systems.

This guide outlines these "shared" data points that appear in both systems, and describes how each one is measured or calculated.

 

Common Data Points: Known Differences

The table below lists data points that appear in both Uberflip Analytics and Legacy Metrics under the same name, whether you can expect differences when comparing these data points across the two systems, and if so, the reason why:

Name Description  Differences Reason
CTA Impressions The number of times CTAs were seen by visitors Yes Different measurement method (see below for details)
CTA Submissions The number of times Form CTAs were completed and submitted No Same measurement method in both systems
Embedded CTAs Metrics related to CTAs that are embedded on non-Uberflip web properties Yes Captured in Legacy Metrics, but not in Uberflip Analytics
Time on Page The amount of time Yes

Different measurement method (see below for details)

Includes Flipbooks in Legacy Metrics, but not in Uberflip Analytics

Note: Custom code and CTA event collection

Many Hubs use custom code to implement non-standard functionality or change the Hub's default appearance. In some cases, this code may impact the way CTA events are collected by Uberflip Analytics, which may also cause discrepancies between Uberflip Analytics and Legacy Metrics beyond those noted above.

 

Measurement Method Comparison

For data points where a discrepancy exists between UFA and Legacy Metrics due to different measurement methods, the table below describes the method used in each system:

Name Measurement Method: Legacy Metrics Measurement Method: UFA
CTA Impressions
  • Recorded on page load.
  • If a CTA was not visible in the viewport on page load, it is still recorded as an impression, even if the visitor never scrolled down to view the CTA.
  • Recorded only when a CTA is visible in the viewport.
  • When a CTA is placed within a Stream, impressions are counted each time additional iterations of the same CTA appear in a Stream (e.g. as a visitor scrolls down a Stream).
Time on Page
  • Only for Flipbook pages, not Hub content pages.
  • Calculated based on the time elapsed between when a page URL was loaded, and when the next page URL is loaded.
  • Recorded on page exit (i.e. when a Flipbook is flipped to the next page).
  • Average Time on Page uses the mean (not median) and excludes outliers (less than 1 second or more than 60 minutes).
  • Only for Hub content pages. Includes Item pages that contain Flipbooks, but not pages within a Flipbook itself.
  • Calculated based on time viewing a specific URL only while tab is in focus.
  • Recorded continuously in 2-second intervals (anything less than 2 seconds is disregarded).
  • Average Time on Page uses the mean (not median) but does not exclude outliers (except views under 2 seconds).

 

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.