Try it on your site
Put AntiAdBlock Core on your own site
Set it up on your own site in about a minute, in just a few steps. From the first visitor, your dashboard shows in real time how many people block ads, how many you win back, and the revenue that was quietly slipping away.
Step by step
See exactly how you go live
The whole journey, from creating your account to your first real numbers. It runs on its own; hover to pause, or click a step to jump.
First-party delivery, set up for you
It is the default when you add a site, and it is what keeps detection working against modern blockers. Here is what it does and why it matters.
Filter lists target third-party scripts
Filter lists keep adding rules against third-party detection scripts, and every new rule means a slice of visitors you never detect. First-party delivery keeps detection at its maximum.
Served from your own domain
First-party delivery serves the exact same script from a hostname on your domain, which blocker lists rarely reach. Same script, same dashboard, far higher coverage.
One CNAME, no code
When you add a site we create the first-party hostname and show you the exact DNS record to add. No Cloudflare token and nothing to run on your server.
The record you add looks like this
- Type
- CNAME
- Name
- aabc.yoursite.com
- Target
- fp.antiadblockcore.com
- Proxy
- DNS only (grey cloud on Cloudflare)
Recommended, not required. The classic third-party tag keeps working while your DNS propagates, so you are never left without detection.
What you get with your own script
Your real ad-block rate
Detections, recoveries and recovery rate per site and per day, with the estimated revenue at stake from your own CPM.
An overlay that matches your brand
Logo, accent color, transparent or solid backdrop, your own title and body text, wall or dismissible. No design work needed.
Detection API when you want control
Headless mode: no overlay, just the result handed to your own JavaScript so your page decides what blocked users see.
Privacy-safe by design
No tracking cookies, no fingerprinting, no visitor identifiers. Our statistics keep daily aggregates only, designed for GDPR and CCPA.
Never blocks rendering
Loaded async with no dependencies, so it is never a render-blocking resource.
Installed in 60 seconds
One async script tag in your head. Works on WordPress, Blogger, Ghost, Webflow, Shopify, Next.js and plain HTML.
Measure your own ad-block rate this week
Free for 10,000 detections a month, no credit card, no traffic minimum. Install the tag in a few steps and watch your first real numbers arrive in real time.
Getting started FAQ
How do I try it on my own site?
Create a free account, verify your domain with a meta tag or a root file, choose first-party or third-party delivery, and paste the script tag into your head. The free plan covers 10,000 detections a month with no card, and the dashboard shows your data in real time, from your very first visitor.
What is first-party delivery and do I have to use it?
It serves the same script from a hostname on your own domain instead of ours, so ad-block filter lists that now target our third-party domain can't cancel it. It is the default and recommended, set up with one CNAME we generate for you. The classic third-party tag keeps working while DNS propagates, so it is not mandatory to start.
Do I need to write any code or run anything on my server?
No. You paste one async script tag into your head, the same way you would add analytics. For first-party you add one DNS record we show you. There is nothing to install on a server and no build step.
Is it really free, and is there a card required?
Yes. The free plan covers 10,000 detections a month with no credit card and no traffic minimum. You only move to a paid plan if you outgrow it.
Does it work on WordPress?
Yes. There is a WordPress plugin that installs the tag and connects your site in a couple of clicks, and the plain script tag works on any platform: Blogger, Ghost, Webflow, Shopify, Next.js or hand-written HTML.
Will it slow my site down?
No. The script loads asynchronously with no dependencies, so it is never a render-blocking resource.