# City targeting

City targeting restricts the exit IP to addresses that geolocation databases place in a given city. It is used for local search results, delivery pricing, real-estate listings, ad verification and anything else served by metro area. Its limits are the pool size in that city, the precision of geolocation for smaller places, and the fact that a household's "city" is whatever the database says, not a GPS position.


## Syntax and naming

City names are written as lowercase ASCII with spaces and punctuation removed: `newyork`, `saopaulo`, `frankfurt`. Diacritics are dropped (`zurich`, `malaga`). The country parameter is required alongside the city.

```text
http://USER-cc-de-city-berlin-sid-7f3a9-ttl-10m:PASS@res.proxshift.com:9000
```


## What to expect

- Capitals and large cities: deep pools, immediate answers.
- Mid-sized cities: fine for sticky sessions, thinner for high concurrency.
- Small towns: may resolve to the nearest larger city in the database; verify with an echo service.


## How it works at ProxShift

ProxShift lists the largest cities for 60 countries on their location pages; any city with active households can be targeted the same way. ISP and datacenter addresses offer city choice at the order where the pool allows.

## Questions

**Why does a city exit sometimes geolocate elsewhere?**

Because databases disagree. The gateway places exits with one database; the target may use another that maps the same address to a neighbouring town. Country-level agreement is near-perfect; city-level agreement is high in metros and lower elsewhere.

Source: https://proxshift.com/glossary/city-targeting