Consent Mode v2, implemented in the right order and scoped to the right regions
Most Consent Mode implementations fail in one of two directions: tags fire before the defaults are declared, which is both a compliance problem and the reason modelling never works, or an EU-style prior-consent banner is applied to every visitor regardless of jurisdiction, discarding conversions no law asked you to discard. We fix the order of operations, scope by region, wire all four signals, and prove it with a network log from a clean profile.
Free30 minutesNo obligation
Consent Mode v2 · what breaks
Where consent implementations go wrong
- 01
Conversions fell after the banner and never recovered
Where modelling should have restored part of the gap.
- 02
Tags firing before the visitor chooses
Visible in the network tab, and hard to defend in a review.
- 03
Modelled conversions never appearing
Which usually means the signals aren't reaching Google, not that volume is low.
- 04
US traffic treated like EU traffic
The most expensive misconfiguration we find, and the most common.
Consent Mode v2 · the fix
What you get out of it — Consent Mode v2
Nothing fires before consent
Verified per destination on a clean profile, not asserted.
Only legally required data is lost
Region-scoped, so you stop over-blocking.
Modelling works
Which requires correct signals to function at all.
Evidence you can hand to counsel
A network log, not a claim.
Consent Mode v2 · architecture
Why the numbers were wrong before you got here — Consent Mode v2
Worth understanding before buying anything, because it decides which tier you need — and for some readers the answer is that you don't need us yet.
- 1
The browser is the weakest link, and it is getting weaker on purpose
Every browser-side tag has to survive the page loading, the visitor staying, the script running and the request leaving. All four are now contested. The order in your database is certain; the browser event reporting it is not.
- 2
Safari caps the cookie your attribution depends on
Intelligent Tracking Prevention limits JavaScript-set cookies to seven days whatever expiry you set, so a customer who takes longer than a week to decide returns as a stranger. A cookie your own server writes in an HTTP response is not capped — the single largest practical difference between browser-side and first-party server-side.
- 3
Ad blockers remove the tag with no error
A blocked pixel does not warn anyone. The customer buys, the order lands, and no platform hears about it. First-party events from your own subdomain are not a third-party request and are not filtered the same way.
- 4
Consent is enforced by hope, not by architecture
Client-side consent means trusting each vendor script to honour a flag. A server container decides at the container: a denied destination receives nothing. That is a materially stronger position, and it also stops the over-blocking that discards data no law required losing.
- 5
Checkout can end where your tag isn't
Wallets and hosted payment pages can be abandoned after the money moves. Sending the purchase from the order record means it arrives whether or not anyone came back.
Consent Mode v2 · diagnose
How we scope the consent mode v2 build
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Clean-profile load, watch request order
Anything firing before the default is a finding.
- 02
Check region configuration
Is prior consent demanded of visitors whose jurisdiction never required it?
- 03
Confirm all four signals exist
In both the default and the update.
- 04
Deny consent and check each destination
Blocking one and not another is common.
- 05
Confirm the update fires on acceptance
Previously-blocked tags should run, not stay blocked for the session.
- 06
Check whether the CMP itself can be blocked
An ad blocker stopping it leaves the page in its default state permanently.
Consent Mode v2 · prove
How the work gets proven — Consent Mode v2
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
Network request log on a clean browser profile
- No advertising or analytics request preceding the consent default declaration.
- With consent denied, no destination receiving an identifiable request — verified one at a time.
- With consent granted, every expected tag firing and the update visible in the log.
- Region scoping verified from at least two jurisdictions.
- Modelled conversions appearing in Google Ads and GA4.
- Reconciled over a fully closed window, matched on ID rather than on totals — totals hide equal and opposite errors.
- Payload evidence captured from real transactions, saved to your own records.
- The same reconciliation repeated 30 days later, because a setup that works once and drifts is the harder failure.
Consent Mode v2 · free audit
What we check in the free audit
- Clean-profile load, watch request order
- Check region configuration
- Confirm all four signals exist
- Deny consent and check each destination
- Confirm the update fires on acceptance
- Check whether the CMP itself can be blocked
Checked against
Network request log on a clean browser profile
Free30 minutesNo obligation
Consent Mode v2 · when not to buy
When you shouldn't buy this — Consent Mode v2
We would rather say it now than three weeks into an engagement.
- You have no European, UK or Swiss traffic and no state-privacy exposure — though confirm that with counsel rather than assuming it.
- Your CMP is a certified Google partner and its integration already fires in the right order. Test it; some genuinely work.
- You run no Google advertising and no GA4. Consent Mode is a Google mechanism; your obligations may still exist but this specific work won't address them.
- You need legal advice on what your obligations are. We implement what your counsel decides. We are not lawyers and won't pretend to be.
Consent Mode v2 · what we deliver
What's included in the consent mode v2 build
Defaults declared before any tag
In the container's initialisation, ahead of everything else.
Region scoping
Prior consent where the law requires it, a different default where it doesn't.
All four signals wired
Including ad_user_data and ad_personalization, which v1-era setups almost always lack.
CMP integration verified
The update actually reaching the container, not just the banner closing.
Server-side enforcement
Where a server container exists, the decision applied at the container.
Evidence pack
Network logs from a clean profile, per destination, under denial and under grant.
Written guarantee
95%+ tracking accuracy
Measured against Network request log on a clean browser profile. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
The correct browser-side build, done properly and verified on a live transaction. Honest about its ceiling: it will not survive Safari's cookie cap, an ad blocker, or a checkout that ends somewhere your tag isn't. If you spend $1K+/month on paid media, start one tier up.
- Correct events, correct parameters, correct values
- Verified on a live transaction, not in preview
- Reconciled against your own order records
- Written handover you keep
1st-party server-side
Recommended$800One-time fee · most popular
The tier that changes the outcome rather than patching it. Your money events stop depending on the browser: they are sent from your order records through a first-party server container on your own subdomain, so iOS, ad blockers, consent banners and interrupted payment redirects can no longer take them away. Built in 2–4 days. You own the stack outright, with no monthly SaaS.
- First-party server container on your own subdomain
- Money events sent from your order records, not the browser
- Meta, Google, TikTok, Microsoft and LinkedIn all fed server-side
- Deduplicated on a shared event ID, verified at every destination
- First-party cookies beyond Safari's 7-day cap on JavaScript-set cookies
- 95%+ conversion accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel server-side, plus the offline loop that connects closed revenue back to the click. For advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop, so closed revenue reaches bidding
- Refunds and cancellations reversed at every destination
- Klaviyo identity stitching, BigQuery and Looker Studio
- Monitoring, so the next break surfaces in days rather than a quarter
FAQ
Consent Mode v2 questions, answered
No. It is a signalling mechanism. Compliance comes from law and your counsel's reading of it; Consent Mode is how you tell Google what the visitor chose.
Because US state privacy laws generally work on opt-out rather than prior consent. Applying an EU-style banner everywhere usually discards conversions no law required losing — often the largest single line in an audit.
The modelled portion usually does, because modelling needs correct signals to work. The genuinely consent-denied portion should not recover, and shouldn't.
Consent Mode is Google's mechanism, but the same decision should govern every destination. With a server container we enforce it once, in one place, for all of them.
Free · 30 min
Get consent implemented in the right order
WhatsAppFree30 minutesNo obligation
