Advertiser & Publisher

Cookies or storage disabled

Detects visitors who block or reject cookies and local storage, making retargeting impossible and the click of little value.

Available actions

Block / Monitor

What it checks

Detects whether browser cookies or local storage are unavailable to the page. This may be caused by browser settings, consent choices, privacy protections or technical restrictions.

Why it matters

Advertisers: Relevant when a campaign depends on storage for frequency capping, attribution or retargeting. It does not mean the visit is invalid.

Publishers: Useful for understanding measurement and monetisation limitations, but generally not a reason to block access to inventory.

How to use it

Prefer monitoring and adapt measurement expectations. Respect consent choices and do not treat privacy settings as evidence of fraud.

Frequently asked questions

What are AdPurify rules?

Rules are checks that run on each visit. In monitor mode, AdPurify records a match while the ad tag continues to run. In publisher blocking mode, a matching blocking rule prevents the wrapped ad tag from loading.

Can I use different rules per tag?

Yes. Each wrapped slot has its own rule set.

How many rules can I use?

Lite allows 3 active rules per slot. Professional and Enterprise allow unlimited rules.

How does AdPurify prevent false positives?

Traffic classification is probabilistic, so no signal should be treated as perfect proof on its own. Start every new rule in Monitor-only mode, review matched traffic, then tune that rule's sensitivity before enabling blocking. You can tune rules individually across 30+ checks and use narrow allowlists for trusted IPs, networks or known services.