← all work

Tracking, Analytics & Compliance

A compliance-critical tracking rebuild, shipped with zero incidents

Led the decoupling and rebuild of a Google Tag Manager / Segment setup for Consent Mode v2 and GDPR/DMA compliance — delivered ahead of schedule with zero tracking incidents.

B2B SaaS · GDPR / DMA exposure

0

Tracking incidents

Ahead of

Schedule delivered

Consent Mode v2

GDPR / DMA compliant

Context

A regulatory deadline put the company’s tracking on a clock. Consent Mode v2 and tightening GDPR/DMA obligations required the Google Tag Manager and Segment implementation to be re-architected — and the existing setup was entangled enough that a careless change risked breaking measurement everywhere.

The problem

Compliance work like this is high-stakes and low-glory: do it wrong and you either violate privacy rules or blind your analytics and ad optimization. It had to ship on a deadline, decouple tightly coupled systems, and not cause a single tracking incident along the way.

What I built

A decoupled tracking architecture with consent enforced correctly at the source. Tags and data flows were untangled and rebuilt so consented data is captured cleanly and consent state governs everything downstream — Consent Mode v2 wired in properly rather than bolted on. The work was sequenced to keep measurement live throughout the migration.

The result

The rebuild shipped ahead of schedule with zero tracking incidents — compliant with Consent Mode v2 and GDPR/DMA, with analytics and ad-platform signal intact. No quiet data outage, no scramble.

What this means for you

Privacy compliance and good measurement are not a trade-off when the tracking is architected properly. Decouple consent from collection and you can satisfy regulators without going dark.

Stack

Google Tag ManagerSegmentConsent Mode v2GA4

Have a problem that looks like this?

If any of this sounds like your stack, let's talk about what I'd do for you.