For data providers to integrate their 1st and 3rd party segments into the SpringServe platform we will need the following information.
...
| Column Header | Format | Description | Required | Example |
|---|---|---|---|---|
| Code | String | The DMP's segment Identifier. To be used in reporting for consolidation, and visible to the user | Yes | SEG123 |
| External Code | String | Used for Iris.TV, otherwise this value should be the same as the Code | Yes | intid_123 |
| Political | Alpha | A Yes or No indicator if the segment is considered political. | No | Yes No |
| Vendor | Alpha | The DMP or partner name exactly how they want it to be displayed in the SpringServe platform | Yes | TruAudience Liveramp |
| segment_category | Alpha | The category that the segment falls into | No | Auto - In Market Demographics Homeowner |
| description | Alpha | More detailed information about the segment such as household income range, specific car type, etc. | Yes | Online shoppers Travel Enthusiasts Married |
| CPM | Alpha Numeric | The CPM that SpringServe pays. | Yes | $1.00 |
...
<epoch_millis> is a numeric timestamp value.
<operation> will be OVR (overwrite) if the contents are to replace the segment_list for each named id_value, or APP (append) if the segment_list for each named id_value is to be added to the current value (if any) you have for that id_value.
<id_type> will be DVC, USR, or IPA designating that the contained id_values are device_id, user_ideid, or ip_address.
<format_version> is the version of the file format that was used, currently always 0.
<HHMMSS> is the human readable hour-minute-seconds of the timestamp.
<extra_info> is anything else (such as sequence numbering or descriptive comment) that may be appended to the name. If there is none, there will be no underscore after the <HHMMSS> value, before the “.tsv.gz”. Currently all files have a "_000" value here.
".tsv" designates that it is a tab separated file.
".gz" designates that it was been GZIPped.
All dates/times are UTC.
...