An ad account does not show you what a real user sees. Moderation, auction bids, creative rotation and even whether an ad is shown at all depend on the visitor's geo — and from your own office you are not physically present in any target region. Here is why a local viewpoint matters, what distortion a datacenter IP causes, and how to make the check repeatable.
Why look at the output through a local user's eyes
An ad platform personalizes what it shows based on dozens of signals, and geo is one of the heaviest. The dashboard shows an uploaded creative and an "active" status, but that is no guarantee a visitor in Munich or Jakarta sees that exact banner: they might get a different A/B variant, a stale cached version, or a competitor's ad that won the auction that second. The only way to check the actual output is to open the feed from an address classified as a local resident.
The same applies to the landing page: a click from the target country can lead to a localized page with local currency prices, while a click from another geo lands on the default international page. That difference is only visible on a live click from the matching region.
How creatives and bids differ by country and region
The same account runs parallel campaigns with different costs per impression, rotation frequency and set of active creatives per country. In a competitive segment the system drops weak variants faster, so ads still running by Friday evening in one region may not match another. Bids are not an abstract dashboard number either — the auction runs by different rules for a user in an expensive market than for one in a low-competition region, which decides whose creative wins the impression.
Differences show up within one country too: a major city and a rural area can get different banners because of local tests or a budget limited to one segment. A single checkpoint is not the whole geo.
Confirming that an ad is actually shown in the target geo
The basic question is not "what does the ad look like" but "is it shown at all." Moderation sometimes approves a creative formally but limits its display in some regions because of local topic restrictions or targeting set broader than it actually works. Logging in under an IP of each target geo and confirming the ad genuinely appears in the feed is the only way to close this without trusting the "approved" status in the dashboard.
The same goes for timing: a campaign with schedule limits can misapply the time zone, so an ad meant for the target country's prime time actually goes out at night by local time.
Why a datacenter address distorts the picture
An ad and antifraud system reads a datacenter IP within a fraction of a second: the ASN belongs to a hosting provider, not a home carrier or mobile network. Some platforms then skip personalization and show a neutral default ad set; others flag the session as suspicious and serve stripped-down content. Either way, what you see does not match what a real user on a home or mobile address gets. See what an ASN is and why it matters.
Checking ads requires a residential or mobile address in the target country — only that matches the campaign's actual audience, as covered in mobile versus residential proxies. Check address reputation too: a high fraud score means some platforms will greet the session with a captcha before personalization even kicks in.
How often to measure and what to record
A one-off check only answers "is the ad working right now." Rotation, competitor bid changes and moderation updates happen continuously, so value comes from checks run with the same method: same geo list, same time of day in the local zone, same click-through scenario. For a campaign spanning several countries, a reasonable cadence is once every one or two days per active geo, recording a screenshot of the feed, the landing page version and, where available, the ad copy.
Save every check with a date, country and address-type label — otherwise a real change is indistinguishable from a fluke a month later. A thousand text pages cost roughly 1 GB, a hundred image cards about 0.3–0.5 GB.
Frequently Asked Questions
Is one address per country enough, or do I need several?
One stable address per geo is usually enough for a single control point, but if a campaign targets a specific city, check from several addresses — rotation reveals whether output differs within the geo itself.
Can I check ads with a mobile proxy instead of a residential one?
Yes, and for some platforms a mobile address reflects what a phone user sees even more accurately, since a large share of impressions happen in the app rather than the browser.
How often does the set of shown creatives change?
It depends on budget and settings: aggressive rotation can refresh the active set several times a day, so a check should be tied to a specific hour, not just a date.
Residential and mobile addresses for checking ads by country are available in the proxy section.