Skip to main content

Platform-Specific Distribution Information

Some destination platforms have specific criteria you need to keep in mind when distributing data. Use the information below and the articles in this section to make sure you set up your distributions correctly.

Destinations That Require Authorization Using OAuth

Currently, the following destinations require authorization using OAuth before any data can be distributed to the destination account:

Supported Destinations for Record Sync

Currently, the following destinations support Record Sync segment deletions:

Note

In the future, we hope to add additional destinations.

When activating a destination account, you’ll see Record Sync versions of each of these integrations. Use the Record Sync version to take advantage of Record Sync’s user deletions.

Destination Platforms that Require LiveRamp Action

For certain destination platforms, LiveRamp needs to perform a manual review and configuration to finalize the activation. In most cases, LiveRamp automatically performs this review and finalizes the activation within 24 hours after you activate the destination account.

Until the activation has been finalized, any segments added to distribution will remain in a "Queued" status.

If the activation hasn't been finalized within 24 hours, create a support case to ask that the activation be finalized.

The destination platforms listed below require LiveRamp action:

  • Adobe Audience Manager

  • Amazon - Data Marketplace

  • Jivox - Onboarding

  • LinkedIn

  • LiveIntent

  • Permutive

  • Prodege

  • Salesforce Audience Studio (Krux)

  • Simulmedia

  • StackAdapt

    • Data Marketplace Custom Segments

    • Data Marketplace Custom Segments Ramp ID

  • Teads

  • Trusignal - Modeling

  • Viant - Onboarding and Data Marketplace

  • Videology - Data Marketplace

Platforms that Do Not Accept Raw Fields

The following platforms cannot accept raw fields, so raw fields can often only be distributed these platforms by creating derived segments from them in Connect. If you try to distribute a raw field to one of these platforms, the delivery will fail.

For more information on raw fields, see "Raw Field".

Rate-Limited Destination Platforms

When it comes to ingesting or delivering data, there are always limits to how much data a system can process at a given time. The destination platforms listed below get large influxes of data and so at times are impacted by rate limits.

These platform rate limits can result in data distribution taking longer than the typical 12-72 hour processing time. Take this into consideration when planning for data delivery and campaign launches on the destination platforms listed below:

If a delivery to a rate-limited platform is delayed, we automatically retry the delivery each day, but performing the troubleshooting steps listed in "Troubleshoot Distributions to Destination Accounts" can still be helpful. However, if you need the priority increased on the delivery, create a support case.

Destinations that Do Not Support Matched Reach Stats

Matched reach stats for the destinations listed below are not supported, as they might not accurately reflect the total cross-device reach your audience has on those destinations' platforms:

To get matched reach stats for one of these destinations, contact your account representative at that destination.

Destination Comparison

Use the table below to compare some of our destination platforms:

Caution

The information listed below was current at the time of publication and represents our best understanding of the integration based on the information available at the time, including information given to us by the destination platform. Any sections not filled out are areas we did not have information on at time of publication. Use this as a general guide but check with the platform to confirm any areas that are critical to your use case.

Note

  • For some destinations, you can use the destination name link to navigate to a destination-specific article with additional information.

  • The list of account info needed might not apply to all integrations for that platform. See the destination-specific article or the destination account configuration screen in Connect for more information on the account info needed for a particular integration.

  • We will continue to add destinations to this list over time.

Destination

Identifiers Delivered

Account Info Needed

Requires OAuth

Precision Levels Allowed

Lookback Window

Record Sync Available

Accepts Raw Fields

Accepts Data Marketplace Data

Data Marketplace Pricing

LiveRamp Attribution Program

Facebook

  • Ad Account ID: The numeric Facebook ad account ID where your segments should be sent

  • Client Name: The name of your company or account

  • Package Name: The name of the distribution

No

  • Individual: Yes

  • Household: No

Yes

No

Yes

Advertiser Direct

Yes

Google Customer Match

  • Google Account ID: Google Account ID (MCC or CID)

No

  • Individual: Yes

  • Household: No

Yes

No

No

N/A

Yes

Google Ad Manager

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: Yes

  • CIDs/Platform IDs: No

  • Entityid: Google Account ID (MCC or CID)

No

  • Individual: Yes

  • Household: Yes

Yes

Yes

No

N/A

Google DV360

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: Yes

  • CIDs/Platform IDs: No

  • Product: Your DV360 account type

  • Entityid: Google Account ID (MCC or CID)

No

  • Individual: Yes

  • Household: Yes

Yes

No

No

N/A

Google Data Marketplace

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

No

  • Individual: Yes

  • Household: Yes

No

Yes

Yes

Programmatic Standard

The Trade Desk

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: Yes (UID2s)

Varies depending on the integration.

No

  • Individual: Yes

  • Household: Yes

30 days

Yes

No

Yes 

Programmatic Hybrid

Yes

Bing

  • Cookies: Yes

  • Mobile Device IDs: No

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

  • Customer ID: The Customer ID issued to you by Bing

  • Msa Email: Your Microsoft Account email

Yes

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No

Yes

No

N/A

Yes

Amazon

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

  • Advertiser ID: Your Amazon Advertiser ID

No

  • Individual: Yes

  • Household: Yes

No

No

Yes

Yes: Custom segments only

Programmatic Standard

No

Yahoo!

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

  • MdM ID: Your Yahoo! MDM ID

No

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No

No

Yes

Programmatic Standard

No

Twitter

  • Cookies: No

  • Mobile device IDs: No

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

  • Account ID: Your  Twitter advertiser account ID

  • Ttl in Days: The number of days that users added to this audience will remain actionable on Twitter

Yes

  • Individual: Yes

  • Household: Yes

No

No

No

Yes 

Advertiser Direct

No

TikTok

  • Cookies: No

  • Mobile device IDs: No

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

  • Advertiser ID: Your 19-digit TikTok account ID

Yes

  • Individual: Yes

  • Household: Yes

No

No

Yes

Yes 

Advertiser Direct

Yes

Snapchat

  • Cookies: No

  • Mobile device IDs: No

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

  • Client: The name of your company or account at Snapchat

  • Snapchat Ad Acct ID: Your Snapchat Ad Account ID

Yes

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No

Yes

No

Yes

Advertiser Direct

Yes

Pinterest

  • Cookies: No

  • Mobile device IDs: Yes

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

  • Advertiser ID: Your Pinterest-provided advertiser account ID

Yes

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

Yes

No

Yes 

Advertiser Direct

Yes

LinkedIn

  • Cookies: No

  • Mobile device IDs: No

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

  • Account ID: The 9 digit LinkedIn account ID

  • Reporting Contact Email

Yes

  • Individual: Yes

  • Household: Yes

No

No

Yes

Advertiser Direct

Yes

Nexxen

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

No

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No 

No

No

N/A

No

Xandr Invest

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: Yes

  • CIDs/Platform IDs: No

  • client_id: Your Xandr Invest Client ID

No

  • Individual: Yes

  • Household: Yes

180 days

No 

No

Yes

Programmatic Standard

No

OneView

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

  • Advertiser UID: The advertiser UID

No

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No 

No

Yes (with conditions)

Programmatic Standard

No

Criteo

  • Cookies: Yes

  • Mobile device IDs: No

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

  • Advertiserid: Your Criteo API Advertiser ID

No

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No 

Yes

No

N/A

Yes

StackAdapt

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

  • StackAdapt Platform Account ID: The name of your company or platform account ID

No

  • Individual: Yes

  • Household: Yes

No

No

Yes

Yes

Programmatic Standard

Yes

Nextdoor

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: Yes

  • Advertiser Name: The name of your company or platform account ID

No

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No

Yes

No

Yes

Reddit

  • Cookies: No

  • Mobile device IDs: No

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

  • Advertiser ID: Your Reddit Advertiser ID.

  • Advertiser Name: Your company name.

No

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

No

Yes

No

N/A

No