Publisher & Advertiser

Timezone vs. IP mismatch

Compares the browser's timezone with the IP's geolocation and flags visitors whose two signals disagree, suggesting proxies or spoofing.

Available actions

Block / Monitor

Example

Flag if offset differs by more than 3 hours

What it checks

Compares the timezone reported by the visitor’s browser with the timezone expected from the IP geolocation. A large difference can indicate a proxy, spoofed location or unusual device configuration.

Why it matters

Advertisers: Adds a useful warning when validating location-sensitive campaigns and detecting traffic that may be disguising its origin.

Publishers: Helps investigate suspicious geographic patterns, but is not usually a reason to block by itself.

How to use it

Monitor first and use a sensible tolerance. Travellers, remote workers, misconfigured devices and privacy tools can all produce legitimate mismatches.

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.