Regs.coppa

Flag for whether the request falls under the US Children's Online Privacy Protection Act rules enforced by the FTC: 0 means no, 1 means yes. Present since 2.2, when the object was still called Regulations.

CurrentintegerOptionalSince 2.3

Field facts

Path: regs.coppa
Object: Regs
Type: integer
Requirement: Optional
Added: OpenRTB 2.3
Spec section: 3.2.3

How it is used

When the flag is 1, the spec's implementation notes ask exchanges to strip or coarsen anything that could identify a child: persistent device and user IDs, precise latitude and longitude, and the low bits of the IP address. Buyers are expected to switch off behavioral targeting and retargeting for the impression, and campaigns that cannot run under COPPA should not bid.

Allowed values

0, 1.

Example

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

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

Common mistakes

Sending true instead of 1. The JSON field is an integer; the boolean form comes from protobuf-generated JSON (openrtb.dialect.bool_for_integer).
Setting the flag to 1 while still forwarding Device.ifa and precise geo defeats its purpose.

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	integer	No	No
2.4	integer	No	No
2.5 to 2.6-202606	integer	No	No