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

GPP consent string received but downstream requesting EU TCF macro #77

Open
garylonghalds opened this issue Jun 1, 2023 · 1 comment

Comments

@garylonghalds
Copy link

garylonghalds commented Jun 1, 2023

In EU, we are facing cases where we either receive either GPP or EU TCF string (and some rare occasions both) from upstream. Our downstream partners raise request via macros for either GPP or EU TCF string.

  1. Is there any guidance on what to do for cases when we have received only a GPP string from a publisher/CMP but the downstream partners are using a EU TCF Macro
  2. The vice versa usecase where we receive only a EU TCF string but received request for consent strings via a GPP Macro?
@janwinkler
Copy link

in theorie you can convert them 1:1 but at least from TCF policy it states that only a CMP should create tc strings. hence the only way out here would be to always receive/send both

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

2 participants