Skip to main content

Data Delivery Guide for Onboarding Integration Partners

For integration partners who receive onboarding data, you’ll receive two types of files for each distribution that's delivered to your endpoint: data files and taxonomy files.


Certain integration steps must be completed to become an onboarding integration partner and receive onboarding data in your platform. Talk to your LiveRamp rep and see “Setting Up LiveRamp File Deliveries” for more details on the information needed to receive files from LiveRamp.


The file information provided here is the default format for most integrations, but the format might vary depending on your configuration.

Data Files

Data files contain identifiers, such as cookies or mobile device IDs, tied to segment IDs. These segment IDs represent data segments you 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.


This is the default format for data files, but the format might vary depending on your configuration.

Data File Example
Figure 4. Data File Example

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

  • File Naming Convention: By default, data files follow the naming convention: "lr_<DEVICE TYPE>_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/onboarding/{'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 LiveRamp client initiates a new distribution to your platform, you will receive a full delivery of all associated IDs to segment IDs. After this initial push, LiveRamp continues to establish matches for a given segment (since we are constantly growing and updating our identity graph). The LiveRamp client might also supplement this segment with more up-to-date data, which would result in the delivery of additional data. For more information, see "How LiveRamp Refreshes Distributed Data."

Taxonomy Files

Every initial distribution includes a taxonomy file (see the example below). Taxonomy files contain the metadata to interpret the segment IDs:

  • Segment ID

  • Field Label

  • Value Label

If a LiveRamp client adds additional segments to an existing distribution, this triggers the delivery of a subsequent taxonomy file that typically only contains the changes from the previous file.


Some taxonomy files might contain an additional "Delta" column to indicate whether the taxonomy file has changed from the previous delivery.

File Naming Convention: File names for taxonomy files follow the naming convention "lr_onboarding_taxonomy_<YYYYMMDD>_<HHMMSS>_<liveramp_distribution_identifier>.csv" (for example, "lr_onboarding_taxonomy_20180828_073917_651869.csv").