Consent Mode v2 check
The Consent Mode v2 check confirms that Google Consent Mode v2 is wired up correctly on your site. It runs as part of the scanner and uses the same crawler, OptSensBot. For what OptSens sets and why it matters for Google Ads and Analytics, see Google Consent Mode v2.
What it checks
The check loads a page and watches the order in which consent signals and Google tags fire, before any visitor makes a choice. It looks for:
- A consent default: a
consentdefaultcall that sets the initial state before tags run - All four v2 signals in that default:
ad_storage,analytics_storage,ad_user_dataandad_personalization - Correct ordering: the consent default fires before the first Google tag, and no tag runs without a consent state
- wait_for_update: a timeout that gives a banner loaded through a tag manager time to update consent before tags act on it
It also reads region overrides, the url_passthrough and
ads_data_redaction flags, and detects the GTM containers and GA4
measurement IDs present on the page.
What it does not do
The check observes the consent setup. It does not send hits to your analytics. The scanner blocks outbound analytics collector requests during the check, which lets it observe Google tags loading without registering page views in your reports.
The verdict
The check returns one of three verdicts:
| Verdict | Meaning |
|---|---|
| Complete | A consent default with all four v2 signals fired in the right order |
| Partial | Some consent code is present, but the setup is incomplete |
| Missing | No consent code was found, or there are no Google tags to gate |
When a site has no Google tags at all, Consent Mode does not apply, and the check reports only that single point rather than listing consent issues.
Common findings
- No consent default: tags can fire without a consent state. Make sure the OptSens script loads before your Google tags.
- Missing signals: the default is present but does not set all four v2 signals.
- Default after first tag: the consent default fires too late, after a tag has already run. Loading order is the usual cause.
- No wait_for_update: a tag-manager-delivered banner has no window to update consent before tags act.
The most reliable fix for ordering problems is to load OptSens as a direct first-party script in the page head, above your Google tags, rather than through a tag manager. See install with Google Tag Manager and verify installation.
If the check comes back empty
If the check cannot read your page, it is usually blocked by a bot challenge or firewall before it loads. Allow OptSensBot and run it again. See OptSensBot for the allow options, and troubleshooting for more help.