Repairing tracking that a consent banner quietly broke
A consent banner installation is the single most common date on which conversion tracking breaks, and it fails in two opposite directions at once: blocking data from visitors who granted consent, and permitting data from visitors who denied it. Both come from the same root — the banner's configuration and the actual execution order on the page are different things. The repair is almost entirely verification: capture what leaves under each consent state and compare it against what should.
Free30 minutesNo obligation
Consent banner repair · what breaks
The situation, as it usually presents — Consent banner repair
- 01
A conversion drop dated to the banner install
The signature.
- 02
Consent rate high but conversions still down
Which points at execution, not choice.
- 03
Nobody able to state what denial does
Risk in both directions.
Consent banner repair · the fix
What changes — Consent banner repair
Consented visitors measured
They were being blocked.
Denied visitors not measured
They were being sent.
Behaviour verified by capture
Not read off a settings screen.
Consent banner repair · architecture
Why this pattern keeps recurring — Consent banner repair
Consent banners break tracking for reasons that are about sequencing rather than about consent, which is why the settings screen looks fine.
- 1
Order beats configuration
A default that fires after the tag it gates has already lost. The configuration is correct and the outcome is wrong.
- 2
Tags land in the wrong category
A conversion tag filed under marketing gets blocked by a visitor who accepted analytics only — often more visitors than expected.
- 3
The banner reports its own state
Not what left the browser. Only a network capture shows the second thing.
- 4
Undecided is a third state
Visitors who never choose are neither granted nor denied, and many implementations never define what happens to them.
Consent banner repair · diagnose
How the root cause gets found — Consent banner repair
In this order. Each step rules out a class of cause, so the last one usually has a single explanation standing.
- 01
Compare conversions against the install date
The drop is usually clean.
- 02
Capture network traffic in all four states
Undecided, accept, reject, partial.
- 03
Check what executes first in the document
The most common cause.
- 04
Review category assignment per tag
The second most common.
- 05
Compare the drop size to the denial rate
A mismatch means consented visitors are blocked.
Consent banner repair · prove
How the work is proven — Consent banner repair
Against the client's own records, not a dashboard turning green.
Source of truth
Outbound network requests captured under each consent state
- All four consent states tested by capture.
- Default confirmed executing before any measurement tag.
- Denial verified — nothing with identifiers leaves.
- Conversion volume compared against the denial rate to confirm consented traffic is measured.
- Reconciled over a fully closed window, matched on ID rather than on totals.
- Payload evidence captured from real transactions and handed over.
- The same reconciliation repeated 30 days later.
Consent banner repair · free audit
What we check in the free audit
- Compare conversions against the install date
- Capture network traffic in all four states
- Check what executes first in the document
- Review category assignment per tag
- Compare the drop size to the denial rate
Checked against
Outbound network requests captured under each consent state
Free30 minutesNo obligation
Consent banner repair · when not to buy
Why there are no client numbers on this page — Consent banner repair
Most agency case studies lead with a percentage. This one doesn't, and the reason is worth stating.
- We don't publish client results we can't substantiate. An audit of this site in August 2026 found named testimonials and before-and-after figures that had never been measured — all of it was removed, and nothing has replaced it that isn't checkable.
- The results that do exist belong to clients under agreement. Publishing anonymised numbers without their sign-off would be the same problem in a thinner disguise.
- What we will commit to in writing is 95%+ conversion accuracy and 8+ Meta Event Match Quality, reconciled against your own order records. That is checkable by you, which a case study percentage never is.
- For proof from actual clients, the video testimonials on the site are real people describing their own rebuild. That is the strongest evidence we have, and it isn't a number we wrote.
Consent banner repair · what we deliver
What the work involves — Consent banner repair
Execution order established
What runs before what, in the document.
Each consent state captured
Undecided, granted, denied, partial.
Category mapping corrected
Tags in the wrong bucket are the second cause.
Findings documented for compliance
So the position is reviewable.
Written guarantee
95%+ tracking accuracy
Measured against Outbound network requests captured under each consent state. 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
Repairs the fault in your existing browser-side setup and verifies it on a live transaction. Honest about its ceiling: it fixes this instance, not the class.
- Root cause fixed, not worked around
- Verified on a live transaction
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than this instance. Money events sent from your order records through a first-party container on your own subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your order records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, 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
- Refunds reversed at every destination
- Monitoring so the next break surfaces in days
FAQ
Consent banner repair questions, answered
Roughly your denial rate. If conversions fell far more than that, the banner is also blocking people who consented, and that part is fixable.
Not if you serve the EEA or UK, where Google requires consent signals. In the US, CCPA and CPRA impose their own opt-out obligations. That's a legal call, not a tracking one.
Because analytics and marketing categories are gated separately, and the conversion tags are usually in the stricter one.
Deny consent, open the network tab, and look for outbound requests carrying identifiers. If they're there, the banner isn't doing what its dashboard says.
Free · 30 min
Find out what your banner is really doing
WhatsAppFree30 minutesNo obligation
