Creating EU Data Files

When creating and uploading EU data files, be sure to strictly follow all of the requirements listed below (in addition to the various guidelines in "Uploading Data").


Failure to follow these requirements exactly will result in your file being rejected.

Keep the following general requirements in mind:

  • Files cannot be processed without headers. Include a header row in the first line of every file that matches the contents of the file.

  • File headers must be consistentand in the same order for subsequent uploads to a given workflow (new and existing segments can be included, but all identifier fields must remain the same).

  • If you work with LiveRamp across multiple geographies, split out your files by country (e.g., one file with French customer data, one file with UK customer data, etc.).

  • Files must be rectangular (have the same number of columns for every row).

  • If any values contain the file’s delimiter character (for example, a comma in a .csv file), make sure that your values are contained within quotes.

  • Keep the uncompressed size of each file to 50GB or smaller. These are our recommended limits but if you send larger files we cannot guarantee that the processing time will meet our 48 hour SLA.

Contact your Product Operations Manager if you will have difficulty meeting any of these requirements.

Including as many identifiers on the user as possible yields the best results. All identifiers are optional, but make sure to follow these formatting guidelines, including using the exact header names listed below.

The bolded headers listed below are required, with the exact heading, for every file of PII identifiers you upload to LiveRamp. Additional headers are shown with their recommended header labels.


Match the case: The headers given are case-sensitive. Failure to match the case will cause the file to fail.


Want a template? Click here to download a .csv file with these headers that you can use as a template.


Don't have all identifier types? If you cannot supply a given identifier (such as name and postal, email, or phone), include the respective header(s) anyway and simply leave the column(s) blank. However, if including name and postal, make sure to include all required name and postal fields.




  • The unique identifier (customer ID) should be persistent across all uploads - the unique identifier will allow us to de-duplicate rows in the uploaded file (in case a file has multiple rows related to the same person).



  • No special formatting required





  • A single address for a consumer can be split across up to four address fields, or included in one field. If the address is split over more than four fields, the additional values will be dropped.

  • If you have more than one address for a consumer (such as a work address and a home address), place each address on a separate row (but segment data values do not need to be duplicated/included on the additional rows). Make sure that all rows for a particular consumer have the same CUSTOMERID so the rows can be tied together.




  • No special formatting required




  • Include up to 3 plaintext emails. Additional emails will be disregarded.










  • Include up to 3 of each email type. Additional email hashes will be disregarded.

  • Before hashing apply the following normalization rules:

    • Lowercase all characters

    • Remove any extra spaces before, after, or within the email address

    • Remove periods before "@" sign

    • Remove accents




  • You can include up to two plaintext mobile numbers and one plaintext landline number for each record.

  • Phone numbers should not include the country code.

  • Remove any parentheses, but you can leave any hyphens or spaces.

  • No hashed phone numbers allowed

We are flexible with how you choose to upload your user segments. You may include:



One Segment per File

File will only contain records with identifiers. We will group all records from the file into one segment with the name of the file as the segment name.

Binary Segments

You can include fields with only two values (for example, a field with values of only "0" or "1", or a field with values of only "true" or "false"), which is used to indicate whether a particular consumer is a member of a certain segment.

Enumerated Segments

LiveRamp can map raw numeric data such as income, or spend, into segment ID codes which you can later modify into ranges by using LiveRamp’s Segment Creator.

  • If including a date segment, use the preferred date formats (i.e. YYYYMM or YYYYMMDD if necessary). Do not include additional characters, such as “/“.


A given segment can have a maximum of 100 distinct values. If you require an exception, contact your Product Operations Manager.

The following file types are supported:

  • Comma delimited (.csv files)

  • Tab delimited (.tsv files)

  • Pipe delimited (|) (.psv files)

  • Semicolon delimited (.scsv files)


Excel files (.xls or .xlsx) and .txt files not allowed. Export your Excel spreadsheets and text files to a supported format before sending to LiveRamp.

File names must be in the following format:


Example file name: LiveRamp_UK_JoesAutoShop_NewCustomerTargeting_02172016.csv

Do not include spaces or special characters in the file name.

Files should be split out by country, where Country Code must be one of:

  • UK (UK may be used for all non-FR EU data)

  • FR


Be sure to include the country code! Files with names that do not include the country code will be rejected.


Contact your LiveRamp representative if you are not able to meet these file naming requirements.

Keep these additional requirements in mind.


Difference(s) from US Data File Requirements

Key-value files

Key-value files not allowed (column-based files only)

File compression

Only gzip (.gz) compression allowed

File limits

  • Maximum rows per file: 100,000,000 for UK data files and 30,000,000 for French data files

  • Maximum characters per line or row: 1,000

Audience limits

Maximum average of 1 file upload per day for PII-based UK data and 1 file per week for PII-based French data