Ad-Blocker Detection Settings: Trigger links and Blocking Rules

Detection accuracy is what makes the difference between catching every ad blocker and either missing them or annoying visitors who don’t have one. The DeBlocker+ detection settings control that balance through two values: Trigger links and Blocking Rules. The optimal mix varies from site to site, so this guide walks through how to find the configuration that fits yours.

You will find every setting covered here in your dashboard at Websites → your site → Detection.

Step 1: Find which scripts ad blockers are targeting

Before you change any DeBlocker+ detection settings, check what an ad blocker is actually blocking on your site. Temporarily disable DeBlocker+ for the site, then visit a page where ads are normally shown.

Open your browser’s Developer Tools and switch to the Console tab. The fastest way is a keyboard shortcut:

  • Chrome: Ctrl + Shift + J (Windows / Linux) or ⌘ + ⌥ + J (Mac).
  • Firefox: Ctrl + Shift + K (Windows / Linux) or ⌘ + ⌥ + K (Mac).

In the Console, look for red error lines containing this text: Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

Each of those errors sits next to the URL of the script that the ad blocker prevented from loading. Right-click the URL and choose Copy link (the wording varies by browser). Keep this list of URLs handy: you will use them in Step 2.

Step 2: Configure Trigger Links

Open your DeBlocker+ dashboard and navigate to Websites → your site → Detection. In the Trigger links section, paste the URLs you copied in Step 1, one per line, using the Add item field.

Trigger links are the URLs DeBlocker+ tries to load on the visitor’s browser to detect interference. If any of them fails to load the way an ad would, DeBlocker+ assumes an ad blocker is active and shows your popup. The whole detection routine is built on this list, so the URLs you choose matter more than any other piece of the configuration.

Best practices for trigger links

  • 3 to 5 URLs is the sweet spot for reliable detection.
  • More than 10 URLs is excessive and slows down the check without improving accuracy.
  • No ad scripts of your own? Use Google Ads or DoubleClick URLs: they are blocked by virtually every ad blocker on the market. The dashboard ships with two of these by default:
    • https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
    • https://static.doubleclick.net/instream/ad_status.js
  • You can also add ad script URLs from your own site or any well-known ad network.

Step 3: Configure Blocking Rules

Blocking Rules tell DeBlocker+ how to decide whether a Trigger link was actually interfered with. There are six rules, and you can enable or disable each one independently. All six are enabled by default and work well for most sites, so blocking rules configuration is usually a matter of trimming, not adding.

The six ad blocker detection rules

Request error: triggers when a request to a Trigger link fails with a network or server error. This is the most common signal that an ad blocker is active.

Request abort: triggers when the request is aborted by the ad blocker before it finishes.

Request type: triggers when the ad blocker modifies the type or method of the request, for example by changing it from a script request into something else.

Request URL: triggers when the request URL matches known ad blocker filter lists.

Request body: triggers when the response body comes back empty or has been modified. Useful for catching cases where the script appears to load but returns altered content.

Request redirect: triggers when the ad blocker redirects the request to a different URL, such as a blank response or a local file.

When to disable a rule

If DeBlocker+ is showing the popup to visitors who don’t actually have an ad blocker, one of the rules is firing on a normal server response. To find which one:

  1. Re-enable DeBlocker+ and open the browser Developer Tools Console.
  2. Reload the page and look for messages indicating which rule fired on which trigger URL.
  3. If a script is failing the rule for server-side reasons (CORS, missing headers, an empty body) rather than because of an ad blocker, either remove that URL from your Trigger links or disable the specific rule it’s failing.

Tightening your DeBlocker+ detection settings this way usually only takes a couple of iterations.

Step 4: Test your DeBlocker+ detection settings

Save your changes in the dashboard, then run two quick checks on your live site:

  • With an ad blocker enabled: the DeBlocker+ popup should appear within a couple of seconds of the page loading.
  • With the ad blocker disabled (and the page reloaded): the popup should not appear at all.

If the popup still shows up without an ad blocker, revisit your Trigger links and Blocking Rules and apply the diagnostic steps from Step 3. For the most thorough result, repeat the test in multiple browsers (Chrome, Firefox, Safari) and with several common ad blockers such as AdBlock, uBlock Origin, and AdGuard. Different blockers use different filter lists, and it’s worth confirming detection holds up across all of them.

If issues persist

Some sites need a little extra care: strict Content Security Policy headers, a Cloudflare layer in front of your origin, or JavaScript concatenation by a performance plugin can all interfere with detection in ways that the standard settings can’t fully resolve. If you have worked through this guide and are still seeing inconsistent behavior, open the Support section in your DeBlocker+ dashboard and our team will help you tune the configuration for your specific stack.

Was this article helpful to you?