Device.dpidmd5

A platform device ID such as the Android ID, hashed with MD5. Present since OpenRTB 2.0 and deprecated in 2.6 (2.6-202204).

Deprecated since 2.6-202204stringOptionalSince 2.0

Field facts

Path: device.dpidmd5
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 text gave the Android ID and the iOS UDID as examples. Apple withdrew UDID access long ago and Android now scopes its ID per app, so the value no longer works as a cross-app identifier. Use device.ifa for the advertising ID.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "device": {
    "dpidmd5": "0f0e0d0c0b0a09080706050403020100"
  }
}

Common mistakes

Still sending it on 2.6 traffic. 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_fields OpenRTB 2.6 deprecated legacy sequence, device-ID hash, demographic, and single-api fields.