Consent-based tracking analytics starts from a blunt sentence: if a person has not agreed to a purpose, you do not measure that purpose. The banner is not a courtesy. It is the boundary of the dataset.
Most leaks we see in Bangkok retail and travel stacks are not sophisticated. A thank-you page fires purchase to three ad platforms regardless of CMP state. A “pending” value is mapped to accept because someone wanted the tag to “still work during the animation.” A server container forwards the same hit the browser was blocked from sending. None of this is a grey area. It is collection without the basis you claimed.
The number that falls is not a defect
When reject is honoured, opted-in purchase will usually sit below the old vanity total. Product will ask whether the implementation is broken. Media will ask whether the CMP is “too aggressive.” Finance will ask why ROAS moved. Your job, if you sit in analytics, is to arrive with a written limitation before that meeting — not after the pixels have been quietly restored.
In Consent Measurement Studio we make learners draft that note in week five. It names the purposes, the expected drop range based on their own banner rates, and the reports that should no longer be compared to the pre-CMP era. The note is uncomfortable. That is its function.
Waiting is not yes
A surprising number of containers treat “CMP not yet returned” as a green light. The person is still reading. The overlay is still on screen. Identifiers are already gone. If your debug capture shows hits in that window, you do not have consent-based tracking. You have a race.
Fixing the race is unglamorous: hold non-essential tags until a grant event, fail closed on timeout, and never default pending to accept. We spend a full clinic on this because it is where most “we installed a CMP” projects still fail.
What we will not help you do
We will not design a “soft reject” that still sends hashed emails. We will not teach you to recreate a fingerprint from first-party fields the person never agreed to share for advertising. We will not call modelled conversions a substitute for honouring a choice. Modelling may exist in a vendor’s UI. It does not rewrite PDPA.
If your organisation cannot live with a smaller, lawful number, the problem is not the tag map. It is the incentive. The studio can only make that visible.