Ad block browser extensions are smarter than ever, most detection scripts get blocked or bypassed in seconds. Ad Block Reactor flips the script: it uses a multi-layered, evasion-resistant approach - including randomized DOM bait, self-hosted probes, and off-thread network testing with performance metrics to reliably detect even aggressive blockers like uBlock Origin (medium/hard mode), AdGuard, Brave Shields, and many others.
But here's what makes it truly different: it doesn't force your hand. No mandatory nags, no hard content locks, no prescribed popups. Reactor simply gives you actionable information and powerful hooks, then gets out of the way. You decide how (or if) to respond. If you want to detect and react to ad blockers - this extension is for you.
Key Features
- Robust, Future-Proof Detection
- Combines DOM bait (with per-load randomization), local transparent GIF probes, and worker-based network bait targeting real ad scripts - with smart timing/size analysis to defeat stubs and fake responses.
- Dynamic ACL Integration
- Optionally add users to a custom Viewing Access Level when blocking is detected (adACL), and switch to a different level when they disable/clear it (clearACL). Perfect for:
- Showing fallback house ads or affiliate banners to blockers
- Unlocking premium modules or discounts for compliant users
- Displaying a timely "Thank you for whitelisting!" offer or subscription nudge
- Flexible Content Reactions (for articles)
- When blocking is active:
- Truncate content (at read-more or custom HTML point) + optional append message
- Redirect to another page/menu item (with optional system message)
- Page-view counter: allow X views before escalating (e.g., redirect)
- Expose counter data to custom JS for dynamic UI
- When blocking is active:
- Custom JavaScript Hooks
- Fire scripts on detection, on clearance, or on status change. Track events in GA4/Matomo, show modals, update UI - whatever fits your site.
- Zero Bloat Philosophy
- No forced outputs, no unnecessary markup. Reactor runs quietly and only triggers the reactions you define.
Real-World Reaction Ideas
- Serve self-hosted/static ads to blockers while keeping third-party networks for clean users
- Tease partial content and upsell an ad-free subscription to detected blockers
- Reward whitelist compliance with exclusive content or perks
- Silently log detection rates for analytics (no user disruption)
- Combine with modules positioned by access level for seamless alternate experiences
Video
Download
System - Ad Block Reactor 5.0.0176
Frequently Asked Questions:
How many people use ad blockers in 2025? Ad blocker usage continues to grow worldwide. Est
Ad blocker usage continues to grow worldwide. Estimates range from over 900 million active users to projections nearing 1 billion by 2026. Globally, around 42-43% of internet users employ ad blockers on at least one device, with higher rates in regions like Asia (e.g., Indonesia and Vietnam over 40%) and Europe (up to 49% in Germany). In the US, usage hovers around 27-35%.
Why do users install ad blockers?
Primary reasons include blocking intrusive or repetitive ads, improving page load speeds, and protecting privacy by reducing tracking. Many users find excessive advertising annoying, with privacy concerns driving a significant portion of adoption.
Is Ad Block Reactor's detection reliable against modern blockers like uBlock Origin?
Yes, the plugin uses a multi-layered approach: randomized DOM bait (to evade cosmetic filters), self-hosted GIF probes, and web worker-based network bait with PerformanceObserver metrics analysis. This defeats stubs (fake responses) common in aggressive modes, including uBlock Origin's medium/hard modes, which block third-party scripts aggressively.
What makes the network bait in Ad Block Reactor effective?
It fetches real ad scripts (e.g., adsbygoogle.js or gpt.js) off the main thread via a web worker, then uses PerformanceObserver to check timing, transfer size, and decoded body size. Real loads show meaningful data; blocked requests or stubs result in zero/near-zero metrics or no entry - allowing reliable distinction even when blockers fake success.
Will this plugin break my site or annoy users?
No, Ad Block Reactor is non-intrusive by design. It provides detection and tools (ACL swaps, content reactions, JS events) but forces nothing. Admins choose reactions: silent logging, fallback ads, gentle messages, or none at all. Best practice: use soft nudges or alternate content rather than hard blocks to maintain positive UX.
How do the adACL and clearACL features work?
Create two Viewing Access Levels in Joomla (e.g., "Blocker Detected" and "Compliant User"). Assign adACL when blocking is detected and clearACL when cleared. Use them to show/hide modules, articles, or menus - e.g., fallback house ads for blockers or thank-you/subscription offers for compliant users.
Does detection work for guests and logged-in users?
Yes, it works for both. Status persists via session userstate for guests and ties into Joomla's Identity for logged-in users when using ACL reactions.
Can I track ad blocker usage on my site?
Absolutely! Enable reporting and use the dispatched JS events (SystemAdBlockReactorDetected / SystemAdBlockReactorCleared) to fire analytics events (GA4, Matomo). Many admins log changes to measure whitelist conversion rates.
Is there a risk of false positives?
Minimal with the multi-layer setup. Network bait targets common ad domains, but self-hosted probes reduce external flakiness. Disable network bait temporarily if testing slow connections.
What's the best way to "react" without losing visitors?
Focus on value exchange: serve self-hosted/non-intrusive fallback ads to blockers (via adACL), reward whitelisting with perks (via clearACL), or show polite one-time messages. Avoid hard content locks—data shows gentle approaches convert better while preserving trust.
