The right IP for the placement
Residential for web placements, mobile for in-app and mobile-web inventory, and static ISP when one fixed identity has to revisit the same publisher over time.
Get ad verification proxiesSee which product fitsSee your ads the way real users in each market see them — placement, creative, landing page and every redirect in between. Residential and mobile IPs targeted to the country, city or carrier the campaign buys, so cloaked and geo-specific ad fraud can't hide behind the fact that you're checking from an office.
How it works
Three things worth knowing about how ad verification actually works on this network, and what each one looks like from the inside.
Residential for web placements, mobile for in-app and mobile-web inventory, and static ISP when one fixed identity has to revisit the same publisher over time.
Get ad verification proxiesSee which product fitsCountry and city targeting on the residential and mobile pools, plus carrier ASN on Mobile, so a campaign bought in forty cities is verified from forty cities.
Get ad verification proxiesSee which product fitsHold a sticky session while a check follows an ad from impression to landing page, so every hop is fetched by the same visitor the fraud was targeting.
Get ad verification proxiesSee which product fitsHow it works
Residential for web placements, mobile for in-app and mobile-web inventory where the buyer is a phone, and static ISP when a fixed identity has to come back to the same publisher day after day.
Target the country, city or carrier the campaign actually bought. Geo-targeted fraud and misdelivery only show up from inside the market.
A new IP per request for broad crawls, or a sticky session for anything that needs to stay logged in or paginate as one identity — the same toggle on the residential and mobile pools.
Ad verification is confirming that an ad ran where, when and how it was bought: the right creative, on a brand-safe page, in the right country or city, reaching a landing page that is what the advertiser approved. Publishers, networks and verification vendors run these checks at scale; so do advertisers and agencies auditing their own spend.
The checks only mean something if they come from the audience's point of view. Ad servers decide what to show by location, device and network, and fraudsters use the same signals to cloak: show the clean creative to a reviewer and the malicious redirect to everyone else.
A check run from your office or a cloud server sees the version of the ad served to an office or a cloud server — which is exactly the version a cloaking scheme wants you to see. Datacenter ranges are well known, and bad actors routinely serve them a harmless page.
Residential and mobile IPs belong to real consumer connections, so the ad server treats the check as a member of the target audience. With country and city targeting, plus carrier ASN on mobile, you can reproduce what a viewer in each market gets, including region-specific creatives and landing pages.
Use rotating residential for broad sweeps across many publishers and locations — a fresh household IP per check keeps every request looking like a different viewer. Use mobile proxies for in-app and mobile-web inventory: they're real 4G and 5G carrier IPs, and targeting by ASN lets you check delivery on a specific carrier.
When a check has to follow a chain — impression, click tracker, one or more redirects, landing page — hold a sticky session so every hop comes from the same visitor. Static ISP addresses suit scheduled re-checks of the same placements, where one stable identity over days or weeks is the point.
Most verification tools and headless browsers accept an HTTP(S) or SOCKS5 proxy. Put the target country, city or ASN and the session length in the proxy username, run each market as its own job, and log the exit IP and location with every screenshot or capture so findings can be shown to the publisher or network.
Keep the checks proportionate: verification traffic should look like a handful of real viewers per placement, not a flood. Our acceptable use policy sets out what the network may and may not be used for.
Built for ad verification
Up to 250 MB of residential traffic with no card, country-to-city targeting on the residential pools, and rotating or sticky sessions set in the username.
The product capabilities that actually matter for this job, line by line.
Five products can carry ad verification traffic, each priced off the same live curve the dashboard charges from. Pick the one that fits the target.
Broad web-placement sweeps from inside each market.
In-app and mobile-web inventory, carrier by carrier.
Scheduled re-checks from one stable identity.
For networks that challenge the standard pool.
The Loopway standard
Every rate on this site is computed from the same price book checkout charges from. No hidden setup fees, no contracts, no sales call.
Top up once and spend it on any of the nine networks, whenever you need it. Unused balance stays in your account.
Sign up, pick a plan and your endpoint, username and password are live before the checkout tab closes.
HTTP, HTTPS and SOCKS5 on every product, plus UDP on UDP Residential and Static ISP. Point your stack at one host.
Rotate on every request or hold a sticky IP. Country, city, state and carrier targeting are set in the username.
Talk to people who run the network, not a ticket queue. Most questions are answered in minutes, any time of day.
FAQ
Can't find the answer? A real person is on chat around the clock, or find us here:
Ad servers and fraudsters both decide what to show by location and network. A check from an office or datacenter IP sees the version served to offices and datacenters; residential and mobile IPs see what the real audience in that market sees.
Residential for web placements and broad sweeps; mobile for in-app and mobile-web inventory, where the audience is on a carrier network. Residential targets by country and city (plus state on Premium); mobile by country, city or carrier ASN.
Yes — hold a sticky session for as long as the check needs, so the impression, click trackers, redirects and landing page are all fetched from the same IP.
Yes. Country and city targeting are included on the residential and mobile pools at no surcharge, with state targeting on Premium Residential and carrier ASN on Mobile, so results come back the way a real user in that market would see them.
No. Loopway is the proxy network your verification tool, headless browser or in-house checker runs through. Anything that accepts an HTTP(S) or SOCKS5 proxy works.
Ship it today
Your endpoint is live before the checkout tab closes. Start on the free residential trial, pay for what you use, keep what you don’t.