When to use this
Tracker blocking is Step 4 of setup. On Growth, this step lets you configure enforcement modes, custom per-domain rules, deeper GTM integration, consent replay verification, and editable tracking policies. On Pro, Step 4 is shown as optional because the plan includes runtime monitoring and consent banner publishing, but not dashboard-configured tracker blocking rules. Upgrade to Growth if you need managed pre-consent blocking configuration.
Use this article when analytics still fire before consent despite a visible banner, when you migrate from another CMP, or when you need to align Google Consent Mode v2 signals with enforcement. Blocking without a published banner is ineffective because the engine needs category state.
Saving enforcement mode in the dashboard writes to your site consent record; runtime verification’s blocking check reads this state on the next visit.
Server-side tags (CAPI, server GTM) still need policy basis in your privacy notice—blocking in browser does not eliminate backend processing you operate separately.
Periodic re-audit after adding new pixels: marketing often ships tags without filing CMP tickets; monthly diff of scan tracker list versus prior month catches drift.
Step-by-step instructions
- Open Dashboard → Consent → Tracker blocking (or Setup Step 4). Site-scoped routes also appear under your site’s tracker-blocking page.
- Review detected or suggested third-party domains from scans and runtime telemetry where shown.
- Select an enforcement mode appropriate for your stack—strict pre-consent blocking is recommended for GA4 and ads tags.
- Map Google tags to Consent Mode defaults if you use GTM; update triggers so tags respect updated consent snapshots.
- Add custom allow/block rules for niche pixels, then save policies explicitly.
- Publish or sync consent configuration if the UI links blocking to published config.
- Visit your site without accepting marketing cookies and confirm in Network tab that blocked domains do not return 200 for tracking pixels.
- Accept marketing in the banner and confirm allowed tags resume (Growth replay verification automates this).
- Mark Step 4 complete in setup when enforcement mode is saved and runtime verification later shows blocking active.
Expected result
Before consent, analytics and marketing requests are suppressed or held per your mode. After granular accept, only approved categories load their tags. Setup Step 4 shows completed, and runtime verification reports blocking engine active.
Protection and Runtime Health views display blocked request counts over time on Growth, giving ongoing assurance—not only a one-time test.
Document enforcement mode in change tickets when marketing blames missing analytics—reviewers can confirm whether strict blocking was intentional versus misconfigured GTM consent updates.
Troubleshooting
Google Analytics still records pre-consent
Verify the GA tag fires through GTM after GDPRChecker boot. Set Consent Mode defaults to denied for analytics and ads until update. Remove duplicate hardcoded gtag installs outside GTM that bypass enforcement.
Custom rule not applied
Advanced rules require Growth. Confirm rule saved, published config refreshed, and page reloaded. Wildcard domains must match the exact request host seen in Network panel.
Blocking breaks embedded videos
Classify necessary embeds separately or allowlisted domains in custom rules. Necessary category should stay minimal—document why each exception is essential.
Step 4 is optional on Pro
Tracker blocking setup is Growth-only. Pro users see Step 4 marked optional, then continue to Step 5 · Legal Pages before Runtime Verification. Upgrade to Growth if you need dashboard-configured tracker blocking.