Ship a consent banner that doesn't tank your data

Ship a consent banner that doesn't tank your data
The implementation checklist between legal and analytics.

1 — Wire your tag manager to fire on consent events, not page load.
Why: tags that fire before consent are exactly the violation the banner was meant to prevent.

2 — Map every tag to a consent category in one table before you touch the banner.
Why: an uncategorized tag defaults to blocked or leaks, and both are bugs.

3 — Test the 'reject all' path as hard as the 'accept all' path.
Why: most teams QA the happy path and ship a reject button that does nothing.

4 — Implement consent mode so blocked tags still send modeled signals.
Why: it recovers a chunk of the conversions a hard block would erase.

5 — Log consent rate by region weekly.
Why: a sudden drop usually means a banner bug, not a behavior change.

That's the stack for this week. Forward to a teammate.