Why LiveRamp's Stats Might Differ From Your Destination's Stats
The way LiveRamp calculates matched reach stats and identifiers delivered stats might differ from how your destination platform calculates the same stats, and Safe Haven might show higher or lower device counts for a given segment.
Here are a few reasons why matched reach counts might differ between Safe Haven and some platforms:
Time window differences: Different platforms use different time windows to report the number of devices they see on their network. Some only count the number of devices they've seen in the past 30 days; others use a longer range.
Filtering mechanisms: Some platforms filter out any browsers that refuse third-party cookies from their counts. Another common filter is for a platform not to count devices they've only seen once on their network. These sorts of filtering mechanisms can affect reach statistics.
In general, LiveRamp tries to deliver the maximum number of devices that we have in sync with a destination, using a 90-day lookback period unless explicitly requested by the partner to change this window. As of the most recent update to this article, here is a list of partners who have asked us to change our delivery window:
Exelate (30-day lookback)
As of the most recent update to this article, here is a list of partners whose methodologies are known to report fewer cookies than Safe Haven:
Lotame
BlueKai
Contact your destination partner representative for more specific information on a particular destination.
Note
If you still have questions about a match rate that seems unexpectedly low or high at the destination platform, first check with the platform to see if it's an issue on their end. If nothing is found, or if the issue is solely with stats within Connect, use either the Activation: High/Low Match Rate Investigation quick case or the Measurement Enablement: High/Low Match Rate Investigation quick case to create a support case to investigate the issue.