Skip to main content

Activate a New Destination Account

A destination account at LiveRamp is a set of configurations that allow you to distribute data to a particular seat at a destination.

In most cases, you need to activate a first-party data destination account to distribute first-party data or a Data Marketplace destination account to distribute Data Marketplace data. You cannot distribute both first-party data and Data Marketplace data through the same destination account.

For certain first-party destinations, U.S. customers will have an additional option to choose a Record Sync-enabled destination account if you want to be able to have the user deletions within segment updates sent to the destination during data refreshes. See "Keep Destination Data Fresh with Record Sync" for more information.

Once you've activated the destination account, you can go to the Segment Distribution page for that destination account to distribute data to your seat at that destination.

Caution

  • To activate a destination account at a destination that requires OAuth authorization, you must have the appropriate permission level to create an OAuth connection for that destination. See "Managing OAuth Connections" for more information.

  • To distribute first-party data to Google, you must first provide LiveRamp with access to your Google account by mapping the appropriate LiveRamp account ID to your Google account. This must be done before you activate the Google destination account. For more information, see "Providing Access to LiveRamp".

  • To distribute data to Facebook through either the Direct Integration or the Data Marketplace integration, you must add LiveRamp as a partner in Facebook for the associated ad account ID(s) before you activate the destination account. For more information, see "Add LiveRamp as a Partner in Facebook".

  • Some destination accounts (such as LinkedIn, and Adobe Audience Manager) require additional manual configuration by LiveRamp after the destination account has been activated (for a list of these platforms, see the "Destination Platforms that Require LiveRamp Action" section below). Create a support case to complete the activation (see "Using the LiveRamp Community Portal" for instructions).

Tip

LiveRamp is integrated with hundreds of destinations, and we're adding new ones all the time. You can find the full list—which includes display, mobile, search, video, site personalization, and attribution platforms—at www.liveramp.com/partners.

To activate a new destination account in Connect:

  1. From the Connect navigation menu, click New Destination Account.

    C-_Global__Nav__Announcement-New_Destination_Accounts__menu__selection.png
  2. Scroll through the available destinations (or use the search bar or the filter options) to locate your desired destination and then click Activate on the tile for that destination.

    C_Activate_New_Destination_Account-activate_button.jpg

    Note

    The Activate button appears when you hover over the tile.

    Destinations that are unavailable to you (often because they were not included in your contract) will be “grayed out” and can’t be activated. You can contact your LiveRamp Customer Success Manager if you wish to have one of those tiles enabled.

  3. From the Choose an Integration screen, click Activate for the desired integration type.

    Caution

    Be sure to use the appropriate integration for first-party data or a Data Marketplace integration for Data Marketplace data. Create a support case (see "Using the LiveRamp Community Portal" for instructions) or contact your Customer Success Manager if you’re unsure which integration to activate.

    Note

    For certain first-party destinations, you'll have an additional option to choose a Record Sync-enabled integration if you want to be able to have user deletions sent to the destination during data refreshes. See "Keep Destination Data Fresh with Record Sync" for more information.

    Integrations that are unavailable to you (often because they were not included in your contract) will be “grayed out” and can’t be activated. You can contact your LiveRamp Customer Success Manager if you wish to have one of those tiles enabled.

  4. If desired, use one of the methods below to change the default end date:

    Active New DA End Date field.jpg
    • Click into the End Date field and select the desired end date from the drop-down calendar that appears.

    • Click the blue "X" in the End Date field to activate the destination account with no end date.

    Note

    By default, the end date is set to six months after the activation of the destination account, and the Account Status is set to “Active”.

  5. Confirm or change the identifier settings. If a destination supports multiple identifier types (for example, a mobile ad platform that supports both Android and iOS devices), you can choose which identifiers you'd like to send data to. The default identifiers for that destination will be used unless you change the selections.

    C-Activate_New_DA-identifier-settings.png

    Tip

    For those destinations that accept RampID as an identifier, we recommend that you keep RampID selected in order to maximize your reach and match rates.

  6. If necessary, view or edit the refresh options. The default refresh options that are suitable for the majority of the workflows for that destination are enabled (see “How LiveRamp Refreshes Distributed Data” for more information). To view or change the default refresh options for the selected identifier types, click the “Show Refresh Settings” link text.

    C_Activate_New_Destination_Account-show_advanced_refresh_settings_link-AoA.jpg

    To change the options (for admin-level users only), select or deselect the appropriate check boxes.

    C_Activate_New_Destination_Account-advanced_refresh_settings_checkboxes-ab0.jpg

    Caution

    The default options for each destination account should only be changed for custom or unique workflows, and only if you have a thorough knowledge of the impact of these settings. Changing the default options might result in your data not being refreshed appropriately.

  7. If the destination requires a valid OAuth connection:

    Tip

    See "Destinations That Require Authorization Using OAuth" for a list of OAuth destinations.

    1. Select one of your existing OAuth connections for that destination from the OAuth Connection drop-down list, or select + New OAuth Connection to create a new connection for that destination and follow the authorization process at the destination's website.

      C-Activate_New_Destination_Account-Select_OAuth_Connection.jpg
    2. Enter the appropriate information in the other OAuth-related fields (LinkedIn example shown - required fields vary by destination).

      C-Activate_New_Destination_Account-OAuth_fields.jpg
    3. Click VALIDATE OAUTH CONNECTION.

      C-Activate_New_Destination_Account-Validate_OAuth_Connection_button.jpg
  8. Note

    See "Activate a Destination Account for OAuth Destinations" for a list of OAuth destinations and information on creating an OAuth connection for those destinations.

  9. Enter the remaining requested destination account settings, following the guidelines given next to that field in the UI. Many destinations will also require you to enter your Account ID with that platform.

  10. Enter a destination account name (this will appear as the name of the destination account in Connect).

    C_Activate_New_Destination_Account-enter_destination_account_name.jpg
  11. Once you fill out all the required fields (and after fixing any validation errors highlighted in red), click CREATE.

    Activate a DA Continue button.jpg
  12. If you're activating a Google first-party integration destination account and you haven't previously provided LiveRamp with access to your Google account by mapping the appropriate LiveRamp account ID to your Google account, follow the appropriate instructions in "Providing Access to LiveRamp".

    Note

    If this access is not provided to LiveRamp, the distributions will get stuck in the "Failed" status.

  13. If you're activating a destination account for a platform that requires LiveRamp action to complete the configuration, you can either wait for 24 hours to see if LiveRamp is able to finalize the activation or create a support case to ask that the activation be finalized. For a list of these platforms, see the "Destination Platforms that Require LiveRamp Action" section below.

After you've activated the desired destination account, you're ready to distribute data to the destination account.

Note

  • Make sure to keep within the limits of the number of destination accounts your contract allows, if applicable.

  • By default, the precision level used by the destination account for distributing segments is the precision level used by the audience those segments are contained within. If you wish to change the precision level for a particular destination account only, create a support case (see "Using the LiveRamp Community Portal" for instructions).

  • Need to make property changes or want to deactivate a destination account you no longer need? You can edit the destination account properties at any time.

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 - First-Party Data

  • LinkedIn

  • LiveIntent

  • Permutive

  • Prodege

  • Salesforce Audience Studio (Krux)

  • Simulmedia

  • StackAdapt

    • Data Marketplace Custom Segments

    • Data Marketplace Custom Segments Ramp ID

  • Teads

  • Trusignal - Modeling

  • Viant

  • Videology - Data Marketplace