9 November 2025

GPP notes for UK measurement teams

The Global Privacy Platform is a transport. It is not a taxonomy. GB teams sometimes copy a GPP string into every event and declare the stack “consent aware”. The warehouse still cannot answer whether analytics was allowed at fire time, because the string was attached after the hit, or because a vendor mapped sections incorrectly.

Read the sections you actually configure. If your CMP emits a UK-relevant signal, persist that signal beside the event, then translate it into your own enum: granted, denied, unknown, withdrawn. Do not query raw strings in Looker. Analysts will invent mappings at 17:30 on a Friday.

GPP also does not settle PECR storage questions. A well-formed privacy string with a poorly argued “strictly necessary” cookie is still a poorly argued cookie. Keep counsel in the loop; our courses are practitioner studios, not a substitute for that conversation.

Where GPP helps is vendor interoperability: ad tech that already speaks the same sections. Where it fails is first-party product analytics that never needed those sections and now inherits their complexity. If you only measure your own site, a small internal snapshot may be clearer than dragging the whole string into BigQuery “just in case”.

We map CMP outputs to warehouse columns in the lab listed on the courses page. Bring a redacted example string; we will not debug your live ads account in class.