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.
You will also be able to access the percentage match rate of your and the advertisers' audience in Console at any time.
Warning
This feature is still in alpha release for users in the EU.
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.
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.
Log in to Console.
Go to ATS > Web and select a configuration of your choice.
Select the "Integrations" tab.
Click
.Select Google PAIR.
Click
.
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.
Go to Prebid's download page.
Select the latest version of Prebid.js core or any version above 7.53.0.
Include the ‘Google PAIR ID’ submodule under the User ID Module.
Click Get Prebid.js.
Update your call to
pbjs.setConfig
to pass the required information to thepairId
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:{} // LiveRamp is the clean-room facilitator }, }], syncDelay: 3000 // 3 seconds after the first auction } });
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.
Monitor the Match Rates
You can check the match rates and overall performance metrics for your PAIR ID inventory in Console. This information is accessible in ATS > Web > PAIR.