Method
Consent-Aware Analytics Design as a sequence, not a banner ticket.
Teams treat the CMP as a legal leftover. We treat it as the first object in the measurement system. Everything downstream — events, warehouse columns, experiments, board packs — inherits a consent snapshot or it is labelled as uncovered.
Five artefacts
Prompt inventory. Every surface that can collect storage or tracking, including forgotten pixels on campaign landing pages.
State machine. Unknown, granted, denied, withdrawn — with time. A grant at 00:12 does not rewrite 00:11.
Split dictionaries. Essential operational telemetry stays out of the analytics schema so reject traffic is not “filled in” with lookalikes.
Fallback set. Counts that survive reject without minting identifiers: coarse page groups, server 200s, explicit first-party forms.
Coverage narrative. Dashboards that print the share of traffic sitting in each state. Executives may dislike the hole; they should still see it.
Where GB teams get stuck
Agencies still promise “full funnel visibility” on pitches. In-house analysts inherit that promise. Consent-Aware Analytics Design is the practice of writing down what remains after a lawful no, then teaching the organisation to plan product work against that remainder.
The sequence is taught in Consent Signal Architecture. If you already have a taxonomy that fires too early, bring it to the course index or write to the desk.