Why is my banner not blocking scripts?

If trackers still fire before consent, use this checklist to fix common causes.

1) Hard-coded scripts outside GTM

• Move them into GTM or use the hybrid method with blocker.js in <head> so they’re paused before loading.
• For scripts you can’t move, wrap them with type="text/plain" and a data-cookieconsent attribute so GetCookies controls them.

2) GTM trigger order

• Your GetCookies tag must use Consent Initialization - All Pages.
• If it’s on “All Pages” or “DOM Ready,” tags may fire too early.

3) Missing consent requirements on tags

• In GTM, open each tracking tag → Advanced Settings → Consent Settings → Require consent → add analytics_storage, ad_storage, etc.
• For Meta/ads, include ad_user_data and ad_personalization.

4) Wrong Domain ID or inactive domain

• Double-check Domain ID in your GetCookies tag/snippet.
• Ensure the domain is active in the dashboard.

5) Script order in <head>

• If using the hybrid approach, blocker.js must be the first script in <head>, before GTM and any trackers.

6) CDN/theme cache

• Clear cache/CDN after changes. Old cached pages may still load the previous scripts.

Quick test

1. Open incognito.
2. GTM Preview: confirm GetCookies fires at Consent Initialization.
3. DevTools → Network: reload; trackers should wait.
4. Grant consent; confirm trackers then load.
5. Revoke/deny; ensure trackers stop on next page load.