Country-based targeting is enough for most work. But scenarios such as local search results, regional pricing and city-based ad verification require a finer breakdown: targeting at the city and sometimes ISP level.
In this article we cover how targeting works, its accuracy limits and how to verify the results.
Targeting Breakdowns
The narrower the breakdown, the smaller the pool, and both accuracy and speed drop. Unless you genuinely need it, staying one level up is more efficient.
How Does the Provider Know the City?
The provider matches every IP in its pool against a geolocation database. These databases are compiled from ISP records, routing information and user feedback. The problem is this: the target site uses its own database as well and the two do not always agree.
Whatever the target site thinks is what counts. That is why you should measure targeting accuracy against the real target, not against your provider's dashboard.
100% accuracy in city-based targeting is not realistic. With a good provider, high accuracy in large cities and noticeable drift in small ones is normal. On critical work, always verify the result on the target itself.
Sending the Targeting Parameter
Parameter names and separators vary by provider. Turkish characters and spaces in city names are not supported by most systems — write the ASCII equivalent.
Scenarios Where City Targeting Is Genuinely Needed
Local search results
Search engines return a completely different result set for “near me” queries depending on location. Local SEO tracking is meaningless without a city breakdown. SEO proxy scenarios, this is the most frequent need.
Regional price and stock
Marketplaces and retailers show different stock, different delivery times and sometimes different prices depending on the city. Price comparison work, this is critical.
Ad verification
To check that campaigns appear in the right city with the right creative. Ad verification page has the details.
Localization testing
Verifying how your own product looks in different regions; currency, language and delivery options.
How Is Accuracy Measured?
The right way to measure whether city targeting works is to look at the target's own output — not at the provider's report.
To see your exit location quickly you can use the My IP Address page; but always run the real test on the target site itself.
The Pool Depth Problem
The narrower the city, the fewer nodes are online there. If a small city has only a few nodes:
- You get the same IPs again and again; rotation loses its meaning.
- You hit rate limits sooner.
- When nodes go offline, requests fall back to the country level or fail.
- Latency may increase; because the pool is thin, the load is not distributed.
Pool depth changes throughout the day. In small cities the pool can drop to a critical level during the night; scheduling your jobs for peak hours improves the hit rate.
When Is ISP Targeting Necessary?
ISP-based targeting is a rare requirement, but it is decisive in some scenarios: viewing operator-specific campaign pages, verifying ISP-based content differences, or testing access from a particular network. Because the pool narrows sharply, its cost and latency are high.
If you need a static and predictable ISP identity, then instead of rotating residential, ISP proxy is a much better fit: the IP is static and the operator registration is clear.
Alternative: Country Level + Verification
If city targeting is costly and volatile, a practical approach is this: work at country level, read the city of the IP you are given, and if it is not the city you want, skip the request and take a new IP. This is a “select and verify” strategy rather than a “filter” one.
Instead of waiting on a narrow city pool, this method samples quickly from a large pool. The cost of the check request is low and it is more efficient overall.
Summary
City and ISP targeting deliver real value in scenarios such as local search, regional pricing and ad verification; but the narrower the breakdown, the smaller the pool, the more accuracy fluctuates and the higher the cost. Always measure accuracy against the target's own output, take intraday pool depth into account, and consider the “select and verify” strategy on narrow pools. For location options see proxy locations page.