User.ext

Exchange-specific extensions for the user. Before OpenRTB 2.6, the TCF consent string and extended IDs commonly lived here as consent and eids; 2.6 made both first-class fields.

CurrentobjectOptionalSince 2.1

Field facts

Path: user.ext
Object: User
Type: object
Requirement: Optional
Added: OpenRTB 2.1
Spec section: 3.2.20

How it is used

During migration some senders write both paths. Keep the values identical and drop the extension copy once partners read the 2.6 fields. RTBlint reports a conflict when the two consent values differ.

Example

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

{
  "id": "req-1",
  "user": {
    "ext": {}
  }
}

Version history

Added in OpenRTB 2.1, 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.1 to 2.2	object	No	No
2.3 to 2.3.1	object	No	No
2.4	object	No	No
2.5 to 2.6-202606	object	No	No

Related fields

Other User fields

For a walkthrough of the whole object, read User identity and EIDs.