Ad verification · Residential recommended

Proxies for ad verification, see what your budget actually buys.

Ad networks target by geography, device and connection type, and fraudsters serve clean creatives to anything that looks like a verifier. To see the placement a real user in Madrid on Movistar gets, you have to be that user: a residential or mobile exit in Madrid, with the matching device profile.

Get started See the recipe
  • $2.45GBResidential proxies, our recommendation for this job
  • $86.78per monthEstimate for 20,000 loads at 2500 KB each
  • 24 hstickyHold a pool exit from a minute to a day when the flow needs it
  • ∞threadsNo concurrency cap on any network; pace per domain yourself

01 — Which network

Residential proxies first. Here is the reasoning for all four.

A recommendation is only useful with its trade-offs. The cards below say what each network does well for ad verification, and where it stops being worth the money.

Residential proxies

Recommended

Household exits by country and city reproduce desktop and mobile-web placements as the audience sees them.

$2.45/GBnever expires · same rate worldwide
Residential proxies

Mobile proxies

Recommended

In-app and carrier-targeted campaigns require a real carrier IP; dedicated devices let you check one carrier repeatedly.

$2.62/GBrotating · devices priced by country
Mobile proxies

ISP proxies

Possible

Stable IPs are recognizable over time; only for verifying your own publisher inventory.

$0.99/IP/mo90-day term, reference zone · unlimited threads
ISP proxies

Datacenter proxies

Not suited

Ad networks classify hosting ranges instantly and serve nothing, or a decoy.

$0.70/IP/mo90-day term, reference zone · unlimited threads
Datacenter proxies

02 — The recipe

How to configure it.

The settings that matter for ad verification, and a working example on the right. Replace USER and PASS with the credentials issued at signup.

Rotation
Rotating for coverage across many households; sticky when a placement depends on a session.
Targeting
-cc- and -city- to match the campaign geo; -asn- to check a specific provider; carrier selection on mobile.
Device
Pair the exit with a matching user agent and viewport; a mobile IP with a desktop browser is a red flag.
Evidence
Capture screenshot, final URL and redirect chain with the exit details for every check.
Node.js (Puppeteer) 
// Madrid household, held 10 minutes so the whole page (and its ad calls) share one IP
const browser = await puppeteer.launch({
  args: ["--proxy-server=http://res.proxshift.com:9000"],
});
const page = await browser.newPage();
await page.authenticate({ username: "USER-cc-es-city-madrid-sid-ver07-ttl-10m", password: "PASS" });
await page.goto(publisherUrl, { waitUntil: "networkidle2" });
await page.screenshot({ path: "madrid-placement.png", fullPage: true });
cc
Country of the exit; add city or asn to narrow.
sid
Any string you choose; requests with the same session ID share one IP.
ttl
How long the session holds the IP, up to 24h; omit to rotate per request.

03 — Budget

What ad verification costs at your volume.

Per-GB pricing is predictable once you know your page size. Enter your monthly volume; the average size is pre-filled with a realistic figure for this job and can be changed.

loads
KB

full page with creatives (images, scripts)

Traffic47.7 GBper month
Rate$1.82per GB on the residential ladder
Estimated cost$86.78traffic never expires

Residential rate ladder, identical in every country. Buying the month's traffic in one purchase reaches the tier shown; smaller top-ups are priced at their own tier. Full ladder.

04 — Best practices

Where ad verification goes wrong, and how not to.

The pool is rarely the problem. These four habits decide the success rate and the bill.

Verify from the real audience

Country, city, device and carrier must match the campaign; anything else verifies a placement nobody sees.

Hold the session for the page

Ad calls fire after the HTML; keep one exit for the whole load so the chain is consistent.

Check the chain, not just the pixel

Record every redirect to catch cloaking and affiliate hijacks.

Sample over time

Fraud rotates; spread checks across hours and days rather than one sweep.

05 — Questions

Straight answers about proxies for ad verification.

Residential or mobile for ad verification?

Residential for desktop and mobile-web placements; mobile for in-app inventory and carrier-targeted campaigns. Many teams run both.

How much traffic does a verification load use?

A full page with creatives is 2 to 4 MB. Twenty thousand loads at 2.5 MB is about 50 GB, roughly $87 on the residential ladder.

Can I verify on a specific carrier?

Yes: pick the country and carrier on the mobile pool, or rent a dedicated device on that carrier for repeated checks.

Can I use headless browsers?

Yes. Authenticate the proxy in the browser and keep a sticky session for the page load so the HTML and the ad calls share one exit.

Ready when you are

Run ad verification on the right network today.

Create your account, top up $10 and try the recipe above on your real target. What you do not use stays on your balance.

Create an account Residential proxies