Google Ads Proxy

What is a Google Ads proxy used for?

A Google Ads proxy lets you run campaign-related checks from an IP address in a specific country, city or carrier network instead of your own connection. The target site and Google see the request coming from that IP. A proxy changes only the network layer; it does not change account settings, ad approval status or your browser fingerprint.

In practice, a Google Ads proxy is used for these legitimate tasks:

• Landing page QA per country. Checking that the landing page of a campaign targeting Germany opens in German, shows prices in euros, sends geo-redirects to the right page and displays the expected regional price.
• Final URL and tracking template checks. Confirming that the final URL, tracking template and redirect chain end on the correct page in every target country.
• Competitor ad research. Reviewing competitor ads in Google's official Ads Transparency Center and visiting those ads' landing pages directly from the target country.
• Stable-IP access for agency teams. Keeping the sign-in location consistent for team members who access client accounts from different cities.

For the general framework of ad verification projects, see the ad verification use case page. Tracking organic search results by country is covered on the Google proxy page, and jobs that need IPv6 capacity on the Google Ads IPv6 proxy page.

Proxy or Ad Preview tool: how do I see my own ad?

To check whether your ad appears for a given location, language and device, the first choice is the Ad Preview and Diagnosis tool inside Google Ads. It simulates Google search results for the location, language and device you pick, does not generate impressions and tells you why an ad is not showing.

Searching for your own ad on Google again and again accumulates impressions without clicks and can eventually stop the ad from being shown to you. Searching through a proxy does not solve this; the IP is different, but the impression is still recorded against your campaign.

A proxy adds value not at the ad itself but at the step after the ad:

When serving ads, Google determines location not only from the IP address but also from the campaign's location option ("presence or interest" / "presence") and other signals. A proxy IP is therefore not a definitive indicator of whether a user will see an ad.

Which proxy type should I choose for Google Ads work?

The choice depends on whether the job needs a session. When someone signs in to a Google Ads account, the IP should stay fixed. For landing page and redirect checks, one IP per target country is enough.

Datacenter IPs are not recommended for account access. These addresses are registered to hosting companies' ASNs, and Google may ask for extra verification more often on sign-ins from those ranges. For the difference between sticky and rotating sessions, see the sticky vs rotating proxy guide.

How do I test a landing page per country?

If a campaign targets more than one country, run a separate checklist for each country. Do every check through a sticky session in the target country, and keep the IP unchanged until the check is finished.

Which fields should I check?

1. Language. Does the page open in the target country's language? If the Accept-Language header and the IP's country give different results, which one does the site prioritize?
2. Currency and price. Is the price in the local currency? Does the price or offer in the ad text match the page?
3. Geo-redirects. If the site redirects by IP to another subdomain or language folder, is the final address on the same domain as the ad's final URL?
4. Availability. Does the page return 200 from the target country, or do you get a regional block, a 403 or a cookie wall?
5. Legal notices. Do the cookie consent banner in EU countries and mandatory warnings in some industries appear?

How do I see the redirect chain from the command line?

You can see the redirect chain without clicking the ad by requesting the final URL directly from an IP in the target country:

curl -sIL -x "http://USER:PASSWORD@HOST:PORT" \
  -H "Accept-Language: de-DE,de;q=0.9" \
  "https://www.example.com/kampanya?utm_source=google" | grep -iE "^(HTTP|location)"

The output shows each step's status code (301, 302, 200) and its Location header. The chain should end with 200 and the correct language page. For location selection and ASN targeting, see the proxy geo-targeting guide.

How do I check a tracking template?

Google Ads lets you test the tracking template in the URL options; that is where the first check belongs. In an additional check through a proxy, you paste the URL the template resolves to into a browser and open it from the target country to see whether the third-party tracking server is blocked in that region. With parallel tracking, users go straight to the final URL while the tracking request runs in the background, so the final URL has to reach the correct page on its own.

How should I record the results?

For each check, record the date, country, exit IP, final URL, status code, displayed currency and a screenshot. When you repeat the same check weekly, you can spot a site update that breaks a redirect in one country before campaign performance drops. Pass issues to the web team together with the country and IP they were seen from; without that information, geo-specific bugs are often impossible to reproduce.

How can I research competitor ads?

The official source for competitor ads is the Google Ads Transparency Center. There you can filter by advertiser, region and format and see an advertiser's running ads. No proxy is needed for this.

A proxy's role here is to visit a landing page you found in the Transparency Center directly from the target country. For example, you can compare a competitor's price in Türkiye with its price in Germany using one residential IP from each country. Clicking a competitor's ad in the search results, on the other hand, costs the competitor money and is invalid traffic; always go to the landing page through its address.

How do agency teams access client accounts from a stable IP?

The correct way for agencies to access client accounts is a Google Ads manager account (MCC) with personal user invitations. Account passwords should not be shared within the team; every user should have their own Google account and 2-Step Verification.

A static IP complements this setup. When a remote team member signs in from a different home, café or mobile network each time, Google may detect a sign-in from a new location and ask for extra verification. When each user gets their own static IP, the sign-in location stays consistent and such unexpected prompts can become less frequent.

These rules work in practice:

• One IP per user. Do not share a static IP between several people; access logs should stay tied to a person.
• Match the country to the office. Choose a Türkiye IP for a team in Türkiye. WeProxy Türkiye static residential IPs come from the Türk Telekom and Vodafone networks; they support HTTP and SOCKS5, and there is no UDP support in Türkiye.
• Keep timezone and language consistent. The browser's timezone and language should match the IP's country.
• Do not change the IP. A static IP stays the same for the package period; changing IPs often defeats the purpose of a static IP.
• Close leaks. Follow the steps in the DNS and WebRTC leak guide so your real IP is not exposed via WebRTC or DNS.

For the difference between static residential and ISP proxies, see the residential vs mobile vs datacenter vs ISP proxy comparison.

How do I set up a Google Ads proxy?

1. Choose the product. For per-country landing page checks, choose Rotating Residential IPv4 or Premium Rotating Residential; for team access, choose Static Residential IPv4.
2. Buy in the panel. Purchase the package in the customer panel. Host, port, username and password appear in the panel; you can also authorize with an IP whitelist. All packages have unlimited threads and concurrent sessions.
3. Enter it in your tool. In your browser profile, testing tool or script, set the proxy type (HTTP or SOCKS5), host, port, username and password. To convert between formats, use the proxy format converter.
4. Verify the exit. Check in the My IP tool that the IP, country and carrier are what you expect. A quick check from the command line:

curl -x "http://USER:PASSWORD@HOST:PORT" https://api.ipify.org

1. Run the first test. Open a campaign's final URL from the target country and tick off language, currency and the redirect chain against your checklist. If you get a connection error, see the 407 and timeout sections of the proxy error codes guide.

Which rules and limits apply when using a Google Ads proxy?

Clicking ads through proxies or bots is invalid traffic. These clicks cost the advertiser money, can be detected by Google's invalid traffic systems, and accounts that generate or benefit from this traffic can be suspended. Opening new accounts to replace a suspended one and showing ad review systems different content than users see (cloaking) are prohibited under "circumventing systems" in the Google Ads policies. Using a proxy does not make any of this compliant.

What a proxy cannot do:

• It has no influence on ad approval, account security or suspension decisions and does not guarantee any outcome.
• It does not reinstate a suspended account; the way to do that is Google's official appeal process.
• It does not show definitively whether an ad will be shown to a user; use the Ad Preview and Diagnosis tool for that.

The purposes for which WeProxy services may be used are set out in the acceptable use policy.