Regulation Object¶

Regulation Object Properties¶
Value	Type	Description
coppa	integer	Flag indicating whether or not this request falls under the COPPA regulations established by the USA FTC: `0` = No. `1` = Yes.
ext*	object	See the Regs Ext Object

Regs Ext Object¶

Regs Ext Object Properties¶
Value	Type	Description
gdpr*	integer	Indicates whether the request falls under GDPR regulations: `0` = No `1` = Yes Under OpenRTB conventions for optional attributes, omission indicates Unknown If consent is given, you should check if the `user.ext.consent` field is present to ascertain what form of consent was given, see the User Ext Object section
us_privacy*	string	Passes the user privacy status for requests which fall under CCPA regulations. The string uses 4 characters, e.g. `"1YN-"`, passed in the following order. Version Number The IAB CCPA Specification version that applies to this string, passed as an integer. Currently only `1` is available. Explicit Notice (`N` = No, `Y` = Yes, `-` = Not Applicable) Indicates whether explicit notice has been provided to the user as required by 1798.115 (d) of the CCPA and whether they have had the opportunity to opt-out of the sale of their data pursuant to 1798.120 and 1798.135 of the CCPA. Opted-Out (`N` = No, `Y` = Yes, `-` = Not Applicable) Indicates whether the user has opted-out of the sale of their personal information pursuant to 1798.120 and 1798.135. LSPA (`N` = No, `Y` = Yes, `-` = Not Applicable) Indicates whether the publisher is a signatory to the IAB Limited Service Provider Agreement (LSPA) and that the publisher declares the transaction should be treated as a “Covered Opt Out Transaction” or a “Non Opt Out Transaction” as defined in the agreement.
dsa*	object	Extension for the Digital Services Act (DSA) transparency information

Regs Ext DSA Object¶

Regs Ext DSA Object Properties¶
Value	Type	Description
dsarequired*	integer	Flag to indicate if DSA information should be made available. This will signal if the bid request belongs to an Online Platform/VLOP, such that a Buyer should respond with DSA Transparency information based on the pubrender value. `0`: Not required `1`: Supported, bid responses with or without DSA object will be accepted `2`: Required, bid responses without DSA object will not be accepted `3`: Required, bid responses without DSA object will not be accepted, Publisher is an Online Platform
pubrender*	integer	Flag to indicate if the publisher will render the DSA Transparency info. This will signal if the publisher is able to and intends to render an icon or other appropriate user-facing symbol and display the DSA transparency info to the end user. `0`: Publisher can’t render `1`: Publisher could render depending on adrender `2`: Publisher will render
datatopub*	integer	Independent of `regs.ext.dsa.pubrender`, the publisher may need the transparency data for audit purposes. `0`: do not send transparency data `1`: optional to send transparency data `2`: send transparency data
transparency*	array of objects	Array of objects of the entities that applied user parameters and the parameters they applied.

Regs Ext Transparency Object¶

Regs Ext DSA Transparency Object Properties¶
Value	Type	Description
domain*	string	Domain of the entity that applied user parameters
dsaparams*	array of integers	Array for platform or sell-side use of any User Parameters (using the list provided by DSA Transparency Taskforce).

{
    "regs":{
        "ext":{
            "gdpr":1,
            "us_privacy":"1YN-",
            "dsa":{
                "dsarequired": 3,
                "pubrender": 0,
                "datatopub": 2,
                "transparency":[{
                    "domain": "platform1domain.com",
                    "dsaparams": [1,2]
                }]
            }
        }
    }
}

User Parameters¶

The definitions below are not meant to be consumer-facing messages.

ID	Parameter	Definition	TCF Purpose intends
1	Profiling	Information about the user, collected and used across contexts, that is about the user’s activity, interests, demographic information, or other characteristics.	TCF Purposes 4
2	Basic advertising	Use of real-time information about the context in which the ad will be shown, to show the ad, including information about the content and the device, such as: device type and capabilities, user agent, URL, IP address, non-precise geolocation data. Additionally, use of basic cross-context information not based on user behavior or user characteristics, for uses such as frequency capping, sequencing, brand safety, anti-fraud.	TCF Purpose 2
3	Precise geolocation	The precise real-time geolocation of the user, i.e. GPS coordinates within 500 meter radius precision.	TCF Special Feature 1