What is the DSA extension in OpenRTB?
Answer
The DSA transparency extension carries EU Digital Services Act ad-transparency data through OpenRTB 2.x ext blocks. On the request, regs.ext.dsa holds dsarequired (0-3, whether a DSA object is required in the response), pubrender (whether the publisher renders the transparency info), datatopub, and a transparency array of domain plus dsaparams objects. On the response, the bid's ext.dsa holds behalf (on whose behalf the ad shows), paid (who paid), adrender, and its own transparency array. It is an IAB Tech Lab community extension, not part of the core 2.6 spec.
Go deeper
More questions on privacy, identity, supply chain, and versions
- How do I pass GDPR consent in an OpenRTB bid request? Set regs.gdpr to 1 when the request is subject to GDPR and put the TCF consent string in user.consent.
- How do I pass a GPP string in OpenRTB? Put the Global Privacy Platform consent string in regs.gpp and list the applicable section IDs in regs.gpp_sid.
- GPP vs us_privacy: which should I send? Send GPP (regs.gpp plus regs.gpp_sid) where your partners support it; the US Privacy signal was deprecated by IAB Tech Lab on January 31, 2024 in favor of GPP.
- How do I signal CCPA in OpenRTB? Put the US Privacy string in regs.us_privacy, which is a first-class field in OpenRTB 2.6; on 2.5 and earlier it travels as regs.ext.us_privacy per the IAB extension.
- How do I signal COPPA in an OpenRTB request? Set regs.coppa to 1 when the request is subject to the COPPA regulations established by the US FTC, and 0 when it is not.
- What is the difference between device.lmt and device.dnt? device.dnt is the browser Do Not Track header flag, while device.lmt is the OS-level Limit Ad Tracking signal from mobile platforms such as iOS and Android.
All 93 questions are listed in the OpenRTB FAQ.