GPP String
Within the IAB Global Privacy Protocol (GPP) framework, end-user consent selections are encapsulated and encoded in the GPP String (gppString). This compact HTTP-transferable string can be used to communicate the end-user's consent selections to downstream ad tech partners. In this article, we will cover how to:
Retrieve GPP String
An end-user's GPP String can be retrieved by utilizing the ping command that comes standard with the __gpp function in the IAB Global Privacy Protocol (GPP) API. If the command is successful, the command will return the PingReturn object that will include (among other information) the end-user's gppString. See below for examples:
__gpp('ping', (pingReturn, success) => {console.log('Ping request was successful: ' + success); console.log('gppString: ' + pingReturn.gppString);});
Decode GPP String
Once your organization has retrieved an end-user's GPP String, leverage the IAB GPP Encoder/Decoder to decode the string by inputting the gppString value into the provided field and clicking Decode.
The decoded GPP String will populate in the JSON tab and include details for the section(s) enabled in the gppString .
The details included in any given section is dependent on the section. Please visit our resources for the national and state sections of the gppString.
Last updated