История страницы

Revisions history

Basics

This document describes a generic way to upload DMP segments to RTBSuite(Getintent) DSP. The workflow is as follows:

• DMP uploads data (TSV gzipped files with headers) through SFTP protocol on RTBSuite servers
  • Batch files with segments
  • Taxonomy files with segments meta information.
• DSP RTBSuite starts using segments data for targeting

...

Batch Ffle name format

DMP data should be stored in txt.gz files and be named the following way:
[DMP ID].[DATE as yyyy-MM-dd_HH-mm-ss].[FILE ID].txt.gz
Where:

...

For display (desktop inventory format) [DMP USER ID] or [DSP USER ID] could be any string that doesn't contain ':' character.
For mobile DMP USER ID each user id should have a prefix

User matching flow

RTBSuite can store user matching tables on their side but it's no recommended and should be done only in case it's the only option to integrate with DMP. The following matching cases are supported:

...

Taxonomy import

To keep segments list up to date recommended to use auto taxonomy import. Taxonomy file should be placed in the same where batch file is placed. Taxonomy should have the same name prefix as batch file: [DMP ID].[DATE as yyyy-MM-dd_HH-mm-ss].[FILE ID].taxonomy.json

Taxonomy should be provided in json format and follow this format:

When no cost is provided then default pricing from DMP settings will be used.

[
    {
        "id": 1000,
        "name": "Mens 18-24",
        "cost_type": "RATE",
        "cost_value": 20,
        "currency": "USD",
        "advertisers": [
            1000,
            2000,
            3000
        ]
    },
    {
        "id": 1001,
        "name": "Mens 25-29",
        "cost_type": "FIX",
        "cost_value": "1",
        "currency": "USD",
        "advertisers": [
            1000,
            2000,
            3000
        ]
    }    
]