Skip to main content

View Matched Reach Stats

Matched reach stats provide information on the number of records and devices that have been matched at a distribution destination for your distributed fields and segments. These stats typically take 4-7 days to populate after the field or segment has been added to distribution.

Matched reach stats allow you to gauge the effectiveness of your ad campaigns by confirming how many users included in your campaign files could be targeted successfully at an advertising platform via specific device types.

There are two place in Connect where you can view matched reach stats for your actively distributing segments:

  • The Segments Distribution page displays the number of cookies, Apple devices, Android devices, and custom IDs (if applicable)  that have been matched at that destination.

  • You can view stats on record matches and device matches ("destination matches") for actively distributing fields and segments (including derived segments) on the Audience Segments page.

Note

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 Connect might show higher or lower device counts for a given segment.

Here are a few reasons why matched reach counts might differ between Connect 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.

Unit of measurement: We report devices synced to your destination via the Connect dashboard, but not all platforms use this metric.

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 Connect:

  • 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 Onboarding: High/Low Match Rate Investigation quick case or the Measurement: High/Low Match Rate Investigation quick case to create a support case to investigate the issue.

Destinations that Do Not Support Matched Reach Stats

Matched reach stats for the destinations listed below are not supported, as they might not accurately reflect the total cross-device reach your audience has on those destinations' platforms:

  • Datalogix

  • Facebook

  • Roku

  • Pandora

  • Spotify

  • Google Customer Match (Data Append)

  • Hulu

  • Charter TV

  • Roku

  • Dish

  • Sling

  • Altice

  • DirectTV

  • Comcast

  • Verizon

  • Cox

  • Discovery

To get matched reach stats for one of these destinations, contact your account representative at that destination.

View Matched Reach Stats on the Segment Distribution Page

The Segments Distribution page displays the number of cookies, Apple devices, Android devices, and custom IDs (if applicable)  that have been matched at that destination.

  • From the Connect navigation menu, click Destination Accounts to navigate to the Destination Accounts page and then click MANAGE on the desired destination account tile to navigate to the Segment Distribution page for that destination account.

    C-Global_Nav_Announcement-All_Destinations_menu_selection.png
    DA tile manage button.jpg

    Note

    By default, the list of destination accounts is initially filtered to show only active destination accounts. To access a destination account that is not active, adjust the filter setting.

    C-Changing_Active_Filter_on_DA_page.png

You can see the number of cookies, Apple devices, and Android devices that have been matched at that destination for all of your actively distributing segments.

C_Onboarding-View_Segment_Delivery_Stats-identifier_counts-EY0.jpg

Note

You may see an hourglass if stats have not yet been generated for this distribution. These stats may take up to 4-7 days to generate. Your segments are still distributing and will show up at the destination platform even if the stats haven't appeared yet.

View Matched Reach Stats on the Audience Segments Page

You can view stats on record matches and device matches ("destination matches") for actively distributing fields and segments (including derived segments) on the Audience Segments page.

Note

For fields and derived segments, you can also view platform-specific estimated device reach. See "View Estimated Reach Stats on the Audience Segments Page" for more information.

  1. From the Connect navigation menu, hover over Audiences and then select the desired audience to navigate to the Audience Segments page for that audience.

    C-audience_menu_selection.jpg
  2. Select a destination from the list of available destinations in the Destinations panel:

    C_Onboarding-View_Segment_Delivery_Stats-select_destination-lB4.jpg

    Two additional columns appear in the table with stats broken down by match type:

    C_Onboarding-View_Segment_Delivery_Stats-matches_columns-djw.jpg
    • Record Matches: The number of records in the segment that were matched to one or more devices at the destination (depending on the match type selected).

    • Destination Matches: The expected number of matched identifiers (mobile device IDs, cookies, or custom IDs, depending on the match type selected) at the destination.

  3. If you are sending multiple device types to a destination, you can toggle between devices by changing the match types in the Match Types panel.

    C_Onboarding-View_Segment_Delivery_Stats-select_match_type-HwI.jpg

    Note

    The "Mobile" selection is an aggregate of delivered Apple and Android in-app mobile device IDs.