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
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: