How to Verify Geo-Targeted Ads Are Actually Showing the Right Creative in the Right City

Ad platforms let you set geo-targeting at the campaign level, but what actually renders for a user in a given city depends on more than your targeting settings — creative rotation, competing bids, local inventory, and platform-side serving logic all affect what a real person in that city sees. The only way to know for certain is to actually look from an IP that's really located there.

What silently goes wrong without verification

• →The wrong creative variant serving in a city where a locally-relevant version was supposed to run
• →Pricing or promo copy that's stale or mismatched to a local campaign that launched or changed on the platform side without your team seeing it directly
• →A competitor outbidding you in a specific metro while your dashboard still shows the campaign as "delivering normally" nationally
• →Landing pages that don't localize correctly for users arriving from a specific city, even when the ad itself is correct

None of these show up in the ad platform's own reporting, because the platform is reporting on delivery and spend, not on what a real user in a real city actually saw when the ad rendered.

What real verification looks like

1. 1Route a request through a residential IP genuinely located in each target city — not just the target country
2. 2Load the ad (or the platform surface it appears on) exactly as a user in that city would, including any city-dependent personalization
3. 3Screenshot or log what actually renders — creative, price, landing page — per city, on a recurring schedule rather than a one-time check
4. 4Compare across cities in the same campaign to catch inconsistencies that a single-market check would miss entirely

This only works if the targeting is real city-level targeting, not an approximation — a proxy that claims a city but is actually serving the nearest available IP in the country will show you the wrong thing and you won't know it's wrong.