Device.dnt

The browser's Do Not Track flag, taken from the DNT request header, where 0 means tracking is unrestricted and 1 means the user turned on Do Not Track. Recommended.

CurrentintegerRecommendedSince 2.0

Field facts

Path: device.dnt
Object: Device
Type: integer
Requirement: Recommended
Added: OpenRTB 2.0
Spec section: 3.2.18

How it is used

Do Not Track is a browser preference, not a legal consent signal, and several browsers have removed the setting, so many requests omit it or send 0 for everyone. When it is 1, the conservative reading is no behavioral targeting or cross-site tracking for that impression. It is separate from device.lmt, which comes from a mobile OS, and from consent strings in user.consent and regs.gpp. Global Privacy Control has no field of its own and usually reaches buyers inside the GPP string.

Allowed values

0, 1.

Example

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

{
  "id": "req-1",
  "device": {
    "dnt": 0
  }
}

Common mistakes

Sending true or false. The field is an integer flag, and a spec JSON reader rejects a boolean.
Sending 1 alongside a live device.ifa or populated user.eids. RTBlint reports that combination as a privacy signal contradiction.

Version history

Added in OpenRTB 2.0, 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	Integer	Recommended	No
2.3 to 2.3.1	integer	Recommended	No
2.4	integer	Recommended	No
2.5 to 2.6-202606	integer	Recommended	No