DMP Segment Uploader

This document is for DMP segment providers who wish to include their DMP segments in Tap's Audience Segments Targeting feature. It describes the process and specifications used for uploading DMP targeting segments to Triton Digital.

Overview

• Publishers who use your DMP segments must have a contract with Triton Digital that provides them access to your DMP audience targeting segments.
• You must work with a Triton Digital Partner Integration Specialist to initiate the upload process and to confirm the setup.
• The S3 folders described below are set up by Triton Digital, who will provide you with access details once they are set up.
• Initially, your segment uploads will be evaluated by a Triton Digital Partner Integration Specialist to confirm they conform to specifications. If they do not conform, the Triton Digital Partner Integration Specialist will work with you to help fix any errors. Once everything is "on spec" your uploads can be done automatically.

Taxonomy

Taxonomy File Locations

• Two S3 buckets are initiated by Triton Digital; one for production and one for pre-production:
  • s3://triton-dmp-integrations>{environment(prod|preprod)}>{DMP Provider}>{PublisherID}>taxonomy>
• Files should be dropped in a folder representing the day of the file under the format (YYYYMMDD).
• Files should be placed in a specific folder for each day:
  • s3://triton-dmp-integrations>{environment(prod|preprod)}>{DMP Provider}>{PublisherID}>taxonomy>{YYYYMMDD}

Example for DMP provider DoccoSegments, publisher ID 12345, on "prod" environment:

s3://triton-dmp-integrations>{environment(prod)}>{DoccoSegments}>{12345}>taxonomy>{20230206}

Taxonomy File Format

The naming convention for a segment file is as follows:

• {YYYYMMDD}.{VOLUME_NUMBER}.taxonomy.tsv.gz
  • YYYYMMDD= Date of upload.
    • Example: 20220803.001.taxonomy.tsv.gz
  • VOLUME_NUMBER = Volume number to split a large file into many smaller ones

The taxonomy file is a tab-separated formatted file which includes the following columns in the following order:

• Segment ID
  • Mandatory
  • Must be unique for the publisher being integrated
• Segment Name
  • Mandatory
• Price
  • Mandatory.
  • Must be in USD. Decimals are optional; 2 is interpreted as 2.00, while 2.00 is also interpreted as 2.00.
  • 0 is an accepted value
  • Double (data type)
• Company
  • Optional
  • Can be used if the segment is provided by a third party
• Segment Category
  • Optional
• Status
  • Mandatory
  • Active or Inactive

Example:

Segment ID        Segment Name        Price        Company        Segment Category  Status

1234457   Age > 25-30   1.40   Triton Digital   Age Active

Taxonomy Processing Details

• Each segment is updated completely with provided data.
• If an existing segment is not in the file, it will not be modified.

Segments – Listener Mapping

Segment File Locations

• Two S3 buckets are initiated by Triton Digital; one for production and one for pre-production:
  • s3://triton-dmp-integrations>{environment(prod|preprod)}>{DMP Provider}>{PublisherID}>segments>
• Files should be dropped in a folder representing the day of the file under the format (YYYYMMDD).

Segment File Formats

The naming convention for a segment file is as follows:

• [inc,full].{YYYYMMDD}.{VOLUME_NUMBER}.{TYPE}.tsv.gz
  • inc,full = Either the file is incremental or full.
    • Use full to completely replace the listener database with the contents of the new segments file.
    • Use inc (incremental) to add or remove the defined segments in the new segments file. You must put either + or - at the beginning of the listener-id segment-ids line. (See example, below.)
      • Use + to add the defined segments
      • Use - to remove the defined segments.
  • YYYYMMDD = Date of upload
  • VOLUME_NUMBER = Volume number to split a large file into many smaller ones
  • TYPE = Listener ID type
    • Supported ID types are: cookie, gaid, idfa, ip
  • Example: inc.20220803.001.ip.tsv.gz OR full.20220803.001.cookie.tsv.gz  
• The file contains a list of listener IDs with their corresponding segments represented as a comma-separated list of segment-ids. This file is a tab-separated file which follows a structure like this:
  Example for full:
  listener-id   segment-ids
  90468516-427e-453b-b8f7-fee93c539f76   111,222,333,444
  Example for inc:
  listener-id   segment-ids
  +90468516-427e-453b-b8f7-fee93c539f76   111,222,333,444

Segment Processing Details

• Each time a file is processed, the segments previously imported for any given listener are overwritten. The segments of listeners not present in the file being processed are not changed.
• If no changes are made to a listener within 35 days, their entry in the database is erased. Therefore if you (the DMP) want to keep the segments active for a listener, you need to send it again within 35 days.
• Segments not uploaded via the taxonomy uploader are ignored.

Feedback

Send any comments or corrections to docs@tritondigital.com. (This is a NO REPLY email address used only for documentation feedback. For customer support, go to the Triton Digital Support Center.)