Skip to content

Set Up Google Consent Mode v2

Last updated: October 3, 20266 min readIntermediateBrandDeveloper

Google Consent Mode v2 allows Google tags to adapt their behavior based on user consent. Arqam360 automatically fires GCM v2 signals — here's how to verify and optimize the setup.

Consent Mode signals your visitor's choice to Google. It isn't designed to meet any particular legal requirement, and turning it on doesn't make a site compliant with any law. Whether you comply depends on your banner and what it says, the consent records you keep, your privacy policy, and the laws that apply to you.

Consent Mode or TCF signals missing or wrong on your Google tags? Contact Arqam360 support first, not Google. Email admin@arqam360.com or use our contact page. We troubleshoot your Arqam360 setup, your banner and your Consent Mode signals, on every plan. Google support may ask for proof that you contacted your consent management platform first.

What is Consent Mode v2?

Consent Mode v2 is Google's framework for adjusting how Google tags operate based on visitor consent choices. It enables cookieless measurement and conversion modeling when visitors deny consent.

The two ways to run Consent Mode, and how to switch: Consent Mode: basic vs advanced.

To set up a banner that covers Google's consent requirements, including the Google privacy link: Set up a banner that meets Google's consent requirements.

GCM v2 Parameters

  • analytics_storage — Controls Google Analytics cookies
  • ad_storage — Controls Google Ads cookies
  • ad_user_data — Controls sending user data to Google Ads
  • ad_personalization — Controls ad personalization features
  • functionality_storage — Controls functionality cookies
  • personalization_storage — Controls personalization cookies
  • security_storage — Controls security-related cookies (always granted)

Setup

1

Install Arqam360

Deploy the widget on your site. GCM v2 is enabled by default — no extra configuration needed.

2

Verify default signals

Open browser console → check that gtag('consent', 'default', {...}) fires on page load with all parameters set to 'denied'.

3

Test consent update

Accept cookies → verify gtag('consent', 'update', {...}) fires with the appropriate parameters set to 'granted'.

Google Consent Mode signals in browser console
Browser console showing GCM v2 default and update signals.

Verify in Google Tag Assistant

Open Google Tag Assistant (tagassistant.google.com), connect to your site, and check the Consent tab. You should see consent state changes reflected in real time.

If Google Ads shows 'No consent signal detected', or Tag Assistant shows a Google tag firing before the consent default, the Arqam360 script loads too late. Make it the first script in <head>, or in Google Tag Manager use the Arqam360 template on the Consent Initialization - All Pages trigger. If the late tag is served through Google tag gateway, follow the guide linked below.

To see in your browser's console whether the consent default runs before your Google tags: Debug mode: check your consent load order.

If a Google tag runs before your consent default, or your tags use Google tag gateway: Google tag gateway (GTG) and consent timing.

Google documentation

Next Steps

  1. 2Set up Meta CAPI

Was this article helpful?