Google Consent Mode v2: Technical Compliance for Conversion Modeling

Basic Mode vs. Advanced Mode

The architectural choice between the two implementation modes defines how much intelligence is preserved in your campaigns:

Example of Consent Initialization in Code

Below is the code snippet that must run in the website's <head> before any Google library loads:

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}

  // Sets the default state to denied before the banner responds
  gtag('consent', 'default', {
    'ad_storage': 'denied',
    'ad_user_data': 'denied',
    'ad_personalization': 'denied',
    'analytics_storage': 'denied',
    'wait_for_update': 500
  });
</script>

As soon as the visitor interacts with the consent management platform (CMP) and authorizes collection, the CMP fires the update command:

gtag('consent', 'update', {
  'ad_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted',
  'analytics_storage': 'granted'
});

How Statistical Modeling by Machine Learning Works

In advanced mode, when a user denies advertising cookies, the Google tag neither writes identifiers to the browser nor reads existing cookies. It sends a lightweight request containing technical context metadata (timestamp, browser type, operating system and page URL).

Google's AI model analyses the behaviour of the millions of users who accepted cookies and uses supervised learning techniques to estimate the conversion probability of the group that declined. The numbers are reflected in the Google Ads conversion reports, offering a reading close to the account's financial reality.

Frequently Asked Questions about Consent Mode v2