The dashboard says it served — someone still has to look from where it served
Ad verification and ad fraud detection
Placements are bought by geography, device and network type, so opening a landing page from the office rarely shows you the creative your audience was served. ZapIP runs ad verification through residential exits in 195 countries — confirming the creative rendered in the geo you paid for, that the landing page was not hijacked mid-redirect, and how much reported volume came from hosting networks.
- 195 countries and regions
- City, state & ASN targeting
- <0.6s average response
- 99.9% uptime
How it works
Confirm the ad ran where you bought it
You bought New York; which state it actually served in is not something the dashboard will tell you. The only way to know which creative was in rotation is to load the placement from that network yourself.
- State-level exits in the US to check state-by-state buys
- City and carrier targeting across 33 priority markets
- Native broadband ASNs, so the ad stack does not filter you out as a crawler
- No concurrency cap — one sweep can cover dozens of geos at once
How it works
Every hop in the redirect chain has to be visible
There are usually several hops between the creative and the landing page, and swapping any one of them puts someone else's page in front of your audience. That kind of hijack is normally scoped to one geo or one carrier.
- Sticky sessions up to 90 minutes to follow a full multi-hop chain and what follows it
- Exit by carrier to reproduce a hijack that only fires for one ASN
- HTTP(S) and SOCKS5 into headless browsers and screenshot capture pipelines
- Rotation from 1 to 360 minutes so verification nodes do not become recognisable
How it works
Separate hosting traffic from real impressions
Ad fraud work is comparative: you need to know how a placement behaves for a genuine consumer network versus a suspicious one. Without real residential exits there is no control group to compare against.
- 90M+ residential IPs where reverse ASN and WHOIS both read residential
- Continuous reputation checks keep flagged addresses out of your sample
- 99.9% request success leaves fewer gaps in data used for billing disputes
- Long-term static IPs give a fixed control point for tracking one placement over time
Coverage
One network behind all four products — changing the billing model does not change how you connect or how you target.
All 33 markets- 195 countries & regions
- Available
- All 50 US states
- Available
- City-level targeting
- Precise
- ISP & ASN targeting
- Supported
4 billing models
How this is billed
All four billing models share one network. Short bursts go per GB, pipelines that run continuously go per Mbps, and anything tied to an account identity goes per IP-day or per IP-month.
FAQ
Questions about this solution
Why does ad verification require residential IPs?
Because ad platforms and anti-fraud systems both filter by network type. Requests from hosting ranges are either excluded from the auction or served a fallback creative, so what you verify is not what ran. A residential exit looks like an ordinary consumer to the ad stack, which is the only way to see the creative that actually won the impression.
Can I verify city-level or state-level targeting?
Yes. Thirty-three priority markets support city and ASN targeting, and the US adds state. State matters in the US in particular: a lot of local-service inventory is bought state by state, spill across a border is wasted budget, and most reporting only aggregates to country level.
For ad fraud detection, should I use rotating or static IPs?
Both. Broad sweeps run on rotating residential so the exit keeps changing and nobody can feed your known addresses a clean creative. When you are tracking one suspicious placement or redirect chain over weeks, add a long-term static IP or two as fixed control points so readings stay comparable across time.
Will verification traffic count as impressions or clicks and skew campaign data?
Any automated visit can register as an impression or a click, so keep the sweep's frequency and behaviour deliberate, and where possible arrange exclusion rules with the ad platform itself. ZapIP supplies network exits and holds no partnership or authorisation from any ad platform named here; designing verification that does not pollute your own reporting sits on the campaign side, though our engineers can help tune rotation and session policy at the proxy layer.
Get one request working. Scale after that.
Test before you commit, with an engineer on your integration.