LiveRamp - Distribution connection

Last update: 2024-01-08
  • Created for:
  • Developer
    User
    Admin
    Leader

The LiveRamp - Distribution connection enables you to activate audiences from Experience Platform to premium publishers across mobile, web, display, and connected TV mediums.

IMPORTANT

This destination connector and documentation page are created and maintained by LiveRamp. For any inquiries or update requests, contact LiveRamp directly here.

Supported destinations

LiveRamp - Distribution currently supports audience activation to the following platforms:

Use cases

To help you better understand how and when you should use the LiveRamp - Distribution destination, here is a sample use case that Adobe Experience Platform customers can solve by using this destination.

The marketing team of a sports apparel retailer used the LiveRamp - Onboarding connection to send audiences from Experience Platform to their LiveRamp account.

Through the LiveRamp - Distribution connection they can now trigger the activation of the onboarded audiences to the supported destinations. Then, they can target users on mobile, open web, social, and CTV platforms.

Onboard audiences to LiveRamp

Before activating audiences through the LiveRamp - Distribution connection, use the LiveRamp - Onboarding connection to export your Experience Platform audiences to LiveRamp.

After you have onboarded your audiences to LiveRamp, continue the activation workflow from the connect to the destination step to select and configure your target destination platforms for data activation.

Connect to the destination

IMPORTANT

To connect to the destination, you need the View Destinations and Manage Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.

Authenticate to LiveRamp

To authenticate to the destination, fill in the required fields and select Connect to destination.

Platform UI image showing the destination connection screen.l

  • LiveRamp Organization ID: The organization ID of your LiveRamp account (listed as owner_org in your LiveRamp-provided credentials).
  • Password: Your LiveRamp account password (listed as secret_key in your LiveRamp-provided credentials).
  • Token URL: Your LiveRamp token URL.
  • Username: Your LiveRamp account username (listed as account_id in your LiveRamp-provided credentials).

Configure destination details

After you have successfully connected to your LiveRamp account, enter the required information to connect to the destination that you want to activate audiences to.

Platform UI image showing the destination details screen.l

  • Name: Fill in the preferred name for your destination connection.
NOTE

When naming your destination, Adobe recommends to follow this format: LiveRamp - Downstream Destination Name. This naming pattern helps you quickly identify your destinations in the Browse tab of the destinations workspace.


Example: LiveRamp - Roku.

  • Description: Enter a description for your destination. Use a description which helps you easily identify the purpose of this destination.
  • Destination: Use the drop-down menu to select the destination to which you want to activate audiences. The destination you select here directly affects what you see in the destination-specific settings screen.
  • Integration: Select the integration account that you want to use for your destination.
  • Identifier: Select the identifiers supported by your destination. Currently, all the destinations have their supported identifiers prefilled in the drop-down menu.

Destination-specific settings

Each of the destinations supported by LiveRamp - Distribution requires you to fill in specific configuration options.

See the sections below for detailed guidance on how to configure each destination.

4C Insights

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the 4C Insights destination.

  • 4C Brand Profile ID: Enter the numeric ID associated with your 4C Brand Profile. If you do not have this ID, contact your 4C client services representative.

Acast

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Acast destination.

  • Client name: Your advertiser account name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Ampersand.tv

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Ampersand destination.

  • Your Company Name: Your company name, as you would like it to be shown to the destination partner. Do not use spaces or special characters.

Captify

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Captify destination.

  • Client name: Your advertiser account name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Cardlytics

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Cardlytics destination.

  • Client name: Your advertiser account name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Disney (Hulu/ESPN/ABC)

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Disney destination.

  • Advertiser data destination terms agreement: Type in I AGREE to confirm the acknowledgment and agreement to the Disney advertiser data terms.
  • Client name: Enter your company name as you want it to be shown to the destination partner.
  • Email address: Enter an email address tied to an individual. This email address serves as a signature to the advertiser data terms agreement.

iHeartMedia

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the iHeartMedia destination.

  • Client Name: Your advertiser account name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Index Exchange

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Index Exchange destination.

  • Account Name: Your Index Exchange client account name. Do not use spaces or special characters.

