OpenRTB extension

Bid Request

OpenRTB 2.X

The unencrypted construction (first, below) is preferred and in use at most exchanges.

Note that if the keyv parameter is present, the id value is expected to be encrypted. If keyv is not present the id field should be unencrypted and may only be sent to known DigiTrust members in good standing.

{
 ...
 "user":{
  "ext":{
   "digitrust": {
     "id": "oIB0sw9b77k="
    }
  }
 }
}

{
 ...
 "user":{
  "ext":{
   "digitrust": {
     "id": "RlKOeWr2qQbFFrsiV3Yk6a2xT/cjnOHBMuWixkoHrrO80SVWnNUYCE2bkUc4B43FGBhRXRpuqDTdaheXyGXhDI1iAbf065lN96EMeIbEW4dymXj4iTcY3hrLh/tVhjEgQ59PJd7ENk3Ru+F+47qkLNDvPkluVAadGjINk5uZoSHwcUJd9taWJu0S4z+votoxDSH8RPtc6lDOcYsMnWFnGr+iNGkQXMt7FK7DgL2jF0JTKGozTJGVWKlXCN8zXiRBp/Y409uHgLLIXQQC4B+TcVX/wh0/xZGcR5/mW2GmgIEG/N0b5oWsepmIWvOao3fl8m+HJH43gCkJaCOzhY3abw==",
     "keyv": 4
    }
  }
 }
}

OpenRTB 3.0

OpenRTB 3.0 provides a standardized container for "extended" identity objects identified by the owner.

The expectation is that only un-encrypted ID values will be passed in ORTB 3 implementations.

{
  ...
  "user": {
    "eids": [
      {
        "source": "digitru.st",
        "uids": [
          {
            "id": "oIB0sw9b77k=",
            "atype": 1
          }]
      }]
  }
}