Check your Consent Mode v2 setup
Paste your consent default block and this checks that all four v2 signals are set — a banner predating v2 usually sets only ad_storage and analytics_storage, leaving ad_user_data and ad_personalization undefined, which Google treats conservatively rather than as granted. It also tells you plainly what it cannot check, which is the failure that actually causes most Consent Mode problems.
Free30 minutesNo obligation
Check your Consent Mode v2 setup
Paste your consent default block and this checks all four v2 signals are set — a banner predating v2 usually sets only two, leaving ad_user_data and ad_personalization undefined, which Google treats conservatively rather than as granted. It will also tell you plainly what it cannot check.
Paste your consent default block and press Check. Everything happens in your browser. Nothing is sent anywhere.
Consent checker · what breaks
What this tool is for — Consent checker
- 01
Conversions dropped after a banner install
And you want to know whether the config explains it.
- 02
You migrated to v2
And want the signals confirmed.
- 03
Compliance is asking what happens on denial
And nobody can answer.
Consent checker · the fix
What you get out of it — Consent checker
A per-signal verdict
All four checked by name.
Default and wait_for_update checks
The two structural elements.
An explicit statement of the limits
Including the failure it can't see.
Consent checker · architecture
Why the most common Consent Mode failure is invisible here
A snippet can be perfectly configured and completely ineffective, and this tool says so rather than implying otherwise.
- 1
Order beats configuration
A default consent command that runs after the tag it was meant to gate has already lost. The configuration looks correct and the outcome is wrong.
- 2
Undefined is not granted
A signal you never set is treated conservatively by Google, which is why a v1-era banner silently under-reports on v2.
- 3
The banner reports its own state
Not what left the browser. Those are different things and only one of them is checkable.
- 4
Category assignment is a separate trap
A conversion tag filed under marketing is blocked by anyone who accepted analytics only.
Consent checker · diagnose
What this tool cannot tell you — Consent checker
Stated up front, because a tool that implies more confidence than it has is worse than no tool. These are checks you have to run yourself.
- 01
Execution order
The single most common failure, and completely invisible in a pasted snippet. Deny consent and watch the network tab.
- 02
What actually leaves the browser
Configuration is not evidence. Only a network capture is.
- 03
Which tags are in which consent category
That's container configuration, not a consent snippet.
- 04
Whether your position is legally defensible
That's your counsel's call. We implement, we don't advise on it.
Consent checker · prove
How to confirm the result — Consent checker
Against your own records, not against the tool's output.
Source of truth
outbound network requests captured under each consent state
- All four signals confirmed set on a live page.
- Default confirmed executing before any measurement tag.
- Denial verified by capture — nothing carrying identifiers leaves.
- Each state tested individually, including partial and undecided.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked after your next site release, which is when most breaks happen.
Consent checker · free audit
What we check in the free audit
- Execution order
- What actually leaves the browser
- Which tags are in which consent category
- Whether your position is legally defensible
Checked against
outbound network requests captured under each consent state
Free30 minutesNo obligation
Consent checker · when not to buy
Why this isn't gated — Consent checker
There's no email form in front of it, and that's deliberate.
- A tool you have to pay for with your contact details is a lead form wearing a costume. If this is useful, it should be useful without a transaction.
- Everything it does runs in your browser. There is no endpoint, so there is nothing for us to collect even if we wanted to — open your network tab and check.
- It will tell you when you don't have a problem. That outcome costs us a sale and happens regularly, which is the point of publishing it rather than putting it behind a call.
- If it does find something and you'd rather fix it yourself, the reference pages on this site cover the how. Hiring us is one option, not the conclusion.
Consent checker · what we deliver
What it checks
All four v2 signals
ad_storage, ad_user_data, ad_personalization, analytics_storage.
A default command
Whether the pre-choice state is set explicitly at all.
wait_for_update
Whether an asynchronous banner has time to report a choice.
Default-to-granted
Flagged as a legal position rather than a technical setting.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
If the tool found something and you'd rather not fix it yourself: we repair the root cause in your existing setup and verify it on a live conversion.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than the instance. Money events from your own records through a first-party container on your subdomain.
- First-party server container on your own subdomain
- Events from your 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, with monitoring so the next break surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Consent checker questions, answered
ad_storage, ad_user_data, ad_personalization and analytics_storage. A banner setting only the first and last leaves the v2 pair undefined.
Because it can only read what you paste. The most common failure is execution order, which is invisible in a snippet — deny consent and check the network tab instead.
That's a legal position for your counsel, not a technical preference. We implement whichever you choose and won't advise on which.
Roughly your denial rate. Much more than that means consented visitors are also being blocked, and that part is fixable.
Free · 30 min
Get consent verified by capture, not configuration
WhatsAppFree30 minutesNo obligation
