Device.didmd5
A hardware device ID such as the IMEI, hashed with MD5. Present since OpenRTB 2.0 and deprecated in 2.6 (2.6-202204), where it remains only as a deprecated table entry.
Field facts
- Path
device.didmd5- Object
- Device
- Type
- string
- Requirement
- Optional
- Added
- OpenRTB 2.0
- Deprecated
- OpenRTB 2.6-202204
- Spec section
- 3.2.18
How it is used
The 2.0 definition asked for the IMEI, or the MEID or ESN when no IMEI existed, hashed and read case-insensitively. Mobile operating systems stopped giving apps access to hardware IDs years ago, and an MD5 of an IMEI is easy to reverse, so there is no sound source for this value today. Use device.ifa for the platform advertising ID and user.eids for other identity.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"device": {
"didmd5": "0f0e0d0c0b0a09080706050403020100"
}
}Common mistakes
- Still filling it from a legacy SDK. On 2.6 the validator reports it as deprecated, and buyers ignore it.
Version history
Added in OpenRTB 2.0, deprecated in 2.6-202204, and present in the latest snapshot. The table shows how each version's spec text types the field.
| Versions | Type in the spec | Required | Deprecated |
|---|---|---|---|
| 2.0 to 2.2 | string | No | No |
| 2.3 to 2.3.1 | string | No | No |
| 2.4 | string | No | No |
| 2.5 | string | No | No |
| 2.6-202210 to 2.6-202606 | string | No | Yes |
Versioned rules that name this field
openrtb.2.6.deprecated_fieldsOpenRTB 2.6 deprecated legacy sequence, device-ID hash, demographic, and single-api fields.