...
This document describes a generic way to upload DMP segments to RTBSuite( Getintent ) DSP. The workflow is as follows:
- DMP uploads data through SFTP protocol on RTBSuite serversGetintent servers
- Batch files with segments
- Taxonomy files with segments meta information.
- DSP starts using segments data for targeting
...
Prefix | Meaning | Examples |
|---|---|---|
m_raw | Raw advertiser id | Android |
m_md5 | MD5 hash of IDFA or Android ID. Hashing is done over string representation of UUID! After that hash is encoded to hex string. | m_md5: 86d8638a89ae4a53a57746500f268bcc |
m_sha1 | NOT SUPPORTED | NOT SUPPORTED |
User matching flow
RTBSuite can Getintent DSP 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:
DSP Initiates Syncs | DMP Initiates Syncs | |
|---|---|---|
DMP Stores Matching | DSP calls: | DMP calls |
DSP Stores Matching | DSP calls: | DMP calls |
...
Taxonomy should be provided in json format and follow this format:
| Node | Description | Mandatory |
|---|---|---|
| id | Segment id in DMP taxonomy | required |
| name | Segment name | required |
| cost_type | Comission type RATE or FIX | |
| cost_value | CPM in case of FIX or percents in case of RATE comission | |
| currency | Segment currency RUB/USD | |
| advertisers | List of advertisers ids to which segment should be availble |
When no cost is provided then default pricing from DMP settings will be used.
...