Magnite CTV Platform

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Magnite CTV destination.

  • Client: Your client name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Magnite DV+ (Rubicon Project)

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Magnite DV+ destination.

  • Partner ID: The Rubicon Project Partner ID associated with the publisher who owns the segment/data. Contact your Rubicon Project account representative if unsure of the value you should use.
  • Seat ID: Magnite DV+ Seat ID provided by your Magnite account manager

Nexxen (formerly known as Amobee)

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Nexxen destination.

  • Rate Type: Rate type represents the way data usage should be billed. All $0.00 rates should be flat fee. Confirm with your Nexxen representative if you’re not sure which rate type to use.
  • Market ID: Enter the numeric Market ID where the Nexxen data contract should be created. If you are doing “AlwaysOn” syndication across every market in the Nexxen platform, enter -1.
  • Advertiser ID: If you’re sending data to a single advertiser in the Nexxen platform, enter the numeric Nexxen Advertiser ID. If you want to make the data available to all advertisers in a market or if these segments are “AlwaysOn”, enter -1.
  • Contact Email: Enter the email address which Nexxen should use to send data contract details. Most likely this is your own email address, but it can also be an email alias. For multiple recipients, separate using commas ( email1@domain.com, email2@domain.com).

One Fox

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the One Fox destination.

  • Client: The name of your company/distribution account as you would like it to appear to the partner. Use your company name by default. Contact your partner account representative if unsure what name to use. Do not use spaces or special characters.

Pandora

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Pandora destination.

  • Account name: The name of your Pandora account. Contact your Pandora account representative if you are not sure what your account name is. Do not use spaces or special characters.

Reddit

To configure details for the destination, fill in the fields below.

Platform UI image showing the customer data fields for the Reddit destination.

  • Reddit advertiser ID: Your Reddit advertiser ID. Must begin with “t2_” or “a2_”. Contact your Reddit representative if you do not know your advertiser ID.
  • Reddit advertiser name: Your Reddit advertiser name. Do not use spaces or special characters.

Roku

To configure details for the destination, fill in the fields below.

Platform UI image showing the supported identifiers for the Roku destination.

  • Roku account email address: Enter the email address tied to your Roku account.
  • Roku account representative email address: Enter the email address of your Roku account representative. To enter multiple addresses, separate them by commas.

Spotify

To configure details for the destination, fill in the fields below.

Platform UI image showing the supported identifiers for the Spotify destination.

  • Client name: Your advertiser account name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Taboola

To configure details for the destination, fill in the fields below.

Platform UI image showing the supported identifiers for the Taboola destination.

  • Account manager email address: The email address of your Taboola account manager.
  • Segment type: The segment type. Only first party segments are currently supported.

TargetSpot

To configure details for the destination, fill in the fields below.

Platform UI image showing the supported identifiers for the TargetSpot destination.

  • Client name: Your advertiser account name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Teads

To configure details for the destination, fill in the fields below.

Platform UI image showing the supported identifiers for the TargetSpot destination.

  • Teads ID: Your Teads ID

WB Discovery

To configure details for the destination, fill in the fields below.

Platform UI image showing the supported identifiers for the WB Discovery destination.

  • Client name: Your advertiser account name, as you would like it to be shown to the destination partner. Use your company name. Do not use spaces or special characters.

Enable alerts

You can enable alerts to receive notifications on the status of the dataflow to your destination. To receive notifications on the status of your dataflow, select an alert from the list. For more information on alerts, read the guide on subscribing to destinations alerts using the UI.

When you are finished providing details for your destination connection, select Next.

Activate audiences to this destination

IMPORTANT

To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

The LiveRamp - Distribution connection activates audiences which have already been onboarded to your LiveRamp account through the LiveRamp - Onboarding connection.

To successfully activate your audiences, you must select the same audiences that you have previously onboarded to LiveRamp.

IMPORTANT

Selecting audiences which have not been previously onboarded through the LiveRamp - Onboarding connection does not trigger the onboarding of the new audiences.

Exported data / Validate data export

To verify and monitor the activation of your audiences, log in to your LiveRamp account and check the activation metrics.

If you have questions about the audience activation, contact your LiveRamp account representative.

Data usage and governance

All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, read the Data Governance overview.

Additional resources

For more details on how to configure your LiveRamp - Onboarding destination, see the LiveRamp - Onboarding documentation.

On this page