InteractiveAdvertisingBureau
Propose a GPC extension to OpenRTB
Intended to address #98
This is intended to apply to any applicable RTB version and I'd be happy to add to this PR if needed to allow it to apply to other iterations if maintainers will tell me what needs to be done in order to do so. I do not believe my organization is currently a Tech Lab member, however, if there are any questions I'd be glad to speak to the group.
The goal is to support passing the Global Privacy Control signal to downstream participants in order to allow them to make decisions on how to interpret the privacy state of a user in regard to applicable regulations.
Downstream consumers of this signal should use it as the primary signal where they believe it applies, since not all publishers may use the signal to change their interpretation of other privacy signals or may interpret it the same way as a downstream consumer. So, where the downstream consumer of OpenRTB signals sees both a USPAPI signal and a GPC signal on a request and considers the GPC signal to mean an opt-out in California, and where the USPAPI signal does not indicate such an opt-out, then the downstream consumer should consider the user opted-out.
When the creator of the OpenRTB object sees a GPC signal they must set this extension with that signal.
Resolved the open comment. Mistake on my part. Let me know if there are any other questions.
Resolved the minor edits @patmmccann
Not sure what to do about the question of what an extension is intended to do / be used and where that should go? Is it that the detail is too high? Should it go somewhere else? I'm unclear on what the best place to put something like this is, but surely it needs to be someplace right?
I am not sure what the best forum to discuss this is, but I feel confident this is not it.
Perhaps: https://github.com/InteractiveAdvertisingBureau/USPrivacy/blob/master/CCPA/USP%20API.md
@AramZS you can email me directly ([email protected]) and I can put you in touch with the privacy working groups.
~We need a URL parameter for this field as well, for GET requests.~ Retract this comment, the HTTP header serves this purpose, there is no need for a URL parameter.
Since the GDPR and US Privacy signals are being promoted to the main specification in OpenRTB 2.6, I recommend we do the same for this one.
Putting the prebid link that was on #98 here too
https://github.com/prebid/Prebid.js/issues/8424
Prebid implemented this on regs.ext.gpc
I tried to contact the author, to help resolve these issues. This was unsuccessful, so I have created a new pull request #123 to move the discussion there, and will close #99.
Closing as dupe of https://github.com/InteractiveAdvertisingBureau/openrtb/pull/123
