Every few weeks someone tells me consent management “destroyed their data.” Then I open their site and find the real culprit: the cookie banner loads last, half the tags load outside the tag manager entirely, and a well-intentioned blocking rule is holding conversion tags hostage for twenty seconds. Consent didn’t kill their data. Sequencing did.

Consent problems are almost always order-of-operations problems, and the fix is a strict load order:

1. Consent platform first

Before anything else, with region-correct defaults. EU visitors get EU rules, US visitors get US rules, and nothing fires until the platform has set the default state. A banner that loads after your pixels is just decoration.

2. Customer data infrastructure second

If you run a CDP or server-side collection, it loads with consent state stamped onto every event, and destination categories enforce what each downstream tool is allowed to receive. Compliance stops being a promise and becomes architecture.

3. Tag manager last

GTM loads with Consent Mode wired in, so Google’s tags behave according to the user’s choice, and modeling fills the statistical gaps for declined users. Your ad optimization keeps working; your lawyers keep smiling.

The surprise ending

Do it in this order and something wonderful happens: your data gets better. No more tags racing the banner, no more mystery gaps, no more delayed conversions silently dying when users navigate away. Compliance isn’t a tax on marketing. Done right, it’s a cleanup crew.

If your regional revenue reporting ever “went dark” after a consent vendor switch, that’s this. It’s fixable without breaking a single rule.