Getting Started with ATS for Brands
Brands can leverage ATS (Authenticated Traffic Solutions) as a standalone product to improve audience addressability or by integrating it with other LiveRamp offerings, such as Online Conversions API (CAPI) programs and eCST. These integrations allow optimized ad delivery and accurate insights into customer journeys without the complexity of building server-side integrations.
See the sections below to learn how to get the best out of ATS for brands.
Overall Implementation Steps
Getting started with ATS for brands 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 your ATS configuration
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 Your ATS Configuration
Once you can confirm that ATS is running on your websites and that identity envelopes are generated, you can add other LiveRamp products to your subscription to integrate with. For marketers' use case, the following products are available:
ATS Direct: If you have a LiveRamp Connect account, you can leverage ATS Direct to activate your people-based segments on your favorite publisher websites through direct deals with those publishers. This allows you to bypass the typical SSP (supply-side platform) workflow and establish a direct deal partnerships with publishers.
ATS Direct for marketers is enabled through Connect. To learn more, see "ATS Direct for Marketers".
Conversions API Program: LiveRamp's Online CAPI Program allows you to send online conversion events and identity envelopes directly to platform partners such as Meta, TikTok, Pinterest, and others for measurement.
You can set up the integration fully in Console with ATS for Web, or by creating API calls. To learn more, see "CAPI Programs"
Enhanced Client-Side Tag (eCST): LiveRamp eCST are tags that can be used to collect and log user activities (such as page views or ad views, adding items to a cart, or completing a transaction) and match the LiveRamp cookies and/or identity envelopes associated with those activities to RampIDs. To learn more, see "LiveRamp Enhanced Client-Side Tags for ATS for Web".
You must be running ATS for Web to utilize the eCST module integration. If you are calling the ATS API, see " Implement the Enhanced Client-Side Tag".
To learn how to add products to your subcription, see "Add Products to Your Subscription".