Advertisers pay for impressions in specific markets, on specific devices, often on specific mobile networks. Verifying that those ads actually appear, look right and land on the right page means viewing them from the same places your audience does. Proxies for ad verification make that possible: you route checks through residential and mobile IPs in the target country, city or carrier and record what a real user would see.
What Ad Verification Checks For
- Geo-targeting: is the campaign actually showing in the countries and cities you paid for, and not elsewhere?
- Creative and landing pages: does the ad render correctly, in the right language, and land on the correct localised page?
- Redirect chains: does the click path go through the expected tracking hops, or is it hijacked to an unrelated or malicious site?
- Brand safety: what content is the ad appearing next to on publisher sites?
- Affiliate compliance: are partners sending traffic the way your agreement says?
Fraudsters and malicious ad networks often show clean content to known datacenter and corporate IPs and the bad version only to ordinary users. That is the main reason verification traffic needs to come from real residential and mobile networks.
Geo-Targeting: Country and City
Start with the country. With NodeProxies you add it to the username, for example USERNAME-country-fr for France. For city-level campaigns, residential plans support state and city targeting such as USERNAME-country-us-state-NY1-city-NYC1. Run the same check across each market in your campaign and compare: missing placements or the wrong creative in one market usually point to a targeting or trafficking error.
Residential IPs cover 195+ countries and mobile IPs 50+ countries, so most campaign markets can be checked from inside the market itself rather than approximated from a neighbouring one.
Carrier Checks With ASN Targeting
Mobile campaigns are often bought by carrier, and some fraud only appears on specific mobile networks. An ASN (autonomous system number) identifies the network an IP belongs to, so targeting an ASN lets you test as a subscriber of that ISP or carrier. In NodeProxies, the ISP or carrier also goes in the username:
# A US check routed through a specific carrier network
http://USERNAME-country-us-asn-VZ1:[email protected]:8080See the documentation for the targeting options available on your plan. Comparing the same placement across two or three carriers in one country is a quick way to spot carrier-specific redirects or missing impressions.
Mobile vs Residential Proxies for Ad Verification
- Mobile proxies (4G/5G, 50+ countries) are the right tool for mobile web and in-app campaigns, carrier-targeted buys and any check where the ad server treats mobile network traffic differently. From $1.10/GB.
- Residential proxies suit desktop and home Wi-Fi audiences, and they are the option with city targeting. From $0.65/GB.
- Datacenter IPs are exactly what cloaking systems are built to recognise, so they are not suitable for verification, though they are fine for internal monitoring of your own landing page uptime.
Match the device to the network as well: a mobile carrier IP paired with a desktop user agent is an unusual combination that some ad servers will treat differently. Use a mobile browser profile or device emulation for mobile checks.
Following Redirect Chains on One IP
A click path may pass through several tracking domains before landing. To see the whole chain as one user would, keep the same IP for the full check with a short sticky session, then switch to a new session for the next check. This Python snippet records each hop:
import requests
PROXY = 'http://USERNAME-country-gb-session-adcheck1-time-5:[email protected]:8080'
UA = 'Mozilla/5.0 (iPhone; CPU iPhone OS 17_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.4 Mobile/15E148 Safari/604.1'
r = requests.get('https://ads.example.com/click?id=123',
headers={'User-Agent': UA},
proxies={'http': PROXY, 'https': PROXY},
timeout=30)
for hop in r.history:
print(hop.status_code, hop.url)
print('final:', r.status_code, r.url)This catches HTTP redirects. JavaScript and meta-refresh redirects only show up in a real browser, so for full verification run the same sticky proxy through a headless browser and take a screenshot of the landing page. Our web scraping guide covers headless setups.
Building a Repeatable Verification Routine
- List each campaign's target markets, devices and carriers.
- For each combination, open a fresh sticky session with the matching country, city or ASN.
- Load the placement, screenshot the ad, then follow the click and record the redirect chain and final URL.
- Compare against the expected creative and landing page; flag differences.
- Repeat on a schedule and at different times of day, since some cloaking only activates at certain hours.
Ad Verification With NodeProxies
- Register without ID verification and add balance from $3 by card or crypto.
- Buy mobile and residential plans to cover your device mix; both are pay as you go with no expiry on balance.
- Build usernames with country, city or ASN targeting using the proxy username builder.
- Check per-GB rates for each product on the pricing page.
FAQ
Why are proxies needed for ad verification?
Ads are targeted by location, device and network, and malicious actors often hide bad behaviour from datacenter and corporate IPs. Residential and mobile proxies let you see what real users in each market see.
What is ASN targeting?
An ASN identifies the network an IP belongs to, such as a specific ISP or mobile carrier. ASN targeting routes your request through that network so you can check carrier-specific campaigns.
Mobile or residential proxies for ad verification?
Use mobile proxies for mobile and carrier-targeted campaigns and residential proxies for desktop audiences and city-level checks. Most verification setups use both.
How do I check if an ad is showing in another country?
Load the placement through a proxy in that country with a matching browser language and device profile, then screenshot the ad and follow the click. Repeat at different times of day, because delivery and cloaking can vary by hour.
