10 recipes where the outcome is governance and compliance, each written out in the same seven boxes. The patterns they compose most often: audit trail generation at the decision point, consent state propagation across systems and consent-scoped signal collection.
Filter these further in browse.
Give the customer real control over what they receive on which channel, propagate the choice to every system that sends, and respect the jurisdictional defaults that say what each silence means
Measure consent rates as the trust signal they are, watch them for the slow degradation that surfaces when banners get heavier, jurisdictions tighten, or audiences shift, and catch the trend early enough to fix the upstream cause
Make the choice a visitor makes in the banner actually constrain what the server-side pipeline does with their data
Collect what the stated purpose needs, decide explicitly before each new field gets added, and treat the customer record as something curated rather than accumulated
Maintain a living inventory of every third-party tracker running on customer-facing surfaces, with the data each takes, the consent context it operates under, and the last-review timestamp that proves the inventory is current
Keep customers in legal hold, dispute, or vulnerability status out of every marketing channel, with the audit trail a regulator will ask for
A single consent record per user, mechanically propagated to every downstream system that activates against it
Carry the deletion request from the source system to every downstream destination holding the customer's data, including active campaigns, queued sends, and cleanroom audiences
Audit the personalization models for systematic bias in who they exclude, accelerate, or under-serve, so the model's behavior is defensible per protected category and per business-sensitive segment
Record why a particular customer saw a particular experience, in a form a regulator, an internal model reviewer, or the customer themselves can reconstruct months later