Google Consent Mode v2 with GetCookies

The four signals

• ad_storage

  Whether advertising cookies may be stored.

• analytics_storage

  Whether analytics cookies may be stored.

• ad_user_data

  Whether user data may be sent to Google for advertising. Required for EEA traffic since v2.

• ad_personalization

  Whether data may be used for personalized advertising and remarketing. Required for EEA traffic since v2.

How it works

1. The GetCookies loader runs as the first script in your page head and calls gtag('consent', 'default', ...) with every signal denied.

2. Google Analytics 4, Google Ads and other Google tags load with those defaults in place and run in their restricted mode.

3. The visitor accepts, rejects or chooses by category in the banner.

4. GetCookies calls gtag('consent', 'update', ...) with the matching signals, and Google tags adjust immediately. When marketing consent is missing, URL passthrough and ads data redaction are turned on.

Ways to install

• Direct script

  Add the loader as the first script in your head. See direct script install.

• Google Tag Manager

  Use the GetCookies tag template with a Consent Initialization trigger. See the GTM installation guide.

• CMS plugins

  WordPress, Magento, PrestaShop and Umbraco plugins load the same script. See integrations.

Good to know

• Global Privacy Control

  When enabled in your domain settings, the widget treats a browser's Global Privacy Control signal as an opt-out.

• No Google partner badge

  GetCookies follows Google's Consent Mode specification but is not listed as a Google-certified CMP partner, and it is not yet a registered IAB Europe CMP.

• Works alongside IAB TCF 2.3

  You can run Consent Mode and TCF consent strings at the same time on Pro and above.