Regs.ext

Extensions to Regs. Before 2.6 this is where the GDPR and US Privacy signals traveled, as regs.ext.gdpr and regs.ext.us_privacy, and the DSA transparency extension still uses regs.ext.dsa.

CurrentobjectOptionalSince 2.3

Field facts

Path: regs.ext
Object: Regs
Type: object
Requirement: Optional
Added: OpenRTB 2.3
Spec section: 3.2.3

How it is used

On 2.6 requests, move the promoted signals to their core fields. A leftover copy under ext invites conflicts: when the core and legacy values differ, the validator reports it rather than choosing one.

Example

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

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

Common mistakes

Keeping regs.ext.gdpr as the only GDPR signal on a 2.6 request. The validator reports it as moved.

Version history

Added in OpenRTB 2.3, 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.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 Regs fields

For a walkthrough of the whole object, read Privacy signals.