Defaults before any tag loads
analytics_storage, ad_storage, ad_user_data and ad_personalization are set to denied as the first script in the page head, ahead of GTM, GA4 or anything your theme prints.
Google Consent Mode v2
Most setups fire the consent update after Google Tag Manager has already loaded. Cookie Consent Banner prints the default-deny signals at the very top of the page, then updates them the moment a visitor chooses.
analytics_storage, ad_storage, ad_user_data and ad_personalization are set to denied as the first script in the page head, ahead of GTM, GA4 or anything your theme prints.
A visitor who already accepted gets their choice applied in the same first script, so there is no flash of denied state and no lost page views.
The plugin detects your GTM container or GA4 measurement ID and sends the consent update to them. Nothing to configure twice.
Open the page with Tag Assistant or type dataLayer in the console: you will see the consent default first, then the update after the visitor decides.
New to Consent Mode? Read our plain-English guide: Google Consent Mode v2 on WordPress.
FAQ
If you advertise to people in the UK or EEA and want remarketing audiences and reliable conversion measurement, Google requires valid Consent Mode v2 signals.
Yes. It detects either and updates consent for both. You do not need to add consent triggers in GTM for the default and update to work.
By default Google tags load with denied signals (advanced mode), so Google can model unconsented traffic. Strict mode holds Google tags back entirely until consent (basic mode).
Yes. Standard mode holds back the Meta Pixel, TikTok, LinkedIn, Hotjar, chat widgets and video or map embeds until the visitor consents.
Up to 5 websites per licence. 14-day money-back guarantee.