# Consent Mode v2 Checker

> Free self-audit of a Consent Mode v2 setup: 14 yes/no/not-sure questions, a weighted score out of 100 and a list of likely gaps, each linked to a fix.

Source: https://sterling.company/consent-mode-v2-checker · Machine-readable spec: https://sterling.company/consent-mode-v2-checker/spec.json · Publisher: Sterling Lab

## 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.

Nothing is scanned and nothing is read from your site or Google accounts: the checker only scores the answers you give. The weights and band cut-offs are our own definitions, not a benchmark.

## How the score works

Each check has a weight of 1, 2 or 3. Yes earns the full weight, Not sure earns half, No earns nothing. A check marked not applicable is left out of both sides of the sum.

**score = round((sum of weights answered yes + 0.5 × sum of weights answered not sure) ÷ sum of weights of the applicable checks × 100). A check answered na is left out of both sums.**

The checks with weight 3 are core checks. A no or not sure on any of them keeps the band out of solid, even when the score is 80 or higher.

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 in which they are listed below.

## Bands

- **80 to 100**: Solid on paper. The remaining items are tidy-up work. Next step: Fix the remaining items when convenient, then 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. Next step: Start with the first item in the fix list. If a core check is named, fix that one before anything else.
- **0 to 49**: Hard to trust. Fix the top items before you change bids or budgets. Next step: Do not change campaign budgets or bidding yet. Fix the top three items, then run the check again.

## Worked example

A site whose banner calls gtag itself: the bridge check is not applicable. The banner never sends the consent update after Accept, so "Accept sends a consent update (gcs G111)" is No. Nobody repeats the 90-second test after changes, nobody has looked at the modeling status in GA4 and nobody has compared the banner acceptance rate with the GA4 gap, so those three are Not sure. Everything else is Yes.

1. Applicable weight: 25 − 1 = 24
2. Points lost: 3 + 1 + 0.5 + 0.5 = 5, so earned is 24 − 5 = 19
3. Score: 19 ÷ 24 × 100 = 79.2, shown as 79
4. Band: 79 is in 50 to 79, so gaps worth fixing
5. Gaps in order: Accept sends a consent update (3 points lost); 90-second test repeated after changes (1); Modeling status checked in GA4 (0.5); Banner acceptance rate known and compared (0.5)

Steps to compute any result: remove not-applicable checks from the total; lose the full weight for each No and half for each Not sure; earned = applicable weight − points lost; score = round(earned ÷ applicable weight × 100); then apply the band and core rules; sort the gaps by points lost, biggest first.

## The 14 checks (25 points in total)

### Defaults and load order

**All four signals defaulted to denied** (weight 3, core)

- Question: Before a visitor answers the banner, your site sets all four Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) to denied for visitors who must give consent.
- How to check: View the page source or the Tag Assistant: a gtag('consent', 'default', …) call should list all four signals. Ask whoever installed the banner if you cannot find it.
- If No or Not sure: Google tags may start without a consent default. Consent Mode is a signal layer between your site and Google’s tags, and the tags read the four flags on every request. Without an explicit default, nobody can say what state the first hit was sent in.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**Consent default loads above GTM and gtag.js** (weight 2)

- Question: The consent default sits inline in the head of the page, above the Tag Manager container and above gtag.js, not on a later trigger.
- How to check: View the page source: the consent default block must appear before the GTM or gtag.js script tag. A banner that loads on a later trigger is a warning sign.
- If No or Not sure: The first hit may fire before consent is set. Our article explains that if the CMP loads on a later trigger, the first GA4 hit fires with default flags and is never updated, because gtag has already sent it. Consent Mode has to load before gtag.js.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**First page view shows gcs=G100** (weight 1)

- Question: In a clean private window, the first GA4 request on the first page view shows gcs=G100, meaning both storage signals are denied by default.
- How to check: Private window → DevTools → Network → filter “collect” → reload. The gcs parameter of the first request: G100 = both denied, G101 = analytics denied and ads granted, G111 = both granted.
- If No or Not sure: The first request may not carry the default you expect. In our 90-second test, gcs=G100 on the first request is the correct starting point for visitors who must consent. Another value means the default is missing, late or set differently from what you intended.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

### Consent updates

**Accept sends a consent update (gcs G111)** (weight 3, core)

- Question: After a visitor clicks Accept, a new request fires and gcs changes from G100 to G111, which means the banner called the consent update.
- How to check: Same Network filter: click Accept and watch for a new collect request. If none fires, or gcs stays at G100, the banner is not calling gtag('consent', 'update', …). The gcd parameter also shows it: p, q, m or u = still denied, r, t, v or n = granted, l = no signal.
- If No or Not sure: The banner may save its own cookie and never tell Google. Our article calls this the most common Consent Mode v2 failure: the banner shows, the CMP stores its own cookie, but the gtag update never fires. GA4 keeps sending cookieless pings in the default state and paid attribution quietly collapses.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**All four signals present after Accept** (weight 3, core)

- Question: After Accept, GA4 DebugView shows ad_storage, analytics_storage, ad_user_data and ad_personalization on your events, all as granted.
- How to check: GA4 Admin → DebugView: trigger an event after accepting and open its parameters. Granted everywhere expected; denied after Accept confirms a gap. gcs shows only the two storage signals, so it cannot confirm the other two.
- If No or Not sure: Google may receive only half of the v2 signals. ad_user_data and ad_personalization are the two signals added in v2. Our article notes that missing them is functionally equivalent to declined consent for Google Ads modeling, and that most CMPs do not map them unless you enable their v2 template.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**Banner categories mapped to the four signals** (weight 2)

- Question: Each banner category is mapped to the right signals: Statistics to analytics_storage, and Marketing to ad_storage, ad_user_data and ad_personalization.
- How to check: Open the banner’s Google settings and compare the mapping with your categories. Then accept only Statistics and check in DebugView that the three ad signals (ad_storage, ad_user_data, ad_personalization) stay denied.
- If No or Not sure: A category may control the wrong signal. Our article lists the mapping that matches Google’s intent: analytics_storage follows Statistics, and the three ad signals follow Marketing. Mapping errors send consent to Google that a visitor did not give, or withhold consent a visitor did give.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**An explicit Deny also sends an update** (weight 2)

- Question: When a visitor refuses on the banner, Google also receives an explicit update with the signals denied, so a refusal is not mistaken for a visitor who has not answered yet.
- How to check: Private window: click Reject or Deny and watch the Network tab for a new collect request. The signals should read denied, and the banner must not leave the visitor in the “still deciding” state.
- If No or Not sure: A refusal may look like “no answer yet”. Our article states that Google’s modeling does not start on a default state alone: it starts on explicit denies. A banner that never sends the update, even for a refusal, leaves every visitor looking undecided and nothing is modeled.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

### Banner and other tags

**Banner’s Google Consent Mode setting turned on** (weight 1)

- Question: The Google Consent Mode setting inside your cookie banner or CMP is switched on, not left at its default.
- How to check: Open the banner’s dashboard: Cookiebot → Manager → Google; Complianz → Integrations (“Enable Google Consent Mode”); Usercentrics → Services → Google. Other tools have a similar switch.
- If No or Not sure: The banner’s Google integration may be off. Our article says the Google Consent Mode v2 template ships disabled by default in most installs. With it off, the banner only sets its own cookie and does not call gtag.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**Bridge from the banner event to gtag** (weight 1)

- Question: If your banner does not call gtag itself, an inline snippet listens for its consent-change event and calls gtag('consent', 'update', …) with all four signals.
- How to check: Look for a listener on the banner’s event in the page source or in Tag Manager: Cookiebot fires CookiebotOnAccept, Complianz fires cmplz_status_change, Usercentrics fires uc:cmp:consent-updated.
- Not applicable when: Banner calls gtag itself
- If No or Not sure: Nothing may connect the banner to Google. Our article’s first fix is an inline bridge: every mainstream banner dispatches an event when consent changes, and wiring that event to a gtag update closes the gap. Without either the banner’s own integration or a bridge, the update never reaches Google.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**Other pixels start after the consent signal** (weight 1)

