Skip to main content

Google PAIR and ATS

You can set up your ATS for Web configuration to support Google PAIR integration for Display & Video 360. If enabled, ATS will return an identity envelope and a PAIR ID when a user authenticates on your website. The Google PAIR integration also works if you are obtaining phone numbers as identifiers.

Once integrated, you can access the match rate of your and the advertisers' audience in Console at any time.

Prerequisites

  • You must be running ATS for Web and not directly calling the ATS API.

  • You must have Google PAIR in your subscription by adding it from the Marketplace.

    Caution

    The Google PAIR integration is currently available in beta. Contact your LiveRamp representative to get this added to your subscription.

  • You must be running the header-bidding solution Prebid configured for ATS (the latest version is recommended). If you haven't, see the steps in Configure Prebid.js for ATS instead to learn how to do this with Google Pair.

This implementation doesn't require an additional ID from Google Display & Video 360. If you have completed the prerequisites above, you can proceed with the instructions below.

Enable Google PAIR Integration in Console

To start obtaining PAIR ID together with identity envelopes, you must first enable Google Pair integration for the ATS Configuration.

  1. Log in to Console.

  2. Go to ATS > Web and select a configuration of your choice.

  3. Select the "Integrations" tab.

  4. Click New.

  5. Select Google PAIR.

  6. Click Publish.

Include Google PAIR ID Module in Prebid

You can pass the PAIR IDs downstream to bidders by including the Google PAIR ID module in your Prebid configuration. If you haven't set up Prebid for ATS yet, refer to Configure Prebid.js for ATS documentation instead.

If you are already running Prebid and have included the RampID module in your Prebid configuration, follow the steps below.

  1. Go to Prebid's download page.

  2. Select the latest version of Prebid.js core or any version above 7.53.0.

  3. Include the ‘Google PAIR ID’ submodule under the User ID Module.

  4. Click Get Prebid.js.

  5. Update your call to pbjs.setConfig to pass the required information to the pairId user ID module. See the example below to learn how you can do this for cookie and local storage.

    pbjs.setConfig({
    userSync: {
        userIds: [{
        name: 'pairId',
        params: {
                liveramp: {
                    storageKey: '_lr_pairId'
                }
            },
      }]
    }
});

After implementing the PAIR ID storage configuration, you can test the integration to ensure PAIR IDs are included in bid requests. To learn how to do this, see Test Your RampID Module Configuration.Configure Prebid.js for ATS

Monitor the Match Rates

You can check the match rates and overall performance metrics for your PAIR ID inventory in Console so you can analyze which inventory can provide the value that you intended.

To check your match rates, to ATS > PAIR. It may take some time for the table to be populated with data as we are building the audience in real time.

The PAIR page displays the following columns:

  • Advertiser Name: The name of the advertiser who has completed the pairing.

  • PAIR Audience: The ID of the audience the advertiser has uploaded to complete the pairing.

  • Match Rate: The percentage of your audience that overlaps with the advertiser's.

  • Pairing Status: The status of the pairing, which can be one of the following;

    • Successful: More than 1000 matches were found.

    • Policy Fail: Less than 1000 matches were found. During the initial launch of your PAIR integration, you might see this status if your PAIR authenticated traffic has not yet reached the level where more than 1000 matches can be found as your PAIR traffic is gradually increasing.

    • Not Started: Pairing has not started yet.

  • Upload Date: The date the audience was uploaded by the advertiser.

  • Last Refresh: The date when the pairing was last updated between you and the advertiser.

In this section: