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:
LinkedIn (see "Distribute Data To LinkedIn" for more information)
Microsoft (Bing) (see "Distribute Data to Bing" for more information)
Pinterest (see "Distribute Data to Pinterest" for more information)
Snapchat (see "Distribute Data to Snapchat" for more information)
TikTok (see "Distribute Data to TikTok" for more information)
Twitter (see "Distribute Data to Twitter" for more information)
Supported Destinations for Record Sync
Currently, the following destinations support Record Sync segment deletions:
When activating a destination account, you’ll see Record Sync versions for some of these integrations. Use the Record Sync version to take advantage of Record Sync’s user deletions.
Note
For some destinations, the standard first-party integration uses Record Sync. For more information, see the individual articles. linked abive
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
Jivox - First-Party Data
LiveIntent
Permutive
Prodege
Simulmedia
Teads
Trusignal - Modeling
Viant
Note
For Viant destination accounts, you do not need to wait 24 hours after activation to create a support case. As soon as you finish activating the destination account, create a support case to have LiveRamp finalize it.
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 to 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:
A&E Networks
Altice
AMC Networks
Charter TV
Comcast
Cox
Datalogix
DirectTV
Discovery
Dish
Fox TV
FuboTV
Hulu
NBCU - Data Collaboration
NBCU - D2C
Pandora
Paramount (fka Viacom)
Roku
Scripps (fka Newsy)
Sling
Spotify
Tubi.tv
Verizon
Vizio (Inscape)
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 the 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
To navigate to a destination-specific article with more detailed information on a particular destination, click the destination name link.
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 | Lookback Window | Record Sync Available | Accepts Raw Fields | Accepts Data Marketplace Data | Data Marketplace Pricing | LiveRamp Attribution Program |
|---|---|---|---|---|---|---|---|---|---|
|
| No | Yes | No | Yes | Yes | |||
|
| No | Yes | No | No | N/A | Yes | ||
|
| No | Yes | Yes | No | N/A | |||
|
| No | Yes | No | No | N/A | |||
|
| No | No | Yes | Yes | ||||
| Varies depending on the integration. | No | Yes | No | Yes | ||||
|
| Yes | Yes | Yes | No | N/A | |||
|
| No | No | Yes | Yes | Yes | No | ||
|
| No | Yes | No | Yes | No | |||
|
| Yes | No | No | No | Yes | No | ||
|
| Yes | No | No | Yes | Yes | |||
|
| Yes | No | Yes | No | Yes | |||
|
| Yes | Yes | No | Yes | ||||
|
| Yes | Yes | No | Yes | ||||
|
| No | No | No | Yes | No | |||
|
| No | 180 days | No | No | Yes | No | ||
|
| No | No | No | Yes (with conditions) | No | |||
|
| No | No | Yes | No | N/A | |||
|
| No | No | No | Yes | Yes | |||
|
| No | No | Yes | No | ||||
|
| No | No | Yes | No | N/A | No |