Türkçe
English
Check Your Google Consent Mode Setup
Verify your Consent Mode v2 signals, review consent states and identify configuration issues that may affect Google Ads and Google Analytics.
Google Consent Mode Checker
Instantly verify your Google Consent Mode V2 implementation and ensure full compliance.
What Does the Checker Review?
The Google Consent Mode Checker reviews how consent signals are configured on your website and whether they respond correctly to visitor choices.
It checks key Consent Mode v2 signals, including ad_storage, analytics_storage, ad_user_data and ad_personalization, and helps identify missing or inconsistent consent states.
This gives you a clearer view of your implementation before configuration issues affect advertising or measurement.
Frequently Asked Questions
Google Consent Mode allows Google tags to adjust their behaviour based on a visitor’s consent choices. It works with a cookie banner or CMP and communicates those choices to services such as Google Ads and Google Analytics. Google explains the framework in its official Consent Mode overview.
A Google Consent Mode Checker reviews the consent signals sent by your website and helps identify missing, incorrect or inconsistent settings. For Consent Mode v2, this includes key signals such as ad_storage, analytics_storage, ad_user_data and ad_personalization.
A correct setup should apply the expected default consent states and update them when visitors accept, reject or change their preferences. The checker helps reveal whether those signals are being sent consistently and whether your Consent Mode v2 setup needs further review.
Consent Mode v2 uses four key signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. Together, they communicate how advertising storage, analytics storage, advertising-related user data and ad personalisation should be handled.
In Basic Consent Mode, Google tags are blocked until the visitor interacts with the consent mechanism and grants the required permission. In Advanced Consent Mode, tags can load with consent set to denied and may send cookieless signals that Google can use for eligible modelling.
Google Tag Manager is not the only way to implement Consent Mode. It can also be configured through the Google tag or a compatible consent management platform, although Tag Manager provides dedicated consent controls and a Consent Overview for managing tag behaviour.
Google Consent Mode does not replace a cookie banner or CMP. The consent interface collects the visitor’s choices, while Consent Mode communicates those choices to Google tags so their behaviour can adapt accordingly.
Google Consent Mode v2 is not a privacy law, but Google requires relevant consent signals for certain advertising, measurement and personalisation features involving users in the EEA. Google explains these requirements in its guidance on Consent Mode for EEA traffic.
The checker is designed to identify configuration issues rather than modify your website automatically. Once a problem is detected, the Consent Mode, CMP or Google Tag Manager configuration should be reviewed and corrected before testing the setup again.