What you are actually checking for
Three separate problems wear the same clothes. Misplacement is your ad appearing beside content you would not have chosen. Fraud is a publisher stacking, hiding or auto-refreshing placements so that impressions are billed and never seen. Cloaking is an affiliate showing the compliant landing page to you and something else entirely to real users.
All three are built to survive inspection, which means they are built to recognise inspectors. Requests from hosting ranges and from the address blocks used by verification vendors get shown the clean version.
Why residential addresses are not optional here
In most jobs a datacenter IP is merely more likely to be blocked. In ad verification it changes what you are shown, which is worse: you get a clean result and conclude everything is fine.
A residential address from a consumer ISP in the target country is indistinguishable from the audience being defrauded, which is the entire point. Rotating means each check comes from a different home connection, so a publisher cannot learn your addresses and start behaving.
Country, city and carrier
Ad delivery is geo-targeted, so verification has to be too. If you are buying in France, check from France; a Belgian address may see a different campaign or none at all. Where a campaign targets a city or a mobile audience specifically, match that as well — a desktop residential IP will not see a mobile-only placement.
A workable checking routine
- Check each market from inside it, on a rotating address, several times across the day rather than once.
- Capture the page, not a verdict. Screenshot and store the HTML; a dispute with a publisher is won with evidence, not with a row in a log.
- Follow the redirect chain to the end. Cloaking usually happens two or three hops in, not on the click URL you were given.
- Vary the referrer and user agent to match the placement being checked, since cloaking scripts read both.
Common questions
Why can't I verify ads from my office connection?
Because fraud and cloaking scripts recognise hosting ranges and known verification vendors and show them the compliant version. You get a clean result that does not describe what your audience sees.
Do I need residential proxies for ad verification?
Yes, more than in almost any other job. Here a datacenter address does not merely risk a block — it changes what is served, which means a false all-clear.
How much traffic does ad verification use?
Not much. Placements are page loads, so a few gigabytes a month covers most campaigns. Screenshotting with a full browser is the expensive part, and only if you load every asset.
Can I check ads in a specific city?
Country targeting is available across 50+ countries. Where a campaign is city or carrier specific, match that as closely as the pool allows — a desktop residential address will not see a mobile-only placement.
Try it before you pay for it
Connect Telegram and we credit 1 GB to your account — enough to measure your own traffic use on your own targets rather than trusting the numbers above. After that it is $0.70–$2.00 per gigabyte depending on volume, traffic never expires, and there is no monthly fee.