Publisher & Advertiser

Automated browsers

Detects webdriver flags and headless user agents left by Selenium, Puppeteer or Playwright, revealing scripted rather than human visitors.

Available actions

Block / Monitor

What it checks

Looks for browser automation indicators, such as webdriver properties, headless-browser traits or user-agent patterns associated with scripted tools.

Why it matters

Advertisers: Helps stop scripts from loading ads or generating clicks that do not represent genuine prospects.

Publishers: Helps keep automated visits from inflating delivery and engagement metrics.

How to use it

Block only when detection confidence is high. QA tools, accessibility testing, monitoring services and legitimate automated workflows can use browser automation too.

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.