Regs.gpp_sid

The GPP section IDs that apply to this transaction, as an integer array. It usually holds one value, such as 2 for TCF EU or 7 for the US national section. Added in 2.6-202211 together with Regs.gpp.

Currentinteger arrayOptionalSince 2.6-202211

Field facts

Path: regs.gpp_sid
Object: Regs
Type: integer array
Requirement: Optional
Added: OpenRTB 2.6-202211
Spec section: 3.2.3

How it is used

Section 3 (the header) and section 4 (signal integrity) never need to be listed. Every ID here should also appear in the string's header, and the validator decodes the header to compare the two. More than one value is allowed for the edge cases where several jurisdictions apply at once.

Example

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

{
  "id": "req-1",
  "regs": {
    "gpp_sid": [
      7
    ]
  }
}

Common mistakes

Sending gpp_sid with no gpp string (openrtb.regs.gpp_sid_without_gpp).
Listing an ID the header does not contain (openrtb.regs.gpp_section_mismatch), or listing 3, which is the header itself.
Sending a single integer or a comma-separated string instead of an array.

Version history

Added in OpenRTB 2.6-202211, 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.6-202211 to 2.6-202606	integer array	No	No

Versioned rules that name this field

openrtb.2.6-202211.regs.gpp OpenRTB 2.6-202211 added GPP consent signaling to the regs object.

Related fields

Other Regs fields

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