How To Verify Consent Mode v2 Is Working

Do not trust a consent setup just because the banner appears. Verify the default state, the visitor choice, and the tags that run afterwards.

Start with a fresh visitor

Use an incognito window or clear the site's consent cookie. Reload the page before clicking anything. The banner should appear and Google consent should start from the expected default state.

Use GTM Preview

Open Google Tag Manager Preview and load the site. Check the first page events. The CMP or consent tag should run early, normally on Consent Initialization. Then check that your GA4 and Google Ads tags are receiving the correct consent state.

Test reject all

Click reject all, reload the page, and check again. Optional storage should remain denied. If analytics or advertising cookies are still being written, something else may be firing outside the consent flow.

Test accept all

Clear the test state again, accept all, and reload. Google tags should now receive granted signals for the categories you allowed. This also confirms that stored consent is applied on the next page view.

Check the browser too

Open DevTools and look at cookies and network requests. This is useful because GTM Preview can show tag behavior, while the browser shows what is actually written or requested.

Common signs something is wrong

Google tags fire before any consent default is visible.
Reject all still writes optional analytics or marketing cookies.
The banner choice changes visually, but GTM does not receive an update.
Stored consent is ignored after a reload.

CleanCMP includes a testable consent event

CleanCMP pushes a clear consent update event, stores visitor choices, and keeps proof records so you can test what happened instead of guessing.

Create account