Ad blocker detection
Creates bait elements to see whether an ad blocker hides them.
In one line
Can guess whether you use an ad blocker, by checking if its bait ads vanish
Creates bait elements to see whether an ad blocker hides them.
Shows when someone uses content blockers, which also marks privacy tool users.
What it can and can't do
What the user does: Nothing. It happens when the page loads.
It can
- Check if a hidden bait element gets hidden or blocked
- Show a message asking you to turn off your blocker
- Count how many visitors use blockers
It cannot
- See which blocker you use for sure
- See your browser history or other add ons
- Turn your blocker off for you
- Be exact; privacy tools can fool the check
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | Create .adsbox style elements and read offsetHeight |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Script reads the value
- Value joins the fingerprint payload
Data you get
What comes back: Ad blocker detection
Shape: boolean
How often: per page
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
adBlockInstalled | boolean | None | Not listed | Not listed |
Technical limits
- Heuristic
The story
What it is
A site can quietly test whether you use an ad blocker.
For you
You never see the test. If it finds a blocker, you may get a message asking you to turn it off, a paywall or a block on the page.
For makers
Publishers do it to protect ad income and to push people to subscribe. Fraud and tracking tools also use it, because a blocker marks someone as a privacy tool user and adds to a device fingerprint.
Where you see it
| Type | Example | Apps |
|---|---|---|
| news | A news site shows 'Please turn off your ad blocker or subscribe' after the test. | Forbes, Wired |
| video | A free video site stops playing until you allow ads. | None named |
| games | A free browser game site shows an ad wall and counts blocked ads. | Poki, CrazyGames |
| ads | An ad network measures how many people block ads to know its true reach. | Google Ad Manager |
| security | A fraud tool treats a blocker as one more signal in a device profile. | None named |
| analytics | A publisher reports how many readers block ads in its audience stats. | None named |
Risks
- Singles out privacy users
- Used in fingerprints
Good uses and abuse
Legitimate uses
- Show a paywall message
Known abuse
- Singles out privacy tool users
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
A real example: LinkedIn
Collector key(s): signals.adBlockInstalled.
Related capabilities
Related
- APFC / DNA device fingerprint (abuse prevention features). Can collect about 48 device traits and send them in secret with later requests
Sources
- BrowserGate: how it works (48 feature table)
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
How well checked: Based on official documentation.