Getting Started with ATS for Publishers
ATS allows publishers to unlock greater monetization opportunities by enriching their addressable inventories without relying on third-party cookies. See the sections in this article to understand how to get started with ATS and what you can do to get the best out of it.
Overall Implementation Steps
Getting started with ATS for publishers typically involves the following overall steps:
Work with a LiveRamp representative to discuss key implementation decisions
Set up your account in Console
Create a placement ID
Implement ATS on your websites
Integrate ATS with email service providers
Configure Prebid.js and ATS Analytics
Integrate your ATS configuration with other offerings
Key Implementation Decisions
Work with your LiveRamp Implementation manager to determine your initial choices in these areas:
Where you want to run ATS: Check if the countries you want to run ATS in are included in the list of ATS Supported Countries. Depending on the countries where you want to run ATS, your websites may be required to have an opt-out methodology.
How you will implement ATS: If you don't want to tinker with codes, you can choose to implement ATS via JavaScript on Console. You can also call the ATS envelope API directly or install the ATS Mobile SDK.
Which products you want to integrate ATS with: LiveRamp offers multiple offerings for brands and publishers, depending on their needs. Talk to your LiveRamp representative to discuss which products would be suitable for your use case.
Set Up Your Account in Console
Once you've made the necessary implementation decisions, you can start setting up your account in Console. If you have created an account for your organization in Console, you will have all permissions by default. This allows you to invite other users, granting them access to your organization's account and enabling them to perform tasks based on the permissions they have.
To learn more, see "Add User Accounts".
Create an ATS Placement
Before you can configure ATS on your websites or apps, you must create an ATS placement. Your placement ID represents the websites or apps where ATS will be running. It will be used for determining the loading rules and for making sure your property is following all of LiveRamp's requirements for running ATS.
When you create a placement ID, you will have to provide the domains and the countries where you want ATS to run. You will also have to confirm if you have a CMP (Consent Management Platform) set up on your websites.
To learn more, see "Create an ATS Placement".
Implement ATS on Your Websites
There are three ways you can implement ATS, depending on your needs and level of technical expertise:
ATS for Web (JavaScript implementation): You can implement ATS for Web by simply attaching a line of code to the header on all the pages of your website. This line of code is obtained from the Console after configuring how the envelopes should be obtained. To learn more, see "ATS for Web (Javascript Implementation)".
ATS API: If you want to integrate ATS but want to limit added JavaScript on your site, you may prefer to call the ATS API directly. Direct interaction will let you cut down the weight of the page and potentially make fewer client-side network requests, however this does add to the implementation complexity. To learn more, see "Configure and Install ATS API".
ATS Mobile SDK: If you want to run ATS on apps, you can implement ATS Mobile SDK available for Android and iOS devices. The SDK contains built-in functionalities to retrieve, refresh, and cache envelopes as well as consent handling. See "Implement ATS Mobile SDK" to learn more.
Installing ATS through LaunchPad allows you to set trigger conditions, enabling ATS to only fire based on the trigger types and locations you selected. If you are running ATS in the US, you can also specifically select which states in the US you want the trigger to fire.
If you have multiple ATS configurations, you can use a single LaunchPad wrapper to apply the same loading rules for all of your ATS configurations, rather than installing multiple ATS snippets.
Note
For brands, LaunchPad is a prerequisite for running Enhanced Client-Side Tags (eCST).
To learn more, see "Integrate ATS for Web with LaunchPad".
Integrate ATS With Email Service Providers
You may already have a large pool of identified users with the email service provider (ESP) you are working with. You can send identifiers in your ESP to ATS so you can still use your existing authentication flow while transforming the captured identities into identity envelopes. To learn how to do this, see "Email Service Providers (ESPs)".
Configure Prebid.js and ATS Analytics
ATS is optimized to plug into the open-source header bidding platform Prebid. This integration allows you to seamlessly pass identity envelopes to downstream bidders, resulting in improved monetization opportunities and advertiser demand. Prebid also facilitates the integration of ATS with Google PAIR through the Google PAIR ID module.
Once you have configured Prebid and added the Analytics module, you can then gain access to ATS Analytics in Console. ATS Analytics is a set of dashboard that gives you detailed overview of bid performances across all domains and how ATS improves your digital monetization.
To learn more, see "Configure Prebid.js for ATS" and "Configure ATS Analytics for Prebid.js"
Integrate ATS With Other LiveRamp Offerings
LiveRamp offers multiple ATS integrations and extensions for publishers' use cases. Some of these products are available to add via the Marketplace. To improve your monetization opportunities, we recommend implementing the following products:
ATS Direct: Enables direct media buys between publishers and marketers in LiveRamp Connect. If you have a brand partner using LiveRamp Connect you want to work with, ATS Direct can be used to facilitate the safe transfer of segment data without you ever seeing the brand's audience. To learn more, see "ATS Direct (Beta)".
Google Secure Signals: Allows publishers who are working with GPT (Google Publisher Tags) to share LiveRamp’s identity envelope directly with bidders that the publishers choose to work with. To learn more, see "Google Secure Signals for Publishers".
Google PAIR: Match cookieless, first-party identity data between publishers and advertisers through Google DV360. Returns both RampID and PAIR IDs in the envelope, with monitoring capabilities in Console. To learn more, see "Google PAIR".
Curation in Google Ad Manager: 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. To learn more, see "Curation in Google Ad Manager".