Appearance

Automatic blocking ​

Automatic blocking is the recommended starting point for Consent Pro. Use the non-async installation so the runtime can initialize before resources that require consent. Keep the installation early in <head>, before other scripts, and do not add async or defer. Webflow's non-async installation has a config script followed immediately by the runtime script; keep their order. Custom sites use the installation snippet supplied for that project.

Set up automatic blocking ​

  1. Install the snippet from the project's Installation tab. Changing a saved loading setting does not replace code already on the site.
  2. Run a scan. Import discovered trackers using the dashboard, or ask your assistant to show the proposed import for your approval.
  3. Review each tracker's category and associated resource URLs. Importing preserves scan evidence and leaves new discoveries unconfirmed. Check missing purpose, provider or retention information before confirming a tracker.
  4. Publish the reviewed configuration when ready. Draft categories do not change the published site. Webflow and custom-site drafts can be tested with the existing banner preview first. Webflow requires the runtime and banner component/source to be installed. Page and region targeting still apply; a link alone does not prove display.
  5. Verify actual browser requests with no consent, after rejection, after allowing each relevant category and after withdrawal. Test initial loads and resources inserted later.

What the runtime uses ​

The blocker uses resource targets attached to published, categorized trackers to identify supported scripts and iframes. A URL must match a configured target; a detected resource without a published category and target is not automatically covered. Essential resources do not wait for optional consent. When a resource requires multiple categories, all must be allowed.

The scanner does not decide which category your business should assign. A completed scan or confirmed tracker describes available evidence and metadata; it does not establish complete blocking or legal compliance.

Check these exceptions ​

  • Google Tag Manager: Consent Pro does not block the GTM bootstrap script through its script matcher. Configure consent inside GTM and test the published tags. See GTM troubleshooting.
  • Images: an image with a live src can load before the runtime intervenes. Use held-source markup for tracking images you control. For images inside third-party frames, check the parent iframe's automatic coverage first; edit the parent embed if needed, not the cross-origin document.
  • Cookie-free embeds: a scan may detect an iframe or script without finding a cookie or storage entry. It may never become a saved tracker. Do not assume a detected Maps embed is automatically gated. Verify it and use manual blocking when it has no supported published target.
  • Async installation: it can initialize too late to intercept resources. Use non-async loading for automatic blocking. Async is a deliberate alternative requiring explicit gating of resources that need consent.
  • Missing observations: a later scan can miss consent-gated resources, unreachable content or unscanned pages. Absence alone does not prove removal or successful blocking. Existing dashboard reconciliation rules still apply to the draft.

When to use manual blocking ​

Choose manual markup when automatic matching cannot target a resource, you want explicit element-level control or you deliberately use async loading. It is an alternative or fallback, not a requirement to rewrite every integration after categorizing trackers. See Manual blocking and Script loading.