You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like other existing privacy signals (TCF and USPrivacy), the GPP string is also able to be transported via OpenRTB. This will be included in the Regs object in the November 2022 release. See this document for approved design prior to release.
However, there is no actual reference to GPP anywhere to be found, so far as I can tell. There is increasing pressure to support GPP by Jan 1, 2023, but I can't find any official information on the OpenRTB implementation.
Can anyone confirm the specification for OpenRTB 2.5? From some past proposals and discussion, I've gathered:
regs.ext.gpp (GPP string)
regs.ext.gpp_sid (array of relevant section IDs)
The text was updated successfully, but these errors were encountered:
What you laid out is correct for 2.5, but we strongly encourage moving to 2.6 which would only require a change to the version number in the header and the inclusion of regs.gpp and regs.gpp_sid. Hope that helps clarify!
This document references the OpenRTB extensions in this repo:
However, there is no actual reference to GPP anywhere to be found, so far as I can tell. There is increasing pressure to support GPP by Jan 1, 2023, but I can't find any official information on the OpenRTB implementation.
Can anyone confirm the specification for OpenRTB 2.5? From some past proposals and discussion, I've gathered:
regs.ext.gpp (GPP string)
regs.ext.gpp_sid (array of relevant section IDs)
The text was updated successfully, but these errors were encountered: