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

Clarification on Mobile Key Names #20

Open
thegreatfatzby opened this issue Nov 16, 2022 · 1 comment
Open

Clarification on Mobile Key Names #20

thegreatfatzby opened this issue Nov 16, 2022 · 1 comment

Comments

@thegreatfatzby
Copy link

Want to make sure I'm understanding correctly: the "IABGPP_HDR_GppString" key says it is the "full consent string", but the "HDR" portion of the key name threw me as I would have thought "HDR" indicates a piece of the GPP string header section...is that value (the value keyed by IABGPP_HDR_GppString) intended to be the entire GPP string, including full header and the user consent sections, or is it a fragment I'm not quite understanding?

Also, less of an issue but curious: is it intentional that the IABGPP_GppSID mobile storage value is underscore separated "2_3" whereas GPP_SID is comma-separated when passed in requests.

@janwinkler
Copy link

HDR: Yes its the full string including all sections. the HDR is a bit missleading but at the end its just supposed to be a starting point (needs to distinguish from the other sections).

GppSID: since the comma is not URL-safe I'd also prefer to use the underscore in the macro

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