Skip to main content

Curation in Google Ad Manager for Publishers (Beta)

LiveRamp's integration with Google Curation allows publishers using Google Ad Manager (GAM) to leverage RampIDs across Google’s ad tech ecosystem by matching them with cohort IDs in real time. This solution enables dynamically generated Deal IDs representing first-party and third-party audience segments to be sent to DSPs in the bidstream.

The Curation workflow ensures marketers can target their desired data across as much of publishers' inventory as possible. It gives publishers access to DV360 third-party data demand on their cookieless inventory, increasing their ad revenue.

Caution

This feature is not available in Europe.

If you implement ATS through direct API calls, see Google Secure Signals for Publishers.

LiveRamp Integration with Curation Workflow

Google_Curation_Flow_Publishers.png

When a bid request for an envelope is sent to an SSP (for example; AdX), GAM makes a call to LiveRamp's Curation API endpoint. LiveRamp matches RampIDs to cohort IDs in real-time, using data provided by data sellers through LiveRamp’s Data Marketplace and any first-party or second-party segments from LiveRamp advertisers distributed for matching. Google uses these cohort IDs to generate Deal IDs and auction packages, which are then forwarded to the DSPs, including DV360.

How to Implement Google Curation for Publishers

  1. Integrate an ATS configuration with Google Secure Signals.

  2. Share data for curated inventory and make sure to share secure signals with 'LiveRamp’ as your curation partner.

  3. Contact your LiveRamp representative and inform them that you've integrated with Secure Signals and would like to implement Curation in Google Ad Manager.

When Google Secure Signals is activated, ATS.js will initially search for a GSSP envelope, which is a size-optimized envelope used in the Google SSP (Supply-Side Platform) system, in browser storage.

If a GSSP envelope is not available, ATS.js will pass the regular ATS envelope to the Google Publisher Tag (GPT) on the page. Secure Signals only allows one signal to be shared per vendor, which is why only one of the two envelopes can be passed.

In this section: