Regulations.coppa
Flag for whether the request is covered by the FTC rules under the US Children's Online Privacy Protection Act: 0 means no, 1 means yes. Introduced in 2.2 and carried forward unchanged as Regs.coppa.
Field facts
- Path
regs.coppa- Object
- Regulations
- Type
- integer
- Requirement
- Optional
- Added
- OpenRTB 2.2
- Last version
- OpenRTB 2.2
- Spec section
- 3.3.15
How it is used
The 2.2 implementation notes asked exchanges, when the flag is 1, to remove hashed device IDs, truncate IP addresses, drop latitude, longitude, city, metro, and ZIP code, and remove user IDs, year of birth, and gender. Buyers should not apply behavioral targeting to these impressions.
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 the flag as a string such as "1" is a type mismatch for an integer field.
Version history
Added in OpenRTB 2.2, last present in 2.2. The table shows how each version's spec text types the field.
| Versions | Type in the spec | Required | Deprecated |
|---|---|---|---|
| 2.2 | integer | No | No |
Versioned rules that name this field
openrtb.2.2.regs.coppaOpenRTB 2.2 added COPPA regulation signaling.
Related fields
Other Regulations fields
For a walkthrough of the whole object, read Privacy signals.