Platform-Specific Requirements for CAPI Programs
To integrate your ATS configuration with LiveRamp's Online Conversions API programs, you are required to provide account IDs and access tokens from the platforms you want to send events to. Providing these IDs means that you are allowing ATS to send events to the configured platforms on your behalf.
You can add the following identifiers in your Conversions API settings. To go there, select ATS → Web from the navigation pane and click on an ATS configuration. Select the Integration tab and click on an existing Conversions API configuration, or click to create one.
Amazon
Amazon Ads account ID: If you've already set up an Amazon Ads account for your websites, we recommend using the same account ID for your browser and server events. Amazon ad accounts may contain multiple countries. An advertiser will usually have 1 ads account ID linked to multiple country-specific profile IDs.
Dataset name: The name of the dataset where the conversion definition is defined.
OAuth Authentication: To give ATS access and authenticate requests to Amazon, a user with admin-level access to Amazon DSP must perform an OAuth in Console. Under the Amazon Conversions API Settings section, click . From the new window that opens with Amazon's sign-in or login screen, enter your credentials and then click .
Meta
Meta envelope: Contact your LiveRamp representative to get Meta envelopes implemented for you. When applied, two envelopes will be returned on a given ATS request. One is a regular ATS identity envelope, and the other is a Meta-encoded RampID, scoped for Meta.
Pixel ID: If you’ve already set up a pixel for your website, we recommend that you use the same Meta pixel ID for your browser and server events.
Meta access token: You can obtain a Meta Access Token via Events Manager (recommended) or using your own app.
See Meta's article "Get Started" to learn how you can obtain the above requirements.
OpenAI
OpenAI account ID: Your OpenAI ad account ID.
OpenAI authentication token: The Ads API key scoped to your OpenAI ad account, which allows ATS to authenticate requests to OpenAI. See OpenAI's article "Authentication" for more information.
Snapchat
Pixel ID: You can find your Pixel ID by logging in to Snapchat Ads Manager and navigating to the Events Manager settings. If you don't have a Snap Pixel set up yet, see Snap's article "Getting Started with Enabling the Pixel" to learn how to set it up.
Snapchat access token: To give ATS access and authenticate requests to Snapchat, you need an access token. See Snapchat’s article “Access Token” to learn how you can generate the token.
Pinterest account ID: If you’ve already set up a Pinterest business account for your website, we recommend that you use the same account ID for your browser and server events.
Pinterest access token: You can obtain a Pinterest access token via Ads Manager (recommended) or using your own app.
See Pinterest’s article "Send conversion events to the API" to learn how you can obtain the above requirements.
TikTok
TikTok ad account ID: If you’ve already set up a TikTok Ads Manager account for your website, we recommend using the same ad account ID for your browser and server events. See TikTok's article “How to set up a TikTok Ads Manager account” to learn more.
TikTok authentication token: To give ATS access and authenticate requests to TikTok, you need an access token from TikTok. To learn more, see TikTok's article "Setup guide for Web".
The Trade Desk
Caution
The Trade Desk Online Conversions API connector is currently in limited availability. If you're interested in being considered to participate, contact your LiveRamp representative.
Merchant ID: Your Trade Desk merchant ID, which can be found in the Trade Desk UI on the Merchant Preferences page.
Tracking tag ID: The Trade Desk's tracking tag ID that is appended to the page. A tracking tag (also known as pixels) is a piece of code which loads an anonymous cookie every time a new user lands on a website. To learn more, see The Trade Desk's article "Tracking Tags".
Yahoo
Yahoo pixel ID: A Yahoo pixel ID that is set as the default pixel for Yahoo In-Flight Outcomes (IFO) conversions. To learn more, see Yahoo's article "Product Conversions API".