Cookiebot (Usercentrics)
GTM template v4+ wiring, IAB TCF 2.x consent string handling, cross-domain consent state persistence, and the initialization timing issues that appear after a major Cookiebot version bump.
Implement Consent tracking ASAP
Experts in quick, accurate consent tracking. Implementation or fix delivered in 1 to 7 working days.
Fixed in 1 to 7 working days. Fixed-price scope confirmed within 24 hours.
You'll recognize at least one of these.
These are the patterns we see most often when a consent setup breaks.
- Tags stopped firing for new EU visitors after a Cookiebot, OneTrust, or Cookie Information update.
- Consent Mode v2 is installed but EU conversions are still missing from GA4 and Google Ads.
- EU traffic shows 30 to 60 percent lower conversion rates than identical campaigns in the US or UK.
- GTM Preview shows tags firing normally, but Meta and GA4 are not receiving the events in real sessions.
- Your CMP shows cookies being accepted, but the tracking tags do not respond.
- First-time visitors convert in your store or CRM but your ad platforms record nothing.
- California traffic underperforms identical campaigns in other states, with conversions quietly missing from your ad platforms.
- Visitors on Brave, Firefox, or a privacy extension (sending a Global Privacy Control signal) are not tracked at all.
The diagnosis
Four reasons consent tracking breaks.
They look different in the symptoms, but they share the same failure pattern: the consent or privacy signal never reaches the platforms that need it.
Consent Mode v2 requires exact GTM wiring.
The signal chain runs CMP → GTM → GA4 and Google Ads. Any misconfiguration in the consent initialization block — wrong trigger order, missing wait_for_update, wrong consent category mapping — and the signal never reaches the platform, even if the user clicked Accept.
CMP template updates silently break the integration.
Cookiebot, OneTrust, and Cookie Information each maintain their own GTM community templates and update them independently. A major version bump can change how consent signals are dispatched, breaking an integration that was working the day before with no visible error.
GTM Preview mode bypasses real consent state.
A tag that fires in GTM Preview is not evidence that it fires in production for real users. Preview mode ignores consent checks. The gap between tags firing in preview and tags firing in real EU sessions after consent is where most consent bugs hide.
US opt-out signals suppress your tags too.
A Global Privacy Control signal from a California shopper is treated as an opt-out of sale and sharing, so your ad pixels and CAPI are suppressed for that user, exactly like a declined EU banner. Most stacks were never configured to handle GPC deliberately, so the suppression is invisible and the lost conversions are never noticed.
Consent platforms
CMPs we work with cold.
We know how each of these platforms talks to GTM, and exactly where each one breaks. Not from documentation — from fixing it repeatedly.
OneTrust
OptanonActiveGroups parsing, Consent Mode v2 initialization via the OneTrust GTM template, consent category-to-Google-consent-type mapping, and the override scenarios that break during a preference center update.
Cookie Information
CI consent category mapping to Google consent types, initialization sequence and timing in GTM, and the specific ways the Cookie Information template interacts with GA4 and Google Ads consent signals.
TrueVault
US state privacy law configuration (CCPA, CPA, VCDPA), server-side consent validation, and the signal chain for stacks that use TrueVault alongside a Consent Mode v2 requirement for EU traffic.
What the fix includes.
End-to-end consent state audit.
We inspect the full signal chain — CMP output → GTM container → GA4, Google Ads, Meta, and any other destination in scope. We find exactly where the break is before touching anything.
Implementation and real-session validation.
We fix the break and validate the full consent-then-fire sequence in both EU consent and California opt-out conditions, not just GTM Preview. We confirm that conversions appear in your ad platforms before marking it complete.
Delivery in 1 to 7 working days.
Fixed-price scope confirmed within 24 hours. Includes a 7-day post-delivery revision window. If something breaks again within that window, we fix it at no additional charge.
Fix it this week.
Describe the symptom. We scope a fixed price within 24 hours and have it working within the week.
- Consent state audit across your full signal chain
- CMP-to-GTM signal chain repair
- Cross-platform validation: GA4, Google Ads, Meta, and others in scope
- Real-session validation in EU consent and California opt-out conditions, not just GTM Preview
- Delivery in 1 to 7 working days
- 7-day post-delivery revision window
Tell us what's broken and we'll scope a fixed price within 24 hours.
FAQ
Common questions about consent tracking fixes.
Almost always a wiring problem between the CMP and GTM, not the CMP itself. The most common cause is an initialization timing issue: GTM fires tags before the CMP has dispatched the consent signal, or the GTM consent initialization block is missing the correct trigger. The CMP looks fine on its own because it is. The break is in how GTM listens for and responds to it.
No. We are not lawyers and do not advise on data policy. We fix the technical execution of what your legal team has already scoped. Your cookie categories, consent duration, opt-out text, and legal language are not touched. If your lawyer defined which cookies require explicit consent, we make sure those tags fire exactly as specified — no more, no less.
Partially. Server-side tracking improves signal quality for users who have consented. It does not send events for users who have declined. Consent Mode modeling in GA4 and Google Ads can recover some of that signal statistically — but only if Consent Mode v2 is implemented correctly, which is typically what we're fixing here.
We run structured tests in real EU browser sessions before and after the fix, confirm the consent-then-fire sequence works end to end across every platform in scope, and compare EU conversion rates before and after. You'll see the change in your platforms within 24 to 48 hours of the fix going live. We do not mark it complete until the numbers confirm it.
We handle the technical tracking implementation only. We are not lawyers. We do not advise on privacy regulations, design your data policy, or review your cookie consent categories. What data you can collect, from which visitors, and under what legal basis — those are decisions for your legal team. Our job is to make sure the tracking technology executes exactly what they've already defined. Compliance is the client's responsibility. We make sure the tracking executes it correctly.
Scope is confirmed within 24 hours. The fix itself is delivered in 1 to 7 working days. If you have a hard deadline — a campaign launch, a product release — let us know in the form and we'll confirm whether expedited delivery is possible.
What clients say
Trusted by teams who run on the numbers
Tracking Health is led by John Bernal, Top Rated Plus on Upwork. Here is what clients say about working with him.
5.0
average rating
200+
verified reviews
US & Europe
clients
Since 2016
Collect the signals you're actually allowed to collect.
Tell us what broke and when. We scope a fixed-price fix within 24 hours and have it working within the week.
Other symptoms? See the full list.