How to test consent and blocking (GTM & DevTools)

Use this quick workflow to prove nothing fires before consent and that revoking works.

Step 1: GTM Preview

• Enable Preview in GTM.
• Load your site in the debug window.
• Check that the GetCookies tag fires at Consent Initialization - All Pages.
• Confirm other tags show “Blocked” until consent is granted.

Step 2: Browser checks

• Open DevTools → Network.
• Reload the page before consenting. Trackers (GA, Ads, Meta) should be absent or pending.
• After clicking “Accept,” reload: trackers should now appear.
• After clicking “Reject” or “Save” with categories off, reload: trackers should stay blocked.

Step 3: Pixel helpers

• Use Meta Pixel Helper / GA DebugView / Tag Assistant to confirm no events before consent.
• Toggle consent and verify events start only after acceptance.

Step 4: Edge cases

• Test in incognito/private mode.
• Test with ad blockers disabled (they can hide issues).
• If using the hybrid blocker, ensure blocker.js is the first script in <head>.

What to document

• Screenshots of GTM Preview showing blocked tags pre-consent.
• Network/console proof that trackers load only after acceptance.
• Note any tags loaded outside GTM and how they’re blocked (blocker.js or data attributes).