No KYC — no ID, no selfie, no documents · City, state and ZIP targeting on every plan
Language: English
Get started

Guide · ad verification

Proxies for ad checks by US city

Campaigns are bought by metro, DMA or ZIP radius. Here is a clean way to confirm that each market sees the right creative and the right landing page.

Last updated:

Quick answer

How do I check my ads in a specific US city?

Start with your ad platform's preview tool, which shows results for a chosen location without adding impressions. Then use a city IP from MetroProxies (from $0.50/GB, October 2026) to load your landing page as a local visitor sees it: redirects, prices, store and tax. Never click ads through a proxy. No KYC; crypto.

What should I check with a preview tool first?

For your own campaigns, start with Google Ads' Ad Preview and Diagnosis tool (or the equivalent in other ad platforms): it shows which of your ads appear for a chosen city and language, without adding impressions or clicks. It answers "is my ad eligible in Tucson?" faster and more cleanly than any proxy.

A local residential IP adds what preview tools cannot show: the landing page, redirects, currency and store details a real visitor in that city gets after the click.

How do I check the landing page city by city?

  1. Copy the final URL of the ad from your ad platform and add your own UTM parameters, for example utm_source=qa&utm_medium=proxy, so your analytics can filter the visits out.
  2. Open it through a city IP: USERNAME-country-us-state-az-city-tucson-session-tuc1-ttl-10 in a browser set to the HTTP port.
  3. Note what changes by market: headline, phone number (area code 520 in Tucson), store or service area, prices and tax, legal notices.
  4. Repeat for each target city, one session per city.

Keep page loads to a few samples per city and per check. Do not open the ad click URL itself: that creates billable clicks and skews your own campaign data.

Which local details are worth checking?

The city pages list the facts most landing pages localize:

  • Area codes: a Houston page should show a 713, 281, 832, 346 or 621 number, not a Dallas one.
  • Time zone: offers that end "at midnight" should use the visitor's zone; Phoenix does not observe daylight saving time.
  • Sales tax: the rate shown before checkout differs by state; Oregon has none.
  • State privacy notices: visitors from states with a privacy law in force, such as California or Texas, may get a different consent banner.

Each city page gives these values, with sources.

Where should I go next?

Get a local IP with change your IP to another city, compare markets with local price checks, and look up area codes and time zones on the city pages. More on the guides page.

What else do people ask about ad checks?

Can I check competitors' ads this way?

You can view public pages, but do not click competitors' ads: it costs them money and breaks ad platform rules. Search engines also prohibit automated access to their results pages, so check results by hand or use the platform's own transparency tools.

How much traffic does an ad check use?

A landing page loaded in a browser is often 2 to 8 MB. Ten cities, three loads each, is under 0.3 GB, well within the 1 GB plan ($1.50).

Can I check ZIP-radius campaigns?

Yes, add a ZIP inside and outside the radius: -zip-85701 for downtown Tucson, then a ZIP outside your radius. ZIP-level geolocation is approximate, so compare with what the landing page shows. See ZIP code targeting.

Sources (2)
  1. About the Ad Preview and Diagnosis tool — Google Ads Help (2026-10-18)
  2. NPA (area code) report — NANPA (2026-10-18)

1 GB $1.50 · no KYC

Get started