Google Ads and Analytics

Google Consent Mode v2, set before the first tag

If you use Google Ads or Google Analytics with visitors in the EEA, the UK or Switzerland, Google asks for valid consent and for the visitor’s choice in four Consent Mode signals. ConnectWiz sets them to denied before any Google tag runs and updates them the moment the visitor chooses.

All four Consent Mode v2 signals Defaults before Google tags A Consent Mode check in every scan

Not legal advice

This page describes Google’s policies as we understand them on 5 November 2026 and how ConnectWiz behaves. It is not legal advice, and using ConnectWiz does not by itself make a website compliant. When in doubt, ask a lawyer who knows your market.

What Google asks

Consent, and the signals that carry it

The EU User Consent Policy

For visitors in the EEA, the UK and Switzerland: legally valid consent for cookies and for ad personalisation, records of it, each party named, and a way to withdraw.

Four Consent Mode v2 signals

ad_storage, analytics_storage, ad_user_data and ad_personalization. Without the last two, Google does not use EEA visitors’ data for personalisation or remarketing.

Basic or advanced

In basic mode Google tags wait for the choice. In advanced mode they load with everything denied and send cookieless pings that Google uses to model conversions.

Google Analytics from 15 June 2026

Google Analytics uses Consent Mode as the single control for the Google Ads cookies and identifiers it collects.

The Digital Markets Act

Gatekeepers such as Alphabet, Amazon and Meta need the user’s consent before combining personal data across services for advertising. Advertisers meet their part by sending Consent Mode signals.

Publishers are different

Sites that show Google ads through AdSense, Ad Manager or AdMob in the EEA, the UK and Switzerland need a Google-certified consent tool that uses IAB TCF.

In ConnectWiz

Consent Mode, from the first line of the page

Denied before any Google tag

All four signals are set to denied in the first lines of your page, ahead of Google Tag Manager and gtag, and updated the moment the visitor chooses.

Mapped to your categories

Marketing carries ad_storage, ad_user_data and ad_personalization; analytics carries analytics_storage.

Less data while denied

ads_data_redaction is on, so Google ad requests carry no click identifiers while ads storage is denied.

A Google Tag Manager template

The ConnectWiz Consent template sets the same signals inside your GTM container.

A check in every scan

Defaults before the tags, all v2 signals present, denied before a choice, and both Reject all and Accept all reaching Google tags.

Google’s Developer ID

ConnectWiz sets the Developer ID Google issued to it as a consent tool, so Google can see which tool set the signals.

Still yours

What you still need to do

ConnectWiz runs the banner and keeps the records. These steps sit with you.

  • Remove other consent defaults your site or GTM container sets for Google tags. Two consent tools fighting over Consent Mode give unpredictable results.
  • Run a scan after setup and after every container change, and fix what the Consent Mode check marks as failed.
  • Check Google Ads: after a few days of traffic, look at the consent status of your conversion tags in Diagnostics.

The details, with sources

The guide explains each rule in more depth, with the settings that apply it and links to the texts themselves.