Skip to content

Ad Verification Proxy Checklist: Geo, Device, Frequency

Six things to fix before each run so a check in one market can be repeated and compared with the next.

What are you checking?

Ad verification covers four different jobs: whether the ad is delivered in a market, what the creative and landing page look like there, how it renders on each device, and how often the same person would see it. Write down which of the four this run answers, because each needs different settings.

A proxy only changes the place your request comes from. The device, the browser language and the account you are logged in to are separate settings, and all of them show up in what you see.

Checklist: what to fix on each run

Checklist: what to fix on each run
ItemSet it toWrite it down
CountryThe market you are checking, using a country exitExit country and IP from an IP check
CityA city exit only when the campaign is targeted by cityThe city the IP check reports
LanguageThe browser language the real audience usesBrowser language setting
DeviceDesktop, mobile or tablet, matching the campaign's device targetingDevice and window size
FrequencyOne page load per market per checkTime and number of loads
EvidenceA full-page screenshot and the landing page URL after redirectsFile name with market, device and date

Location, language and device are the three filters Google lists for its ad preview tool (read 16 November 2026); the other rows are our working checklist.

Geo: country first, city only when needed

Start with a country exit. It is enough for language, currency and country-level targeting. Move to a city exit only when the campaign targets cities: on the Premium line you can choose state and city, while the Budget line takes a country only.

Rotating residential covers 195+ countries and regions and targets major cities, with no city level in Russia or Singapore, so some small towns exit at country level. Always read the exit back with an IP check before you trust a result.

Device and language

The proxy does not change the device. Google's tool lets you pick the device and the language for a preview; for a real page load, use the browser's own device mode and language setting and keep them the same from run to run. Change one variable at a time, or you will not know which one caused the difference.

Use a clean browser profile for checks, not the account you run your own campaigns from, so personalised results do not mix into the comparison.

Frequency: keep the sample small

Frequency capping limits how many times the same person sees an ad, and for Display campaigns only viewable impressions count. A check that reloads the page again and again can add exposures and distort the advertiser's numbers, which is why Google built a preview tool that avoids accumulating impressions.

Plan one load per market per check, space repeat checks out, and do not click ads that are not yours: a click can cost the advertiser money. If you must repeat a check from the same place, use a static IP or a sticky session so the repeat is comparable.

Which Proxy302 line fits

For checks across many countries, rotating residential is billed per GB: the Budget line is US$1.50 per GB and the Premium line US$5 per GB. The smallest purchase is 1 GB and there is no free trial.

For a repeat check that must come from one place, a static ISP IP costs US$0.50 for 1 day (US$7.99 for 30 days), and the same price applies in every country. Check availability by country on the order page.

Run one check in 6 steps

  1. Step 1: Write the plan

    Market, city (if any), device, language, the ad or landing page URL, and the question this run answers.

  2. Step 2: Generate the exit

    Open the rotating residential page, pick the line and country (city on Premium), and generate. Copy HOST, PORT, USERNAME and PASSWORD from My assets.

  3. Step 3: Read the exit back

    Open an IP check through the proxy and confirm the country and city.

    Expected result The country matches the market in your plan.

  4. Step 4: Set device and language

    Use the browser device mode and language setting from your plan, in a clean profile.

  5. Step 5: Load once and capture

    Load the ad or page once, take a full-page screenshot, and add a row to your log.

  6. Step 6: Repeat per market

    Change only the country (or only the device) for the next run, so differences have one explanation.

Evidence log: one row per run

market,city,device,language,exit_ip,loaded_at_utc,landing_url,screenshot
DE,Berlin,mobile,de,203.0.113.x,2026-11-16T09:00Z,https://example.com/de,de-mobile-1116.png

Example only: the IP shown is a documentation address, not a real exit.

If the result looks wrong

The ad does not appear in a market

Check Whether it is eligible there at all: budget, location settings and account rules decide that, not only your IP.

Fix Run the platform preview tool for the same location, language and device, then repeat once through the proxy at another time.

Stop when Two checks at different times and the preview tool all show nothing: ask the account owner instead of reloading.

The landing page shows the wrong language or currency

Check The browser language and the exit country.

Fix Set the language you planned, confirm the exit country, and load again once.

Stop when The exit country is right and the page still differs: record it as the result.

Each run gives a different result

Check Whether the exit IP changed between runs, and the time of day.

Fix Use a sticky session or a static IP for repeats and log the time of each load.

Stop when Results still differ with the same IP: the ad rotation is the cause, not the proxy.

The exit city differs from the one you chose

Check IP databases can disagree about the same IP.

Fix Read the city from two IP databases and note both.

Stop when Still wrong: open a ticket with the order number.

Ad verification proxy FAQ

Which proxy type is used for ad verification?

Residential exits are the usual choice for checking what a local audience sees, because the IPs belong to ordinary networks. Use rotating residential for many countries and a static IP when a repeat check must come from one place.

How many times should I load an ad?

Once per market per check. Frequency caps and impression counts are the advertiser's numbers, and Google's own preview tool exists to avoid adding impressions.

Do I need a city exit?

Only if the campaign is targeted by city. Otherwise a country exit is enough and cheaper.

Can a proxy guarantee I see the same ad as a customer?

No. Which ad is shown depends on budget, targeting, the account and the auction, so record what you saw and when instead of treating one load as proof.

Reference links

3
  1. Google Ads Help: Ad preview and diagnosis tool

    Official documentation · Confirmed on:

    Read 16 November 2026: the tool shows how an ad appears in search results and why it may not be showing; compared with searching yourself it avoids accumulating ad impressions and affecting performance statistics. Its update note says you can filter by location, language and device, and by audience.

  2. Google Ads Help: Use frequency capping

    Official documentation · Confirmed on:

    Read 16 November 2026: frequency capping limits how many times ads appear to the same person; it works in Display and Video campaigns; for Display only viewable impressions count toward the cap.

  3. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site, checked 16 November 2026: prices in US$ (1 PTC = US$1), lease terms, protocols and ports (HTTP 2222, SOCKS5 3333), what each product connects over, countries and city targeting, no free trial.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.