Proxy Location Targeting: Country, Region and City

Country, region and city work for residential and mobile proxies, on the same gateway and port.

No. City and state targeting cost nothing extra at ProxyField: the same $2.95/GB for 1 GB down to $1.95/GB from 1,000 GB, whether you target a country, a state or a city. There is no surcharge for a region or a city, and none for countries, requests or threads. You pay only for the traffic you use, at the rate of your purchase's volume tier, which applies to the whole purchase:

The same 10 GB purchase, priced by targeting level:

The smallest purchase is 1 GB, there is no subscription, the traffic never expires, and all purchases are final. No annual contracts, no monthly minimums, no auto-renewals, and ordinary purchases need no identity verification.

Where "extra cost" can hide with a provider, and what ProxyField does:

From 1 TB the price is individual: contact sales. Nothing about targeting is billed separately; the products sold per IP, dedicated ISP proxies and datacenter proxies, are priced per IP for 30 days instead of per GB. The full table is on the pricing page.

Yes, the location is set in the username. Username formats differ from provider to provider; ProxyField's order is login, country, region, city, session, ttl, and every part after the login is optional.

1. Copy your credentials. Your login, password and the configurator (it generates as many proxy lines as you need) are in your ProxyField account.
2. Point your tool at the gateway: host gate.proxyfield.io, port 7000. HTTP, HTTPS and SOCKS5 all use this host and port with the same username and password.
3. Add the country to your login: <login>-country-de. Requests now exit from Germany.
4. Add a region or a city after the country: <login>-country-us-region-california for California, <login>-country-us-city-<city> for a city, with its name from the list in your dashboard. Names are lowercase, with underscores for spaces and hyphens.
5. Add a session if you need one IP for a while: -session-<id>-ttl-<seconds> at the end.
6. Run the two curl lines at the top of this page with your username: the first prints the exit IP, the second asks ipinfo.io, an IP geolocation service, where that IP is ("city": "New York", "region": "New York", "country": "US" when the target matches). Databases disagree at city level, so check the target site's own view too.

To move to another location, change only the username; the host, port and password stay the same.

The full list of region and city names for each country is in your dashboard.

The full proxy line has the form host:port:username:password, for example gate.proxyfield.io:7000:<login>-country-au-region-australian_capital_territory-city-canberra-session-he9f2qga-ttl-60:<password>.

Your tool sends each request to one address, gate.proxyfield.io:7000, and the username tells the gateway where the request should come out. The gateway forwards the request through an exit IP registered in that place, and the target website sees only that IP. It then serves the page it serves local visitors: their language, currency, prices, search results and ads.

In rotating mode the exit IP changes on every request, and every new IP comes from the location in your username. That keeps a scrape spread over many addresses in the same market. Mobile proxies have the same targeting as residential; how the username selects mobile instead of residential is residential by default; add -mobile after the login for mobile IPs, as in <login>-mobile-country-us.

Country targeting is the right level for most jobs. It draws on the whole national pool, so you get the widest choice of IPs, and it is enough wherever a site changes its content by country only. Every country takes its two-letter code in lowercase, as in <login>-country-de. The coverage per country, such as 61.2M+ residential IPs in the United States, is on the proxy locations page.

Region targeting narrows the exit to a state or province, and in the United States it covers all 50 states. Use it when prices, taxes, delivery options, laws or search results differ from one state to the next. The region follows the country, its name in lowercase with underscores for spaces: <login>-country-us-region-new_york exits in New York State, <login>-country-us-region-california in California, and <login>-country-au-region-australian_capital_territory in the Australian Capital Territory. All 50 US states are covered; region names outside the US: the full list is in your dashboard.

The city follows the country, or the region if you set one: <login>-country-us-city-new_york exits in New York. City targeting covers 21,000+ cities in total. These are the city counts for ten markets:

When no IP is available in a city at the moment, the gateway answers 502 Bad Gateway; it does not fall back to a nearby city.

Country is the broadest and steadiest level, and city the narrowest:

