Ve tus anuncios exactamente como los ve tu audiencia.

What geo coverage costs per month

Ad verification is a small-traffic, wide-geography job, which flips the usual arithmetic. Blocking heavy assets keeps a checked page near 500 KB:

Residential wins here and it is not close. You need a real provider address inside each market, you need it only for seconds at a time, and 220+ countries come from one login instead of thirty separate purchases.

One session per market, held long enough to load the page

Give every country its own session id so a check runs start to finish through a single address. Fifteen minutes covers a page load plus screenshots:

Python: one session per market

COUNTRIES = ["US", "GB", "DE", "FR", "BR"]

def proxy_for(country, session_id):
    login = f"login_c_{country}_s_{session_id}_ttl_15m"
    return f"http://{login}:password@proxy.sotaproxy.com:10000"

for i, country in enumerate(COUNTRIES, start=1):
    proxy = proxy_for(country, i)
    r = requests.get("https://publisher.example/article",
                     proxies={"http": proxy, "https": proxy},
                     headers={"Accept-Language": LOCALES[country]},
                     timeout=30)

• Match Accept-Language to the country. A US address asking for pages in Russian tells the ad server you are not who you claim to be, and you will see the wrong creative.
• City targeting matters for local campaigns. Add _city_New-York when the buy is city-scoped, and drop back to country level if the pool returns a 400.
• Screenshot through the same session that loaded the page. A rotation between load and capture gives you a screenshot from another city.
• Run checks at the hours the campaign runs. Dayparting means the creative at 03:00 is not the creative at 19:00.

What quietly invalidates the whole report