Skip to main content

Platform Data Buyer Integration Setup

After you’ve completed the integration steps to become a Data Marketplace buyer, you will be able to:

  • Browse the LiveRamp Data Marketplace catalog

  • Distribute segments to yourself via the Connect UI

  • Have Data Marketplace segments pushed to your platform by data buyers interested in leveraging data on your platform

Integration Steps

  1. Establish the connection (SFTP or S3) for LiveRamp to pass you data.

  2. Confirm that the initial test delivery is working as expected in terms of content, naming, and delivery location.

  3. Receive training from LiveRamp on how to find new segments, explore segment details, distribute to destination platforms, and report back to LiveRamp on data usage.

Establish the SFTP or S3 Connection

Data and taxonomy files can be delivered to an S3 bucket or SFTP. Provide the information listed below to your LiveRamp representative when setting up your integration.


When having files delivered to an AWS S3 bucket, you can only use the method where you create an IAM user under your AWS account. You cannot use the method where you authorize LiveRamp's user to deliver data to your bucket.

Information required for SFTP delivery:

  • Host name

  • Port

  • Username

  • Password

  • Root path

Information required for S3 delivery:

  • Access key

  • Secret key

  • Bucket

  • Root path for delivery

LiveRamp will prompt for a client name when a new distribution is being established. LiveRamp will incorporate this string into the delivery file path to help you distinguish deliveries. For example, if BrandX is distributing Data Marketplace segments to your platform, they would enter BrandX when setting up the distribution in Connect and we would deliver this data to /BrandX/<data file> in your SFTP or S3. We recommend communicating client IDs here vs plaintext names.

Types of Files You’ll Receive

For each Data Marketplace segment purchased, you will receive two types of files: data files and taxonomy files.

Data Files

Data files contain identifiers, such as cookies or mobile device IDs, tied to segment IDs. These segment IDs represent data segments you have requested or another user has pushed to your platform. The format will be one column containing identifiers followed by a tab, followed by a comma-separated list of segments that that identifier belongs to.


Data File Example


Identifier Format: Identifiers are returned in plaintext (unhashed) format.

Data files follow the naming convention: "lr_<idfa, aaid, or cookie>_segments_<YYYYMMDD>_<HHMMSS>_<liveramp_distribution_identifier>_part<XX>.gz" (for example, "lr_aaid_segments_20180821_150815_1468649_part003.gz"). The default file path is "bucket/liveramp/datastore/{'advertiser_name'}".


Larger Files: The data file will be split into multiple files if the decompressed file size exceeds 5GB.

Segment Data Refreshes

When a new distribution is initiated you will receive a full delivery of all associated IDs to segments. After this initial push, LiveRamp continues to establish matches for a given segment (since we are constantly growing and updating our graph). The data seller may also be supplementing this segment with up-to-date data. Every 3-6 days, LiveRamp delivers any additional matches that have been found for segments set up to deliver to you.

Taxonomy Files

Every initial distribution includes a taxonomy file. Taxonomy files contain the metadata associated with the data you are receiving in your data files:

  • Segment ID: The ID of the segment

  • Key: The field name

  • Value: The value name

  • Provider Name: The name of the data seller

  • Segment Name: The segment name

  • Segment Description: A description of the segment

  • Use Restrictions (if any): Information on how the segment can or cannot be used

  • Permitted Advertisers

  • Custom: "TRUE" for custom segments and "FALSE" for standard segments

  • Price ($CPM): The CPM for the segment


Taxonomy File Example

File names for taxonomy files follow the naming convention "lr_taxonomy_<YYYYMMDD>_<HHMMSS>_<liveramp_distribution_identifier>.csv" (for example, "lr_ds_taxonomy_20180828_073917_651869.csv").