search

InteractiveAdvertisingBureau / Global-Privacy-Platform

IAB Tech Lab Global Privacy Platform specification
72 stars 36 forks source link

In-App key names clarifications #89

Open lrNegovan opened 1 year ago

lrNegovan commented 1 year ago

Kind regards,

as an 3rd party SDK, I would like to read consent signals for mobile without decoding GPP string.

Is that possible, without implementing CMP library? What is the best practice(if you can provide an example) for 3rd parties when reading the consent for the US national/country segments. And could you clarify more on which is the key format inside SharedPreferences/UserDefaults?

If I understand specification correctly, we should be able to read every encoded GPP string component separately from SharedPrefs/UserDefaults? For example, for Utah: IABGPP_11_SaleOptOut - value

janwinkler commented 1 year ago

The naming in the spec is not really clear. The first paragraph says the naming is IABGPP_2_String while the example table below says IABGPPTCFEU2.... Anyhow, the second table seems incorrect (also it is missing the "v" in "IABTCFV2"), hence I'd assume that you should find the data in "IABGPP_11_SaleOptOut" (that's how our SDK is creating it)