• Country: the whole national pool, the most IPs to rotate through. Use it unless the content differs inside the country.
• Region: fewer IPs than the country; right for state-level prices, taxes and search results.
• City: a city holds far fewer IPs than its country. Use it for checks that need the local view (local search results, local ads, store availability), and keep volume work at the country level.

Location comes from IP geolocation databases, which are built from different sources and can disagree at city level: one service may place an IP in a neighboring town. Before a city-level job, send a few requests and check the location the target site itself shows (its store picker, currency or local results), not only an IP lookup. If a site sees a different location from the one you chose, message our 24/7 live chat with the IP and the time of the request; more causes are in the proxy setup guides.

In rotating mode, every request gets a new IP from the location in your username. A sticky session keeps the same IP instead, for 30 seconds to 36 hours (30 to 129,600 seconds, 20 minutes by default), with presets of 1, 5, 10 and 30 minutes and 1, 3 and 6 hours. Use sticky sessions for logins, carts and multi-step forms, where the site expects the same visitor from start to finish.

A sticky session adds -session-<id> and -ttl-<seconds> after the location: <login>-country-us-city-new_york-session-he9f2qga-ttl-600 asks for one New York IP for 600 seconds. The IP is held while its exit node is up; an IP that stays idle for 120 seconds is replaced by a new one, so a long job should send a request at least every 2 minutes. The IP is not guaranteed if the exit node drops: on a connection error the gateway retries once with a new session, so the IP may change, and a connection that breaks is not restored, so your client reconnects. When to pick which is covered in sticky vs rotating proxy sessions and on the rotating proxies page.

Need the same IP for longer than 36 hours? Dedicated ISP proxies and dedicated datacenter proxies are sold per IP for a 30-day term, renewed by you in the dashboard.

Targeting is by country, region (state) and city. The carrier is not a targeting option. On the mobile location pages, carrier names describe the networks the mobile IPs run on in that country. ASN and ZIP code targeting are not offered.

The parameters on this page apply to residential and mobile proxies. Rotating datacenter proxies cover the same countries as residential and target by country only, with -dc after the login: <login>-dc-country-us. Dedicated ISP and datacenter IPs come in the countries their order form lists, which follow stock, and take no targeting keys: you choose the country when you buy them. See the datacenter proxies and ISP proxies pages.

The same username works in any tool that accepts an HTTP or HTTPS proxy with a username and password. This Python script with Requests sends one request from the United States and one from Germany: the location change is only a username change.

from urllib.parse import quote
import requests

LOGIN, PASSWORD = "<login>", quote("<password>", safe="")   # URL-encode the password

for country in ["us", "de"]:
    proxy = f"http://{LOGIN}-country-{country}:{PASSWORD}@gate.proxyfield.io:7000"
    ip = requests.get("https://api.ipify.org",
                      proxies={"http": proxy, "https": proxy}, timeout=30).text
    print(country, ip)    # two different exit IPs, one per country

The password goes inside a URL here, so characters such as @, : or / in it must be URL-encoded; quote(..., safe="") does that. For a city, extend the same string: f"http://{LOGIN}-country-us-city-new_york:{PASSWORD}@gate.proxyfield.io:7000".

The same check in Node.js 18 or later with Axios and https-proxy-agent (save as geo.mjs, run node geo.mjs):

import axios from "axios";
import { HttpsProxyAgent } from "https-proxy-agent";

const LOGIN = "<login>", PASSWORD = encodeURIComponent("<password>");
for (const loc of ["country-us", "country-us-city-new_york", "country-de"]) {
  const agent = new HttpsProxyAgent(`http://${LOGIN}-${loc}:${PASSWORD}@gate.proxyfield.io:7000`);
  const { data } = await axios.get("https://ipinfo.io/json", { httpsAgent: agent, proxy: false, timeout: 30000 });
  console.log(loc, data.ip, data.city, data.country);   // one line per location
}

Step-by-step setup for other tools is in the integration guides for Python, cURL, Node.js, Playwright and Selenium.

New to ProxyField? Start with the quick start, from sign-up to your first request. Billing and account questions are answered in the help center.