Geo-targeting is how you choose where your proxy traffic appears to come from — a country, a city, even a specific network. You set it with parameters in the proxy username, and getting it right is what makes localized data (search results, prices, ads) actually reflect the place you care about.
Levels of targeting
Country targeting is the baseline and is included on every pool: add a country code and every exit IP resolves inside it. City, state, ZIP and ASN targeting narrow it further — useful when results vary by metro or you need a specific carrier or ISP.
Every pool resolves country, state, city, ZIP and ASN. Country traffic always bills 1:1; below-country traffic bills 2:1 on datacenter, residential and mobile, and 1:1 on premium residential. Choose the pool by the IPs you need and by how much of your traffic is finely targeted — not by whether fine geo is available, because it always is.
How it rides in the username
Targeting parameters attach to your login. A country looks like cr.us; a city like city.newyork; you can combine them, and add a sticky session so a targeted IP holds for a few minutes. One credential, many geographies — just change the string.
Because the geography is per request, you can fan a single job out across dozens of locations without managing separate proxy lists. The gateway resolves an exit that matches each request's parameters.