AntiAdBlockCore – AdBlock Recovery

Description

Recover the ad revenue that ad blockers take from your site

A growing share of your visitors browse with an ad blocker. They read your content, but your ads never load, so every one of those page views earns you nothing. AntiAdBlockCore detects ad blockers on your WordPress site and shows those visitors a customizable anti-adblock message asking them to allow ads. Visitors who whitelist your site start seeing ads again, and you get that revenue back.

Free plan, no payment method needed. Works with any theme and with WP Rocket, LiteSpeed Cache and W3 Total Cache: the script is kept out of their JavaScript optimization and their page cache is purged for you when something changes.

It is built for publishers, bloggers and media sites that live on advertising: news, recipes, tutorials, downloads, streaming, forums or any site monetized with Google AdSense, Google Ad Manager or another ad network.

Up and running in minutes, no code to paste

1. Install and activate the plugin.
2. In Settings > AntiAdBlock Core, click Click here to connect your AntiAdBlock Core account. Sign in or create your free account (no payment method needed), check the security code and approve.
3. The plugin verifies your domain and the detection script goes live on every page. With first-party delivery, the default, the script starts once your CNAME record is active.

No snippets to copy, no theme files to edit. The plugin adds the script to every page whatever your theme, and a built-in installation check confirms it is really there.

Ad blocker detection that keeps working

• Detects the ad blockers your visitors actually use: browser extensions such as uBlock Origin, AdBlock, AdBlock Plus and AdGuard, browsers with built-in blocking such as Brave, and network-level blockers.
• Built to avoid false positives: visitors without an ad blocker are left alone.
• Always up to date: detection is maintained on the service side, so it keeps up when ad blockers change, without plugin updates.
• First-party delivery: serve the script from a subdomain of your own site with a single CNAME record, so delivery stays first-party and more reliable. The plugin walks you through the record step by step (including the Cloudflare grey-cloud setting) and switches over by itself when it is active. Prefer to keep it simple? Third-party delivery works too, and you can switch at any time.

An anti-adblock message that converts

• A clear notice that explains why ads matter to your site. By default it works as an adblock wall: visitors allow ads on your site to keep reading, with step-by-step instructions for their ad blocker and a button that checks again right away.
• The built-in text is in English or Spanish, following the visitor’s browser.
• Customize the message, colors, logo and look from your dashboard, depending on your plan, and preview it without installing an ad blocker.
• Show the message (recovery) or, on eligible plans, run in detection-only mode, and exclude any page or path, such as checkout or privacy pages.

Measure what you recover

• Ad blocker rate, detections and recoveries, per site.
• Pages, countries, browsers and ad blocker types in the dashboard (detailed analytics on the Max and Business plans).
• A monthly summary right on the plugin’s settings page.

Everything under control from WordPress

• Overview: site, account, delivery mode and status at a glance, with a Check button and a link to the step-by-step guide.
• Protection switch: turn ad block protection on or off on this WordPress.
• Installation check: opens your home page and your latest posts and pages as an anonymous visitor and confirms the script is on each one, and off the pages you excluded.
• Logged-in users who can edit posts are skipped by default (contributors, authors, editors and administrators), so your team never sees the message and their visits stay out of the stats.
• Manual code option for headless front ends or builders that serve their own HTML.

Works with your stack

• Any theme, including themes that do not call wp_head().
• Caching and optimization plugins: WP Rocket, LiteSpeed Cache, Autoptimize, SiteGround Optimizer, Perfmatters, Flying Press and W3 Total Cache. The script is excluded from their JavaScript optimization (minification, deferral or delay). When something changes, the plugin purges the page cache of WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer and WP Engine.
• Cloudflare, including Rocket Loader.
• AMP pages and feeds are skipped automatically.
• Multisite: each site connects on its own.

Plans

The free plan includes 5,000 detections per month (a detection is a page view where an ad blocker is detected; page views without one never count), no payment method required. Paid plans add more detections and sites; Max and Business also add full customization of the message and detailed analytics. Plans are managed in your AntiAdBlock Core dashboard, never inside WordPress: the plugin code is complete and the same for every plan.

Third-party service

This plugin relies on the AntiAdBlock Core service (https://antiadblockcore.com), a software-as-a-service run by the plugin authors. It is required for the plugin to work.

• When you connect: nothing is sent until you click the connect button. Then the plugin sends your site address and name, the WordPress, PHP and plugin versions, your admin language and whether the site is a multisite, a subfolder install or a non-production environment to https://antiadblockcore.com. It receives a token limited to this site, used to read the site’s status, usage and plan and to verify your domain. No user accounts, emails or content of your site are ever sent.
• In the background: while connected, the plugin reads that status once an hour so the script address, the verification state and your quota stay current. It stops when you disconnect.
• On your pages: once the domain is verified, your pages load the detection script from antiadblockcore.com or, with first-party delivery, from a subdomain of your own domain that points to the same service (you create that DNS record yourself; nothing is changed for you). For each page view the script reports whether an ad blocker was detected and which kind, the page path, the browser type and the country derived from the visitor’s IP address. The IP address is used in transit to derive the country and to protect the service; it is not stored in the statistics and is deleted from the service’s server access logs after 14 days. To count recoveries correctly, the script keeps a few small first-party entries on your own domain: in the browser’s local or session storage and, when your site spans several subdomains, in a first-party cookie on your domain. They hold when an ad blocker was last seen and which kind, a few flags for the current visit (such as the page and whether the message was closed) and, for up to 24 hours, reports that could not be sent yet. They contain no identifier of the visitor, are not used for advertising, profiling or tracking across sites, and are ignored after 30 days; the cookie expires then. Describe them in your privacy or cookie policy and decide, under the rules that apply to you, whether your consent tool should cover them.
• Credit: the message shown to visitors who have an ad blocker carries a small “powered by AntiAdBlock Core” link. It appears only inside that message, only for visitors with an ad blocker, and higher plans can switch it off.
• Terms of service: https://antiadblockcore.com/terms
• Privacy policy: https://antiadblockcore.com/privacy

The detection script is loaded from the service and is not bundled in this plugin; the plugin code itself is fully readable.