Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about inbound Open RTB fields for GPP #50

Closed
ym-corey opened this issue Jan 15, 2023 · 3 comments
Closed

Question about inbound Open RTB fields for GPP #50

ym-corey opened this issue Jan 15, 2023 · 3 comments

Comments

@ym-corey
Copy link

Where will the new GPP fields be located?

e.g.,

user.ext.gpp
user.ext.gpp_sid
user.ext.gpp_consent
regs.ext.gpp
regs.ext.gpp_sid
regs.ext.gpp_consent

If the GPP string contains sections other than what is specified in gpp_sid, are they applicable?

Thanks,
Corey

@janwinkler
Copy link

"GPP assumes the use of OpenRTB 2.x.

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](https://github.com/InteractiveAdvertisingBureau/openrtb/tree/master/extensions/community_extensions) for approved design prior to release."

@ym-corey
Copy link
Author

Hi @janwinkler , I don't see any reference to GPP in that repo, aside from another issue also pointing out that it is missing. InteractiveAdvertisingBureau/openrtb#114.

So we can expect to find either of these fields:

regs.gpp
regs.gpp_sid
regs.ext.gpp
regs.ext.gpp_sid

@patmmccann
Copy link
Contributor

https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md already specifies regs.gpp &
regs.gpp_sid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants