LiveRamp Activation API

The LiveRamp Activation API offers programmatic access to LiveRamp marketing solutions.

Guides    API Reference

Uploading Files to LiveRamp

Learn about the file format requirements for uploading files.

After your customer selects a segment (list) to distribute using LiveRamp, your integration must upload the related file. The file must be correctly formatted and then uploaded. This section describes the required file formats and information about uploading files.

File Formats

When your customer selects a segment for distribution, your application must convert that data into a format that LiveRamp can automatically process. The required format varies depending on whether the data is PII-based or device-based.

File Names

File names must include the customer name, list name, and date created.

[CustomerName]_[ListName]_[DateCreated]

The date created should be in YYYY-MM-DD format. For example:

KevinsBoatStore_HighLifetimeValue_2019-04-15.csv

Formatting PII-based Data

For PII-based data such as name, postal address, email address, or phone number, your application must map the original customer source data to the LiveRamp required file format.

Required file format for PII-based dataRequired file format for PII-based data

Required file format for PII-based data

PII-based data file requirements

  • Files must be comma-separated value (CSV), column-based files.
  • Columns A-O must always be included.
  • A header must be included in every file, and the column headers for columns A-N must exactly match the headers in the above example.
  • The Client Customer ID (CCID, column A) must be a unique ID so that LiveRamp can use it as an audience key to deduplicate and consolidate records
  • Column O (“specific_list_name”) should always be the segment name to be created and displayed in the application UI. All cells below the header row should be filled with a “1” to indicate that every row is a member of that segment.
  • Do not add additional columns. Additional columns will break the automation.
  • If there are no values for a particular column, keep the column header but leave the cells empty.
  • When sending name and postal addresses, all fields must be present (first name, last name, address, city, state, ZIP code).
  • Do not enter any values in the ZIP4 column (column I).
  • Do not hash any of the identifiers, such as the email address or phone numbers. Include only plaintext (raw) identifiers.
  • Make sure that the file has more than 25 rows and not more than 500,000,000 rows

Formatting Device-based Data

Your customers can also distribute device-based data, such as segments tied to cookies or mobile device IDs such as an AAID for Android devices or IDFA for iOS devices.

Device-based data file requirements

  • Files should have only two columns: the identifier column with either the cookie or the mobile device ID, and the segment name column similar to column O for PII-based data files.
  • To send both mobile device ID types in one column, label the first column Mobile Device ID
  • To send each mobile device ID type in separate columns, send two files, one with an AAID column and one with an IDFA column
  • To send cookies, label the first column Cookie ID

Sending cookie-based files requires a cookie sync with LiveRamp. Contact your LiveRamp Representative if you’re interested in setting up a cookie sync.

Upload Files

When the file is correctly formatted, upload the file to LiveRamp's SFTP.

The application must upload the file to the customer-specific SFTP directory provided by your LiveRamp Representative. The directory is specific for each uploaded data type: PII-based or device -based. SFTP server access credentials and directory access are specific to each customer.

📘

Upload file limits

When uploading multiple files, do not exceed 24 file uploads per day.
Exceeding the maximum average of 1 file upload per hour may impact SLAs.

Updated 6 months ago

Uploading Files to LiveRamp


Learn about the file format requirements for uploading files.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.