Publisher & Advertiser

Language vs. country mismatch

Flags visitors whose browser language is unlikely for their IP's country, a signal of spoofed location or non-genuine traffic.

Available actions

Block / Monitor

Example

Flag zh-CN browsers on Brazilian IPs

What it checks

Compares the browser’s preferred language with the country inferred from the connection. Some combinations may be unusual for your audience, but language and nationality are not the same thing.

Why it matters

Advertisers: Provides supporting evidence when checking whether traffic genuinely matches a campaign’s intended market.

Publishers: Can help spot patterns in suspicious traffic, but has limited value as a standalone blocking rule.

How to use it

Treat this as a contextual signal. Multilingual users, expatriates, tourists and people using translated browsers commonly have a language that differs from their current country.

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.