Detection API
The headless adblock detection API
Run our multi-signal detection engine with no overlay. The script confirms the ad blocker, then hands the result to your own code through a JavaScript event or callback, so you decide what happens next. Available on the Max and Business plans, set per site.
A detector you can build on
Your interface, our engine
The script detects every major blocker and renders nothing. No overlay, no message, no whitelist prompt. What a blocked visitor sees is entirely your call.
A clear result on every visit
One window event, aabc:detection, fires with a small frozen payload: whether an ad blocker was found, which kind, and the browser. A callback and a snapshot are there too for listeners that attach late.
The blocker type, classified
Every result says what is doing the blocking: a browser extension, Brave Shields, built-in browser protection, or network and DNS level filtering. The same taxonomy your dashboard already uses.
Stats and quota, unchanged
Detections are still counted and still show in your dashboard, and a detection costs the same as in recovery mode. If your own flow convinces a visitor to allow ads, your recovery rate still records it.
One listener, your logic
Read the result in a few lines
<script>
window.addEventListener("aabc:detection", function (event) {
var d = event.detail;
// { detected, blockerType, path, browser }
if (d.detected) {
// Your logic: your own notice, content gating, logging.
}
});
</script>Example payload: { detected: true, blockerType: "extension", path: "A", browser: "chromium" }. Every field, enum value and edge case is documented on the API reference.
One account, both modes
The mode is a per-site setting. Run a headless domain for your app and keep the recovery overlay on your content site, from the same dashboard and the same quota.
Detection API FAQ
What is the Detection API?
It is a headless mode for AntiAdBlock Core. The same detection engine runs, but instead of showing a recovery overlay it emits the result to your own JavaScript. You handle the response: a custom notice, content gating, analytics, whatever your product needs.
Which plans include it?
The Detection API is available on the Max and Business plans. It is set per site, so one domain can run headless while another keeps the recovery overlay.
Does a detection still count against my quota?
Yes. Detection works exactly the same in this mode, so each ad-block visit counts once, just as it does with the recovery overlay. Plain page views never count.
How do I read the result reliably?
Listen for the aabc:detection window event, define a window.AABC_ON_DETECT callback, or read the window.AABC_DETECTION snapshot for listeners that attach late. The callback is the most robust, since page scripts cannot intercept a direct call. The API reference covers all three.
What happens if the script cannot run?
It stays silent. If a site is unverified, a kill switch is on, or the visitor is a bot, no event is emitted. Silence means no answer, not no ad blocker, so your code should treat the normal path as the default and fail open.
Build your own adblock response
Start free, move to Max when you are ready, and switch any site to the Detection API from your dashboard.