For data providers to natively integrate 3rd party segments into the SpringServe platform we will need the following information.
Data provider to provide a synch pixel which will be applied to all, or some, of Springserve's traffic. This can be added immediately to build up the data segments.
File type: Excel or google sheet
Format: The following columns should be provided in the same order if possible with no commas in the value. Commas are used as the delimiter and will skew the data.
Can contain Underscores
|The DMP's segment Identifier. To be used in reporting for consolidation.||SEG123|
|Political||Alpha||A Yes or No indicator if the segment is considered political.||Yes|
|Partner||Alpha||The DMP or partner name exactly how they want it to be displayed in the SpringServe platform||Activate by Semcasting|
|segment_category||Alpha||The category that the segment falls into||Auto - In Market|
|description||Alpha||More detailed information about the segment such as household income range, specific car type, etc.||Online shoppers|
|CPM||Alpha Numeric||The CPM that SpringServe pays.||$1.00|
|ABC1||No||Activate by Semcasting||Consumer - Arts and Crafts Stores Shoppers||Arts and Crafts Stores Shoppers : All||$1.50|
|ABC2||No||Activate by Semcasting||Consumer - Arts and Crafts Stores Shoppers||Arts and Crafts Stores Shoppers : Hobby Lobby||$1.50|
|DEF1||No||Activate by Semcasting||Consumer - Arts and Crafts Stores Shoppers||Arts and Crafts Stores Shoppers : Jo-Ann Stores||$1.50|
|POL_RI_RI013||Yes||Activate by Semcasting||State House Districts Rhode Island - RI||RI013||$0.90|
|POL_RI_RI040||Yes||Activate by Semcasting||State House Districts Rhode Island - RI||RI040||$0.90|
|12345678||No||Tru Optik||Auto - In Market||New Vehicle||$1.50|
|91011121||No||Tru Optik||Auto - In Market||Used Vehicle||$1.50|
|31415161||No||Tru Optik||Auto - In Market||Small/Compact||$1.70|
|71819202||No||Tru Optik||Auto - In Market||Midsize||$1.70|
|12223242||No||Tru Optik||Auto - In Market||Pickup Truck||$1.70|
Segment file format
File structure: The format we generally expect is: ['Ip address'] | [list of segment attributes - comma delimited]
Naming convention: Can be anything but typically:
<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_ide, 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.
Unless otherwise specified SpringServe will apply standard boolean logic to determine segment overlap pricing.
- 'Or' statements alone (single charge)
- 'And' and 'And' (double charge)
- 'And/Or' (depends on whether one or both segments was used)
Storage service: SpringServe could provide S3 credentials for data transfer or we could use the data provider S3 credentials. There is no strong preference.
Each day, a new folder named <YYYYMMDD> gets created in the results_SpringServe S3 folder, previously provided. Within that <YYYYMMDD> folder, files will be created hourly with names formatted as:
Frequency: The frequency of data transfer needs to be agreed upon so that SpringServe knows when to export and process the segments for usage in the platform. Ex: Once nightly, 2 times a day, every hour
File Count and process: We need to know many files should we expect in each upload and if the files are a complete refresh or added on data.
SpringServe will provide a usage report which includes: segment ID, segment name, impressions, cost, and total revenue. If there is anything else that needs to be reported let SpringServe know, or provide a sample report.