CookieSure sends Google Consent Mode v2 signals by default. Google tags on your site learn whether the visitor allowed statistics and marketing, before they set any cookie.
What CookieSure does
- Default state. Before any Google tag runs, CookieSure sets the consent types (such as
analytics_storage,ad_storage,ad_user_data,ad_personalization) to denied where your region rules ask first. - Update. When the visitor makes a choice, CookieSure sends an update with the categories they allowed.
- Returning visitors get their saved choice right away.
Switch it on or off on CookieSure → Settings with Google Consent Mode v2. It is on by default.
WP Consent API
The WP Consent API lets other plugins read the visitor’s choice, so they can wait for consent too. CookieSure shares the choice with it when that plugin is active. The switch is WP Consent API on CookieSure → Settings.
Check that it works
- Open your site in a private window.
- Open Google Tag Assistant (tagassistant.google.com) and connect to your site.
- Before you choose, the consent state shows the defaults. After you click Accept or Reject, an update appears with your choice.
Common questions when setting it up
- Google Tag Manager users: keep the Consent Mode defaults from CookieSure and do not add a second default in Tag Manager, or the two may disagree.
- Two banners? Use one consent tool only. Remove other cookie banners so only one sets Consent Mode.
- Region rules decide the default: where visitors are asked first, the default is denied until they accept. See Set up the cookie banner.
FAQ
Do I need Consent Mode if I do not use Google tags?
No. Without Google tags the signals have no effect. You can leave the setting on.
Does Consent Mode replace the banner?
No. Consent Mode passes the visitor’s choice to Google; the banner is how the visitor makes that choice.
Does Consent Mode work without the banner?
The signals describe the visitor’s choice, so they only change once a visitor can make one. Turn on the banner if Google tags on your site need consent.