Blocking

Auto-blocking and custom rules

How allowedit blocks 40+ known trackers until consent, which Google tags it leaves to Consent Mode, and how to add your own URL rules for anything else.

Auto-blocking holds known trackers until the visitor allows their category, without changing your site's code. It's on by default for every new site, on every plan.

How it works

When the allowedit script runs, it watches for scripts and iframes added to the page, whether they're in your HTML or added later by Tag Manager, a plugin or an app. Each source URL is matched against a list of 40+ known trackers. If one matches and its category isn't allowed yet, allowedit stops it from loading. When the visitor allows that category, it loads.

This only catches tags that load after the allowedit script, which is why the script must be the first thing in your head.

What it blocks

The list covers the common advertising, analytics and embed services, including:

ServiceCategory
Meta Pixel (Facebook)Marketing
TikTok PixelMarketing
LinkedIn Insight TagMarketing
Pinterest TagMarketing
Microsoft Advertising (Bing UET)Marketing
YouTube embedsMarketing
Google Maps embedsMarketing
HotjarAnalytics
Microsoft ClarityAnalytics

The full list, with each pattern and category, is in your dashboard under Banner, then Blocking. We keep it up to date as vendors change their script URLs.

Blocked YouTube and Google Maps embeds show a placeholder with a button, so visitors can load a single video or map without accepting everything.

Google tags (the Google tag, Google Analytics 4, Google Ads, Floodlight) understand Google Consent Mode. With Consent Mode on in advanced mode, allowedit doesn't block them. They load in a denied state and adjust to the visitor's choice themselves.

In basic mode, Google tags are held until their category is allowed, like any other tracker.

See Google Tag Manager for how the modes differ.

Add your own rules

For a tracker that isn't on the list, add a custom rule:

  1. In your dashboard, open the site, then Banner, then Blocking.
  2. Choose Add rule.
  3. Enter a pattern: part of the script or iframe URL, at least 3 characters. Any src that contains it matches.
  4. Choose the category it should wait for: preferences, analytics or marketing.
  5. Publish.

Examples:

PatternCategoryBlocks
widget.reviewvendor.comMarketingA reviews widget that tracks across sites
cdn.example-heatmaps.com/rec.jsAnalyticsOne heatmap script
chat.example.com/loaderPreferencesA chat widget that stores settings

You can add up to 50 rules per site. Keep patterns specific: a pattern like cdn would match far more than you mean.

When to use manual blocking instead

Rules match URLs, so they can't catch inline scripts (code written straight into a <script> tag with no src). For those, mark the script yourself with type="text/plain" and data-category.

Turn auto-blocking off

You can switch auto-blocking off under Banner, then Blocking. Do this only if you already control every tag with consent triggers, for example in Google Tag Manager. With it off, your custom rules and manual blocking still work.

Check what's still getting through

  • Run a scan. The scanner loads your pages before any consent and flags every cookie set before consent. Each one points to a tag that isn't blocked.
  • Check the network. In a private window, choose Reject all, then check the Network tab in your browser's developer tools for requests to tracking domains.
  • Try the free checker. The cookie checker shows the trackers it saw before consent on any page.

Read more about why blocking matters.

Still stuck? Email support@allowedit.com with your site's address and what you see.