Publisher & Advertiser

Bounce-and-fire patterns

Flags ad requests or clicks arriving with no genuine page view, or visitors leaving instantly after the ad fires.

Available actions

Block / Monitor

Example

Leaves within 1 second of the ad request

What it checks

Looks for ad requests or clicks that occur without a meaningful page visit, or sessions that end almost immediately after the ad event. The pattern can indicate automated firing or a placement that triggers before a real opportunity to view it.

Why it matters

Advertisers: Helps reduce spend on clicks that lack a credible visit or engagement context.

Publishers: Helps detect accidental or artificial ad firing that can lead to invalid-traffic concerns.

How to use it

Use a threshold suited to the page and ad format. Fast exits can be normal, especially on single-page answers or slow-loading pages, so combine this with other signals.

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.