What ad verification is
Ad verification means checking that your ads appear where they should, look the way they should, and lead where they should. Advertisers and agencies verify:
- Placement: ads appear on the intended sites and apps, in the intended countries and cities.
- Creative: the right image, video, copy and offer are shown in each market.
- Landing pages and redirects: clicks lead to the correct page, without hijacked redirects.
- Brand safety: ads don't appear next to content you've excluded.
- Fraud and cloaking: publishers and affiliates aren't showing one thing to reviewers and another to real users.
All of this depends on seeing the web as real users in specific places see it. Ad systems and fraudsters both treat datacenter and corporate IPs differently from consumer connections. That's why verification relies on residential proxies, and why Geonode, with country, state, city and ASN targeting on its residential traffic, fits this work.
Settings for ad verification
| Setting | Recommendation | Why |
|---|---|---|
| Proxy type | Residential | Ad systems and cloakers treat consumer IPs as real users |
| Targeting | City or region matching the campaign; ASN to check specific ISPs | Ads are targeted by location and sometimes by carrier or ISP |
| Session | Sticky for the whole visit and redirect chain | The IP must not change between ad, click and landing page |
| Browser | A real browser, images and scripts on | Ads are images and scripts |
| Profile | Fresh profile per check | Avoid frequency caps and retargeting skewing results |
A verification workflow
- List the checks: campaign, placements, target locations, expected creative and landing URL.
- For each location, open a fresh browser profile through a sticky residential session in that city.
- Visit the placement (site or page where the ad should appear) and wait for ads to load.
- Capture evidence: a full-page screenshot, the ad's creative URL, and the time and exit location.
- Click through (or follow the ad's link programmatically) and record every redirect and the final landing page.
- Compare with expectations and flag mismatches.
Automate with Puppeteer or Playwright for scale. See Geonode with Puppeteer and Geonode with Playwright.
Detecting cloaking and malicious redirects
Cloaking means showing different content depending on who's looking. Fraudulent advertisers and compromised publishers use it to hide scams from ad reviewers while showing them to real users. Signs to look for:
- The landing page differs between a residential exit and a datacenter or office IP.
- Redirect chains vary by country, device or ISP.
- Content changes when the visitor arrives from an ad click versus a direct visit.
Running the same check from several residential locations, and from a datacenter IP for comparison, reveals most cloaking. Record full redirect chains for evidence.
Proxy tip: Before scaling, run a short pilot on your real targets with Geonode and record success rate, latency and GB per result. Our our complete Geonode guide explains which Geonode product to start with.
Checking mobile and carrier-specific ads
Some campaigns target mobile users or specific carriers. Emulate a mobile device in the browser, and use ASN targeting to exit through specific ISPs where you need to check carrier-specific delivery. For true carrier IPs, compare with a mobile proxy specialist if your checks require it.
Cost and scale
Ad verification loads full pages with images, so it uses more bandwidth per check than text scraping. Keep it efficient by limiting checks to the placements and locations that matter, sampling rather than checking every impression, and closing pages once evidence is captured. Geonode bills residential traffic per GB with no expiry, which suits verification work that peaks around campaign launches. See cheap proxies.
Good practice
- Don't click ads in ways that generate fraudulent charges for other advertisers. Verify your own campaigns, or use methods agreed with partners.
- Keep evidence organised by campaign, location and time.
- Share findings with publishers and ad networks through their official channels.
A sample verification schedule
For a campaign running in eight cities across two countries:
- Launch day: full check in every city: placements, creatives, click-through, landing page and redirect chain.
- Days two to seven: daily spot checks in three rotating cities, plus a redirect chain check in all cities.
- Ongoing: weekly spot checks, and immediate checks after any creative or landing page change.
- On alert: if click-through data or conversion rates drop in one market, run a full check there.
Store results in a shared folder per campaign, with screenshots named by city, date and placement. Geonode's city-targeted residential exits make each check a matter of minutes, and its non-expiring bandwidth suits launch-heavy schedules.
Reporting findings
When you find a problem, report it with evidence: screenshots, URLs, redirect chains, timestamps and exit locations. Publishers and ad networks act faster on clear, reproducible reports. For affiliate-driven campaigns, pair these checks with affiliate link testing.
FAQ
Why can't I verify ads from my office?
Your office IP, cookies and browsing history all affect which ads you see, and some fraudsters hide from corporate IPs. Residential exits and fresh profiles show what real users see.
Do I need city targeting?
If campaigns are targeted by city or region, yes. For national campaigns, country targeting is enough.
Should I use rotating or sticky sessions?
Sticky. The ad view, click and landing page must come from the same IP to reflect a real user's journey.
Can I automate ad verification?
Yes, with a headless browser, sticky residential sessions per check, screenshots and redirect logging.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.