What Google Consent Mode v2 requires
- Set a default consent state before any Google tag sends data, using
gtag('consent', 'default', ...)or Tag Manager’s consent settings. - Set ad_storage, analytics_storage, ad_user_data and ad_personalization based on user consent.
- Update the consent state when the user changes their preferences.
- Use a Google-certified CMP that works with the IAB TCF if you show personalised ads through AdSense, Ad Manager or AdMob to visitors in the EEA, UK or Switzerland.
How GrantCookie covers it
- Scheduled scans. The scanner finds the cookies and trackers your site sets, sorts them into categories and re-checks on every scheduled scan, so the banner asks about what is really there.
- Provable records. Every choice is timestamped and stored with the banner version the visitor saw. Paid plans include consent log export.
- Withdrawing consent. A re-open control stays on every page, so visitors can withdraw or change their choice at any time.

This page is general guidance. It is not legal advice. Check your specific obligations with a qualified adviser.

