Consent Mode v2 checker
14 questions about your Consent Mode v2 setup.
- ad_storage
- analytics_storage
- ad_user_data
- ad_personalization
Short answer
The Consent Mode v2 Checker is a free self-audit of whether your consent signals reach Google. You answer 14 yes, no or not-sure questions and get a score out of 100 and a list of likely gaps, biggest first, each linked to a fix. It does not scan your website or read your Google accounts, it is not a legal compliance check, and your individual answers are not sent anywhere.
This Consent Mode v2 checker is a free self-audit. Answer yes, no or not sure for each check. You get a score out of 100 and a list of the likely gaps, biggest first, each linked to an article that explains the fix. No email, no sign-up, nothing is scanned and nothing is read from your site or your Google accounts.
Updated . Plain-text versions for tools and AI assistants: markdown and JSON spec.
Run the self-check
The note under each question says where to look: the page source, the Network tab, GA4 DebugView or your banner’s dashboard.
What the checker looks at
The questions follow the consent signal from your page to Google. Defaults and load order covers whether all four signals default to denied, whether that default loads above Tag Manager and gtag.js, and what the first request shows in its gcs parameter. Consent updates covers whether Accept sends an update, whether all four signals are present afterwards, whether banner categories map to the right signals and whether a refusal also sends an update. Banner and other tags covers the banner’s Google Consent Mode setting, the bridge to gtag and the other pixels on the site. Modeling and upkeep covers the repeat test after changes, the modeling status in GA4, the comparison with Google Ads conversions and the banner acceptance rate.
For the reasoning behind the checks, read Consent Mode v2 silently deletes GA4 conversions.
How the score is calculated
Each check has a weight of 1, 2 or 3. Checks that decide whether Google receives your consent state at all weigh the most. A “Yes” earns the full weight, “Not sure” earns half, “No” earns nothing. A check marked as not applicable is left out of both sides of the sum.
The checks with weight 3 are core checks: All four signals defaulted to denied; Accept sends a consent update (gcs G111); All four signals present after Accept. A “No” or “Not sure” on any of them keeps the result out of the top band, even when the score is 80 or higher, and the result names the core check to look at first.
The fix list is sorted by points lost, biggest first: a “No” loses the full weight of the check, a “Not sure” loses half of it. Checks that lose the same number of points keep the order of the table below.
Score = (sum of weights answered Yes + ½ × sum of weights answered Not sure) ÷ sum of weights of the applicable checks × 100, rounded to a whole number.
Worked example
A site whose banner calls gtag itself marks the bridge check as not applicable, which leaves 24 of the 25 points in play. The banner never sends the consent update after Accept, so “Accept sends a consent update” is No. Nobody repeats the 90-second test after changes, nobody has opened the modeling status in GA4 and nobody has compared the acceptance rate with the GA4 gap, so those three are Not sure. Everything else is Yes.
- Applicable weight: 25 − 1 = 24
- Lost: 3 + 1 + 0.5 + 0.5 = 5, so earned is 19
- Score: 19 ÷ 24 × 100 = 79.2, shown as 79
The fix list starts with the consent update, then the repeat test, the modeling status and the acceptance rate. The consent update is a core check, so the result names it as the first thing to fix. The band is 50 to 79.
How to read your result
- 80 to 100
- Solid on paper. The remaining items are tidy-up work. Re-run the check after any change to the banner, Tag Manager, the theme or the consent code.
- 50 to 79
- Gaps worth fixing. Some of the consent signals Google receives are partial or guessed. A failed or unconfirmed core check holds you here even with a score of 80 or more. Start with the first item in the fix list.
- 0 to 49
- Hard to trust. Fix the top items before you change budgets or optimization events, then run the check again.
These bands are our own cut-offs for deciding what to do next, not a benchmark. The order of the fix list matters more than the number itself.
What a self-check cannot see
Answers describe what you believe is set up. They cannot show a banner update that fires on one page and not on another, a signal that GA4 DebugView shows as denied, or traffic that ad blockers and browsers drop before it arrives. Run the 90-second test from our Consent Mode v2 article yourself. Our GA4 setup service and server-side tracking service pages explain what we set up around it.
For Google Ads and GA4 as a whole, run the Conversion Tracking Checker. For the Meta Pixel and Conversions API, run the Meta CAPI & Pixel Checker. For the GA4 property itself, run the GA4 Setup Checker. If you would rather have it checked inside the accounts, request a free conversion tracking audit of your banner, Tag Manager and GA4 setup.
Related checkers and guides
Questions about the checker
Does the Consent Mode v2 checker connect to my website or Google account?
No. It asks questions and scores your answers. Nothing is loaded from your site, your banner, Google Tag Manager or GA4, so the result is only as good as the answers. Each question has a short note on where to look: the page source, the Network tab, GA4 DebugView or your banner’s dashboard.
Why does “Not sure” count as half?
An unknown is not a confirmed failure, but it is not a pass either: nobody is watching that check. Half the weight keeps it visible in the score and on your list.
Is the score a benchmark against other sites?
No. The weights and the 80 and 50 thresholds are our own definitions, chosen to rank what matters most for whether the consent signals reach Google. They are not drawn from industry data, and the score does not compare you with anyone.
What happens to my answers?
They stay in your browser tab, are not sent anywhere, and disappear when you leave or start over. Our site analytics receives only an aggregate: that the check was started and finished, with the final score, the band and the number of gaps, and the score again if you click the audit link. The individual answers are never sent.
Why can a high score still stay in the middle band?
The three checks with weight 3 are the consent default for all four signals, the consent update that fires after Accept, and all four signals present after Accept. A No or a Not sure on any of them keeps the result out of the top band, even when the score is 80 or higher, because the rest of the setup cannot make up for signals that never reach Google. This rule is our own definition, like the weights and thresholds.
Where do the questions come from?
From our published article on the Consent Mode v2 gap between the banner and gtag, from the consent check in our Conversion Tracking Checker, and from Google’s own terms: ad_storage, analytics_storage, ad_user_data, ad_personalization, the gcs and gcd parameters and GA4 DebugView. Where our site gives no fact, the check is worded as an action to carry out, not as a statistic.
What does the free audit add on top of this?
We open your banner settings, Tag Manager and GA4 and test the same points directly, instead of relying on answers, then send a written report with the fixes in order.
Does this check legal compliance?
No. The checker is not legal advice and does not check legal compliance. It only checks whether the consent signals reach Google.