Location targeting

The keys

Without -cc- the exit can be in any country. Region, city, ISP and carrier need a country key in the same login. Keys combine: region with city, city with ISP. Each extra key narrows the choice of exits.

LOGIN-cc-us-st-texas                       # anywhere in Texas
LOGIN-cc-us-st-texas-city-dallas           # Dallas, Texas
LOGIN-cc-us-city-dallas-isp-spectrum       # Dallas, on Spectrum
LOGIN-cc-de-city-berlin-sid-b1-ttl-30      # one Berlin IP for 30 minutes
LOGIN-cc-gb-car-three                      # mobile, on Three

The dashboard writes the keys in this order: country, region, city, ISP or carrier, then the session. The gateway accepts any order, but the keys themselves must be lowercase: -CC-us gets 407.

Writing the values

Values are the names from the dashboard's lists in lowercase, with everything except letters and digits removed:

The lists use English names, such as bavaria for Bayern. Pick values in the generator on the Residential or Mobile page, or fetch them with the locations API, which returns each name with the value the login takes.

When a value does not match

The gateway checks every value against the lists before it looks for an exit. A value it does not know gets 407 with an X-Reason header that names the key: unknown region, unknown city, unknown isp or unknown carrier. A region or city without a country gets region, city and isp need a country. The gateway never hands you an exit somewhere else in the country instead, so a typo shows up at once and not in your data.

Each of these 407s counts as a failed login. A job that sends a misspelt city from 50 threads soon reaches 30 failed logins a minute, and then every login from that address gets 429 until the minute is over. Gateway errors lists every answer.

A city that is in the list can still have no free exit at a given moment, especially a small one. The gateway then answers 502. Retry, or target the region instead.

How precise it is

In October 2026 we checked 40 residential sessions per level and placed each exit with ipinfo.io:

Most UK misses come from geolocation databases, which place many UK addresses in London. Every site uses its own database, and two databases can disagree about the same IP at city level. When the city matters, check the exit with the IP checker in the browser that uses the proxy, or a whole list with the proxy tester. The guide to checking a proxy IP goes further.

Targeting and sticky sessions

A sticky session belongs to the login, the key and the targeting together. Keep the targeting fixed for a profile or a task: when a session ends, the next IP then comes from the same place. Change the city and keep the key, and you start a new session with a new IP. Rotating vs sticky sessions has the details.