Managing Google Consent Mode V2 manually can be highly error-prone. In this tutorial, we will walk through how FitConsent automates the technical handshake—from dashboard configuration to live validation in your browser.
Google offers two implementation modes for Consent Mode V2: Basic Mode (which blocks tags entirely until consent is given, losing attribution data) and Advanced Mode. Google recommends Advanced Mode because it uses cookieless pings to recover up to 70% of lost attribution data for unconsented users.
To use Advanced Mode, you must inject consent defaults into the dataLayer before any tag fires and include a registered Google CMP Partner ID. Here is exactly how FitConsent handles this for you.
Watch the Video Guide
Step 1: Dashboard Configuration
Let’s start by configuring the consent banner in your FitConsent dashboard to ensure it outputs the correct Advanced Mode signals.
- Add Your Website: In the FitConsent dashboard, click Add Website in the top right and enter your domain. Once created, click Configure Website.
- General Settings: Enter your GA4 Measurement ID to link FitConsent to your Google Analytics property. Set the Legislative Framework to Auto so FitConsent can dynamically apply the correct legal framework based on the visitor’s location.
- Enable Advanced Mode: This is the most critical step. Toggle Google Consent Mode V2 to Advanced. This instructs FitConsent to inject our Google Partner ID into every consent call, certifying your site as CMP-compliant.
- Customize Appearance & Behavior: Navigate through the Appearance, Content, and Behavior tabs to adjust colors, text, translations, and button layouts (like enabling/disabling the Decline button based on your region’s requirements).
Step 2: Integrating the Direct Embed Code
With the dashboard configured, it is time to add the code to your website. Navigate to the Integration tab and select Code and Integration > Direct Embed.
The code provided here must be pasted into the <head> section of every page, before any other scripts (like Google Analytics or Google Ads).
How the code works: The first block immediately sets all four Consent Mode signals (
ad_storage,ad_user_data,ad_personalization, andanalytics_storage) to denied. It also passesdeveloper_id: true, which registers FitConsent as the active CMP before any user interaction occurs.
Below the default script, you will load your tracking tags, followed by the asynchronous FitConsent banner script which handles the user’s choice and fires the update calls.
Step 3: Live Validation in the Browser
You can verify that FitConsent is working perfectly using your browser’s developer tools.
- Open your website and right-click to Inspect the page. Navigate to the Console tab.
- Type
dataLayer.filter(e => e[0] === 'consent')and press Enter. This isolates the consent-related events. - Inspect the Default Call: Expand the first entry (Index 0). You will see the arguments
consentanddefault, with all four signals set todeniedand thedeveloper_idpresent. Notice thegtm.uniqueEventIdis 1—confirming it fired first. - Interact with the Banner: Click Accept All on your live banner.
- Inspect the Update Call: Run the filter command again and expand the newest entry. You will now see the arguments
consentandupdate, with all four signals marked asgranted.
Step 4: Cross-Checking with Google Tag Assistant
For ultimate peace of mind, you can validate the integration using Google Tag Assistant.
- Connect Tag Assistant to your website URL.
- Looking at the event timeline on the left, you will verify that Consent Default is Event 1.
- Navigate to the Consent tab to view the Event Consent State table.
- Before clicking the banner, the On-page Default, On-page Update, and Current State columns will all show Denied for the four purposes.
- After clicking Accept All, the timeline will show a new Consent Update. The On-page Update and Current State columns will immediately switch to Granted for
ad_storage,analytics_storage,ad_user_data, andad_personalization.
And that’s it! Your defaults are set, your updates fire correctly, and Google’s Tag Assistant confirms you are fully compliant.
Note: If you use a tag-managed environment instead of a direct embed, you can achieve the exact same behavior using the official FitConsent GTM Community Template available in the dashboard.
Leave a Reply