Ad Verification Proxies

Cloaking defeats datacenter checks

Fraudulent networks detect datacenter ASNs and serve a clean creative. Verification from residential and mobile IPs is the only way to observe the ad a real user is served.

Breadth of geography matters more than volume

You need many countries, cities and carriers rather than huge bandwidth. Prioritise providers with deep ASN and city coverage over headline pool size.

Mobile carrier verification

In-app and mobile-web inventory is targeted by carrier. Verifying it requires real 4G/5G exits on the specific operator, not a residential IP on fixed broadband.

Verification, affiliate and media-buying workloads

Three related jobs share the same infrastructure. Ad verification checks that a paid placement rendered in the right geo, next to safe content, at the promised viewability. Affiliate and media-buying QA checks that a funnel, cloaker or tracking link behaves the same for a real consumer as it does for you. Traffic-arbitrage operators use the same viewpoints to see which creatives competitors are running in each market.

All three fail for the same reason when done from the office: your own IP and a datacenter IP both look nothing like the audience being targeted, and any half-competent cloaker serves them a compliant page.

Beating cloaking and geo-misdelivery

Cloaking scripts classify visitors by ASN, IP reputation, headless signals and referrer chain, then branch. Residential and mobile exits in the target market are the only viewpoints that consistently land on the branch a real user sees. Rotate the viewpoint — different city, different carrier, different device profile — because a single clean check proves nothing about a campaign that only misbehaves for mobile users in one region.

Capture evidence as you go: full-page screenshots, the complete redirect chain, response headers and the exit IP's geo and ASN. Without that record a violation report is an assertion, not proof.

Mobile and in-app inventory

In-app programmatic inventory is targeted by carrier and device, so verifying it needs real 4G/5G exits on the specific operator. A fixed-line residential IP with a mobile user-agent string does not reproduce carrier-targeted delivery, and the discrepancy will show up as false clean results.

Prioritise providers by carrier and city depth rather than headline pool size — breadth of viewpoints is the product here, not bandwidth.

PPC intelligence and competitor monitoring

Search and social ad auctions surface different advertisers by location and audience signals. Pinning the city gives you a genuine picture of who is bidding against you and what copy they run, and doing it on a schedule turns that into a competitive time series. Keep query rates modest — ad-serving endpoints rate-limit harder than organic ones.

How to choose a provider for ad verification

Start from the workload, not the price list. For ad verification the recommended class is residential and mobile, wide geo spread, with a medium traffic profile — that pair alone eliminates most of the market. Then score the shortlist on four things: measured success rate against your own targets, geographic and ASN granularity, session control, and the billing model.

Every credible provider offers a trial or a small pay-as-you-go tranche. Run the same hundred requests through each candidate, from the same client, against your real targets, and compare success rate and median latency. Vendor benchmarks are run on empty pools at favourable hours; yours will not be.

Finally, read the refund and expiry terms. Non-expiring traffic, prorated refunds and the ability to pause a plan are worth more than a 10% discount when workloads are seasonal.

Pricing and budgeting for ad verification

Three billing models dominate. Per-gigabyte pricing suits residential and mobile pools and rewards efficient clients that block images and analytics. Per-port or per-IP pricing suits static ISP, dedicated datacenter and mobile ports, and is the only sane model when one identity must hold one address. Per-request pricing, used by unlockers and scraper APIs, transfers the block risk to the vendor and is the cheapest option on genuinely hard targets.

Model the total, not the headline. Add failed-request overhead, the bandwidth your client wastes on assets you never parse, and the engineering time spent maintaining parsers. Efficiency work — response compression, asset blocking, conditional requests, aggressive caching — routinely halves a bill without changing provider.

Commit annually only after a full month of production traffic. Volume discounts are real, but so is the cost of being locked into a pool that turns out to be weak on your key geos.

Rotation, sessions and geo targeting in practice

Rotation policy should follow state. Stateless requests can take a new exit every time; anything with a login, a cart or a multi-step form needs a sticky session that outlives the flow. Most gateways support both concurrently, selected by port or by a session token in the username.

Geo targeting granularity matters more than pool size for most buyers. Country-level is table stakes; city, region, ZIP and ASN or carrier targeting are what let you reproduce a specific user's experience. Verify the targeting actually works by resolving the exit IP's geolocation against two independent databases — advertised coverage and delivered coverage diverge more often than vendors admit.

Common mistakes in ad verification setups

Buying on pool size alone. Headline IP counts are unaudited and include long-inactive peers; a smaller, well-maintained pool with good ASN diversity outperforms a bigger stale one on every hard target.

Rotating when you should be sticky, and sticky when you should be rotating. Both fail loudly — one as account-takeover challenges, the other as rate-limit blocks.

Ignoring the client fingerprint. A default HTTP library behind a premium residential IP is still detectable in the first packet.

No observability. Without per-target success rates, per-IP error codes and a cost-per-record metric, you cannot tell a provider problem from a code problem, and you will keep switching vendors instead of fixing the crawler.

Measuring success and knowing when to switch

Instrument four metrics from day one: success rate per target domain, median and p95 latency per exit country, cost per successful record, and ban half-life — how long a fresh IP survives on a given target. Together they tell you whether a degradation is the pool, the target's new defences, or your own code.

Set a review cadence. Re-benchmark the top three providers quarterly with the same script; pools shift as peers churn and vendors buy or lose supply. A provider that led a year ago is not automatically the right answer today, and switching is cheap when your crawler treats the gateway as configuration rather than architecture.