Operations

What is Geotargeting?

Geotargeting is choosing which country, region, city or carrier your proxy traffic exits from, so a site sees a visitor located where you want. You select it through parameters in the proxy username, a country-specific hostname, or a dedicated port, and the site reads that exit IP against whichever geolocation database it uses.

Selection happens at connection time. Gateway providers read a parameter out of the username, in forms like country-gb, city-manchester or an ASN identifier, while others publish one hostname or port per location, which is easier to wire into tools that will not accept a structured username. Granularity falls off below country level. Most pools honour a country request reliably and a large city approximately. Few can hold a postcode or a named carrier inside a named region. Ask what happens on a miss, since some gateways fall back to another country without saying so.

An IP address has no inherent location. What a site sees comes from a commercial database, MaxMind and IP2Location being the common ones, built on registry records and routing data. Vendors disagree about the same address, and their records lag reallocations. The location you were sold and the location your target reads can therefore differ, and the only test with any weight is checking against the geolocation service the target itself relies on.

Mobile carriers complicate this further. Traffic exits at a regional gateway, so a handset in one city often geolocates to another city or to the carrier's registered address entirely. That is normal consumer behaviour and rarely trips anything by itself. Mismatches inside your own stack cause more trouble. A German exit IP paired with an en-US browser locale, a New York timezone and a DNS resolver in Amsterdam is a pattern anti-fraud systems read quickly. Align the browser and the resolver with the exit.

Verify each country before you build on it. Request an exit, then check it against two independent geolocation lookups and against the target's own localisation, meaning the currency it quotes and the store it redirects you to. PROXIES.SX covers 100+ countries with per-country selection, and the location pages list what is available where. Coverage on paper is worth less than one clean test against the page you need to see.

Where you meet it

Geotargeting shows up as a dropdown in an ad verification tool and as a string in a scraper config. You need it when the page changes by location: local pricing, regional stock, a result set that differs between London and Manchester, an ad creative served in one market only. The decision it forces is granularity, whether country level is enough or whether the difference you are checking only appears at city level.

Browse locations

Common questions

How accurate is proxy geotargeting?

Country level is dependable across most providers. City level is approximate, because commercial geolocation databases disagree with each other and lag behind reallocations, and mobile traffic exits at regional gateways that can register a different city than the device sits in. Verify against the lookup your target site uses rather than the provider's own map.

Can I target a specific city or mobile carrier?

Some providers expose city and ASN parameters, which lets you request addresses belonging to a named carrier. Availability varies by country, and the pool shrinks fast as you narrow, so a city request in a small market may return very few distinct IPs or quietly fall back to the country. Confirm what a miss does first.

Why does the site still show the wrong country?

Usually something other than the exit IP is talking. A DNS resolver outside the tunnel, a browser timezone and locale from your own machine, a cookie holding a previous region choice, or a CDN serving a cached regional response. Clear site data, route DNS through the proxy, and match the browser locale to the exit country.

Related terms

Geo-Restriction
Geo-restriction is a service limiting access or content by the visitor's apparent location. The site maps the client IP to a country through a geolocation database, then blocks the request or quietly swaps in a regional catalogue with local pricing. Content licensing, sanctions rules, tax registration and commercial strategy are the usual reasons.
IP Rotation
IP rotation is the practice of changing the outbound address a client uses, on every request, on a timer, or on demand. It spreads traffic so no single address builds up enough volume to be rate limited or banned, and it is the defining behaviour of rotating and backconnect proxy services.
Session
In proxy usage, a session is a span of requests that all exit through the same IP address. It begins when you open a connection or claim a session identifier, and it ends when that identifier's timer expires or the network reassigns the address underneath you. Session control is what separates rotating traffic from a continuous identity.
Sticky Session
A sticky session is a proxy configuration that pins your traffic to one exit IP for a fixed window instead of rotating on every request. You request it through a session identifier in the username or through a dedicated port, and the gateway routes each matching request back to the same node until the timer runs out.
Proxy Pool
A proxy pool is the set of IP addresses a provider can route your traffic through. Its usefulness comes from composition as much as from size: how many distinct subnets and autonomous systems it spans, how many countries it reaches, how heavily each address is reused, and how clean those addresses look to the sites you target.
Concurrent Connections
Concurrent connections are the number of proxy connections open at the same moment, counted across your workers rather than over a period. It is a capacity limit, separate from requests per second and from bandwidth. Ten connections can carry thousands of requests an hour when each is short, or almost none when each holds a slow page open.
Backconnect Proxy
A backconnect proxy is a single hostname and port that fronts a pool of many IP addresses. The client keeps one connection string while the provider's gateway assigns a different exit IP per request, per session or on a timer. Rotation and pool health checks happen upstream, where the client cannot see them.

Real 4G/5G mobile and residential IPs

PROXIES.SX runs carrier IPs in 100+ countries with HTTP and SOCKS5 on every endpoint. $4/GB down to $2.40/GB at volume, free endpoints and rotation, and your GB never expire.

View pricing Browse the glossary