Advertiser & Publisher

Region and city targeting

Checks your target at region or city level. Useful for local campaigns and store offers.

Available actions

Block / Monitor

Example

Target: Texas. Flag visits outside TX

What it checks

Uses the visitor’s inferred location below country level, such as a state, region or city, to decide whether the visit matches the intended area.

Why it matters

Advertisers: Useful for local campaigns, store-radius alternatives and offers available only in selected markets.

Publishers: Helps validate local inventory packages and understand whether regional traffic matches what was sold.

How to use it

Start in monitor mode and allow for geolocation uncertainty. City-level IP data is less precise than country-level data and should not be treated as an exact physical location.

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.