FAQs for Liveramp

Change audience of an existing segment

Once a segment is created by selecting an audience, it cannot be changed later. For any audience related changes, create a new segment.

Direct vs Data Store Distributions

Data Store (third-party data): Segments delivered to platforms governed by contracts held between LiveRamp and the destination platforms. Segments are discoverable to buyers in Liveramp excluding any that are blacklisted.

Q. Why Segments Are Not Available in the Data Store Yet?

A. Segments must go through an approval process before they appear in the Data Store. Segment approval status can be checked in the main panel of the Data Store for sellers. To enable a segment, go to Sell Data in Datastore, click Enable on DataStore to submit it for LiveRamp Business and Privacy approval.

Direct (first-party data): Segments delivered to platforms governed by contracts between the data provider(zeotap) and destination platforms. Segments are not discoverable to buyers in Liveramp.

Q. How to find out if a segment is direct or data store segment?

A. While selecting a segment for distribution if i. the segment name shows up in the list, then you are distributing it as a 3rd-party segment ii. if the field name(zeotap segment id) shows up instead of segment name, then you are distributing it as a 1st-party segment Also, the 1st-party segments won’t show up in the segment reporting tab for data.

Custom vs Syndicated Segments

Custom Segments: Are typically sent to destinations on behalf of specific advertisers. Example: P&G asks for a gender segment to be used on TTD. Destination Platforms need to be whitelisted for custom segments. Distributions go to the Advertiser’s seat at the Destination Platform.

Syndicated Segments: Public or Standard segments. Can only be sent to destinations that have agreed to accept the data or have been requested through Connect by the data buyer. When a destination requests a syndicated segment, this triggers an automated distribution sequence. Sent to the Public at the Destination Platform or an Advertiser Seat. Whitelisting not needed.

Creating a Data Store and Distributing to it

1. From the left sidebar menu, hover over OUT and then select “My Destinations” to navigate to the Your Destination Accounts page.
2. Click the New Destination Account tile.
3. Scroll through the available destinations, or use the search bar or the filter options, to locate your desired destination and then click Activ ate.

Be sure to select Data Store when activating a new Destination Account

1. From the Choose an Integration screen, click Activate for the desired integration type.
2. Enter the requested destination account information, following the guidelines given next to that field in the UI.
3. Review the configuration properties to make sure they're correct, and then click Finish It typically takes 24 business hours for Data Store segments to be approved

Distributing to DDP store

Use "Doubleclick for Data Store" Destination account to send and license data store segments to Google. All Data Store distributions to DoubleClick are first sent to a single LiveRamp-managed account at Google. Segments are then shared either publicly or directly to buyer accounts.

Use the following existing destinations to push segments to any client seat for any country:

Google DDP - All Devices : if you want to push for Device IDs and Cookies

Google DDP-US-Cookies Only : if you to push Cookies only

When you select a Data Store segment to add to a destination account, you'll be prompted at the bottom of the screen to "Add and Share". After clicking, a popup appears asking you to specify a Google product and customer seat ID.

For syndicated segments, select "Google Reseller" as the product and enter"0" as the seat ID.

For custom segments, if buyer has i. account then select DoubleClick for Publisher ii. account then Bid Manager Advertiser for Invite_Advertiser and Bid Manager Partner for Invite_Partner iii. AdEx account then DoubleClick Adexchange Buyer

Distributing to TTD

TTD accepts custom segments on demand, and syndicated segments after a review. To distribute custom segments to a specific buyer at TTD, need to activate a new destination account for each buyer. Liveramp will prompt to enter the the buyer's TTD advertiser ID during each new destination account creation. This is typically a short alphanumeric string that looks like "ac81c0z"

Has the data arrived at the end platform?

You can check on the status of your distributions by navigating to the “Out” tab in Connect, selecting the relevant destination account, then searching for the segment and looking for the status indicated under the “Active” and “Delivered” columns.

A green check mark under the “Delivered” column indicates that the segment has been delivered successfully.

If the client cannot see data in their account even if the green check mark is “Delivered” you should have the client reach out to their account representative at that platform. Note that typically takes platforms 48 business hours to ingest data after Liveramp has successfully delivered it to them.

Can’t add a segment to the Destination Account

Check to see if the segment is custom or standard. If it is a custom segment, you first need to whitelist the destination platform you want to distribute to before you can send the segment. You can do this by updating the taxonomy for the relevant segment(s)--under the “Whitelist Platforms” column

Whitelisted destinations

It is basically the data store destination to which we are pushing the segment and the field is only passed by us when someone selects the Private flag for Liveramp in Unity. So the whitelisted platform field in Liveramp should have the same data store listed which was selected in Unity.

Distributing to destination

MediaMath is a leading that ad buyers engage with using their TerminalOne (T1) platform. MediaMath accepts syndicated segments after a review, as well as custom segments on demand.

To distribute the syndicated taxonomy for visibility in the T1 public UI, contact the LiveRamp support team. They will submit the taxonomy to MediaMath, and deliver the syndicated segments if taxonomy is approved. The segments will appear in the Targeting section on the Strategy level, under the "Audience" tab, in the LiveRamp IdentityLink Data Store section.

Which audience to push segments to in Unity? Where should Liveramp check for uploaded files?

edit for Liveramp segments

Price of existing segments can be edited in Liveramp UI(Data Store Sell Data Segment Details). But Liveramp follows one segment, one price rule. So same segment cannot have different price for different destination accounts. Let your LiveRamp operational contact know that you have made the price change. When you first create a segment and perform a distribution to a specific destination platform, all Data Store metadata (such as Data Store segment names and prices) gets sent. If you subsequently change the segment price within Connect, that information does not automatically refresh at the destination platform. LiveRamp must initiate a manual refresh of this information.