Сравнение версий

Ключ

  • Эта строка добавлена.
  • Эта строка удалена.
  • Изменено форматирование.

...

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

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

 

Cookie (user) matching

For matching DSP and DMP user ids DMP should support user matching aligned with RTBSuite DSP API. Depending of which side initiates matching/initiates syncs different workflows is applied. See table below:

...