...
Prefix | Meaning | Examples |
|---|
m_raw | Raw advertiser id
(iOS IDFA or Android Advertising ID). Case sensitive | Android
m_raw:dec820aa-41ae-43e0-b3b1-19e2ab258233
iOS
m_raw:C78B8B75-885A-4573-B394-CEB5B1337BA3 |
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.
NOTE: md5 hashing is compatible with google AdX hashing | m_md5: 86d8638a89ae4a53a57746500f268bcc
(hash of dec820aa-41ae-43e0-b3b1-19e2ab258233)
m_md5: d03b31165b28e930419700bcba1cd7ab
(hash of 0AAF2E9B-8237-66FE-4768-35EF193327CA)
m_md5: 95a3c8be285dcb7b83a4a76f3bf4a4f6
(hash of 7D50A078-3388-8161-AC55-FFE718377953) |
m_sha1 | NOT SUPPORTED | NOT SUPPORTED |
User matching flow
RTBSuite can keep 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_url?...[DSP_USER _ID]
DMP Stores Match | DMP calls
//[RTBSuite domain]/p/cm/[DMP_NAME]?u=[DMP_USER_ID]
DSP Redirects to:
//dmp_url?...[DSP_USER _ID]
DMP Stores Match |
DSP Stores Matching | DSP calls:
//dmp_url?...[DSP_USER _ID]
DMP Redirects to:
//[RTBSuite domain]/p/cm/[DMP_NAME]?u=[DMP_USER_ID]
DSP Stores Match | DMP calls
//[RTBSuite domain]/p/cm/[DMP_NAME]?u=[DMP_USER_ID]
DMP Stores Match |
...