- Question: Meta, TikTok, LinkedIn and other pixels on the site start only after the consent signal, and the consent code comes before their conversion code.
- How to check: Private window: before clicking anything, check in Network whether the other pixels already sent requests. Then accept and confirm they start. Your Meta pixel and server events have to follow the same rule.
- Not applicable when: No other pixels
- If No or Not sure: Other pixels may ignore the consent signal. Our article says Meta, TikTok and LinkedIn read the same signal chain, so the consent code has to sit before their conversion code. Our Meta checker covers how the pixel and the server side agree with the banner.
- Fix: [Meta CAPI and Pixel checker: banner and pixel agreement](https://sterling.company/meta-capi-pixel-checker)

### Modeling and upkeep

**90-second test repeated after changes** (weight 2)

- Question: After every change to the banner, Tag Manager, the site theme or the consent code, someone repeats the Accept test and looks at gcs.
- How to check: The test: private window, Network → “collect”, load, click Accept, confirm gcs moves from G100 to G111. Write down the date of the last run.
- If No or Not sure: A working setup may have broken after the last change. Our article says the 90-second test catches the vast majority of Consent Mode v2 gaps. A banner update, a container publish or a theme change can undo a working setup, and a setup nobody retests is one nobody knows works.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**Modeling status checked in GA4** (weight 1)

- Question: You have opened the Consent Settings of your GA4 property and know whether Google is modeling, and whether your traffic is enough for it to start.
- How to check: GA4 Admin → Property Settings → Consent Settings shows the modeling status. Our article gives roughly 1,000 users per day per country over 28 days as the threshold.
- Not applicable when: No EEA traffic
- If No or Not sure: Nobody knows whether modeling is running. Our article’s last step: once accept and deny both flow correctly, check that Google is modeling. Below the traffic threshold modeling does not start, and the gap stays until volume grows or reporting is consolidated.
- Fix: [Consent Mode v2 silently deletes GA4 conversions: the 90-second test](https://sterling.company/blog/consent-mode-v2-ga4-attribution-gap)

**GA4 compared with Google Ads conversions** (weight 2)

- Question: In the last month someone compared the conversions Google Ads reports with the ones GA4 shows, and you know how large the gap is.
- How to check: Compare the same period and the same conversion in Google Ads and GA4, and open Traffic acquisition to see how much paid traffic sits in Direct or Unassigned.
- If No or Not sure: Nobody has measured the gap between Google Ads and GA4. The pattern in our article: Google Ads reports N conversions, GA4 shows a fraction of N, and part of the paid traffic is in Direct or Unassigned. Without a regular comparison the gap is invisible.
- Fix: [Conversion tracking checker: the consent question among 14 checks](https://sterling.company/conversion-tracking-checker)

**Banner acceptance rate known and compared** (weight 1)

- Question: You know your banner’s acceptance rate and have compared it with the share of conversions GA4 is missing.
- How to check: Your banner’s dashboard shows the acceptance rate. If most visitors accept and GA4 still misses a large share of paid conversions, the acceptance signal is not reaching gtag.
- If No or Not sure: A high acceptance rate may hide a broken update. Our article’s tell: if most visitors accept and GA4 still misses half of the paid conversions, the users are not declining, the acceptance signal is not reaching gtag. The rate alone proves nothing, but next to the gap it points to the cause.
- Fix: [Conversion tracking audit service](https://sterling.company/services/conversion-tracking-audit)

## FAQ

**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.

## Related checkers

- [Conversion Tracking Checker](https://sterling.company/conversion-tracking-checker): Google Ads and GA4
- [Meta CAPI & Pixel Checker](https://sterling.company/meta-capi-pixel-checker): Meta Pixel and Conversions API

## Next step

If you want the same points tested inside your banner settings, Tag Manager and GA4, request the [free conversion tracking audit](https://sterling.company/services/conversion-tracking-audit).
