Types of Segment Data Fields

After your data has been uploaded to LiveRamp, LiveRamp creates fields from your segment data and classifies each field into one of the following field types, based on the data type and the number of distinct values.

In some cases, the field type will determine the types of operations you can perform with those fields.

A file-wide field is a way to send data where all the records in the file are members of one particular segment. The name of the file indicates the segment name for the file-wide field.


File name limit: Because segment names are limited to 250 characters, file names for file-wide field files must not be longer than 250 characters, including the file extension.


Additional fields are allowed: Files that contain file-wide fields can also contain additional fields with segment data.

For example, a file named "LiveRamp_test_field.csv" would result in a segment named "LiveRamp_test_field.csv" where every record in the file is part of the segment.

A binary field is a a field 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 audience member is member of a certain segment.


What about empty binary field values? If a binary field value is empty for a given record, it is assumed that that record is not a member of that segment.

For example, you may have a field "ownsCar" with values of "0" or "1,". You can use the segment of records which have a value of "1" for that field to target all car owners.

A numeric field is a type of data field that only contains numeric values.

LiveRamp can map raw numeric data (like annual income or date of most recent purchase) into segment ID codes that you can later modify into segment ranges using LiveRamp’s Segment Creator.


Including dates? If the field represents a calendar date and you want to use that field to create derived segments, use one of our preferred date formats: YYYYMM or YYYYMMDD. Do not include forward slashes (/) or hyphens (-).

A string field is a text-based field whose entries can contain letters, numbers, and special characters.

LiveRamp can ingest string data values, such as "blue" and "red" for a field named "favoriteColor", and then target based off the segment of users who have "favoriteColor=blue".

At LiveRamp, the number of distinct values a field contains determines whether that field is a raw field or an enumerated field. If a field has 100 or fewer distinct values, the field will be an enumerated field and the values for that field will be viewable as segments in Connect.

If a field has more than 100 distinct values, this will be a raw field and the values for that field will not be viewable in Connect.


Before uploading files containing fields with more than 100 distinct values, talk to your LiveRamp account manager.


Field values accumulate with each import. If the first import for a given field has 75 distinct values, we will enumerate those values. But then if a second import has that same field with 85 new distinct values (now a total of 160 distinct values), that field will be passed as raw in the second import rather than enumerated. This would then cause there to be two fields with the same name in Connect, but only one will show the field values (the enumerated field from the first import) and the duplicate field (the raw field from the second import) will not show any enumerated values to activate on.

Raw fields have some additional limitations:

  • Stats are not calculated on individual raw values. Instead, stats will be calculated at the field level.

  • Many destinations (such as Facebook and Google DBM) cannot accept raw fields.


Data Marketplace segments cannot be created from raw fields.


You can use raw segments to create derived segments in Connect.