Proxy sellers love to offer targeting "down to a specific city" and even "down to the provider" — and charge a noticeable premium for it. But is this accuracy necessary for your task? We analyze when country-level proxies are sufficient and when city-level or ISP targeting is essential for a campaign to succeed.
Why proxy targeting affects results
Proxies are not just "IP from another country." Each IP carries metadata: country, region, city, provider (ASN), connection type (mobile operator, home internet, data center). Facebook Ads, TikTok Ads, Wildberries, and banking services analyze this metadata and compare it with account behavior. If you claim targeting in Moscow but the IP resolves as a data center in Germany — the system sees a discrepancy, increasing the risk of a ban or distorting the output.
The problem is that the level of geo detail varies for different tasks. An arbitrage specialist running ads across Russia does not care about the city. However, an SMM specialist managing a local business account in Krasnodar critically needs the IP to resolve specifically in that city — otherwise, Instagram may show content to the wrong audience, and the platform itself will notice the anomaly: the account "lives" in one city but accesses from another region.
Paying extra for accuracy makes sense only when the platform or task genuinely checks this level of detail. We will further analyze where verification exists and where it is merely a marketing overcharge.
Three levels of targeting: country, city, provider
All proxy targeting can be conditionally divided into three levels of detail, with each subsequent level being more precise but also more expensive.
Country-level. The most common and affordable option. Proxies are guaranteed to resolve in the required country according to geolocation databases (MaxMind, IP2Location, and similar), but the region within the country may "jump." For most tasks with broad geo, this is sufficient.
City-level. The proxy provider guarantees that the IP resolves specifically in the declared city — Moscow, Yekaterinburg, Almaty. This requires either a pool of IPs from that city or mobile proxies tied to base stations in the region. Accuracy here depends on the density of the pool: in large cities, the selection is vast; in smaller ones, there may be only a few IPs.
ISP/provider-level. The most expensive and narrow targeting — the IP is tied to a specific internet provider or mobile operator (MTS, Beeline, Rostelecom, etc.). This level is important where the service checks ASN (Autonomous System Number) and compares it with expected behavior — banks, streaming platforms, and some anti-fraud systems of marketplaces.
Comparison of targeting levels and when each is needed
Below is a summary table that helps quickly determine which level of targeting is needed for a specific task.
| Targeting Level | Accuracy | When it's sufficient | When it's insufficient |
|---|---|---|---|
| Country | Guaranteed country, region arbitrary | Advertising across the country, parsing general prices, access to geo-blocked content | Local business, regional promotions of marketplaces, hyper-local SMM |
| City | Guaranteed specific locality | Monitoring prices on Wildberries/Ozon by regions, Avito ads "from the city," local Facebook Ads campaigns | Services that check ASN and provider type directly |
| Provider (ISP/ASN) | Guaranteed specific telecom operator | Banking services, streaming with anti-fraud, accounts tied to a mobile number and operator | Usually excessive for advertising and SMM tasks |
When country targeting is sufficient
If you are running Facebook Ads or TikTok Ads to a broad audience — for example, "all of Russia" or "the USA" — the platforms do not check the city at the IP level as strictly as the country. The algorithm primarily looks at the billing country of the card, the interface language, geolocation by IP at the country level, and the behavioral patterns of the account. City accuracy is redundant here.
The same applies to parsing general data — for example, collecting prices on AliExpress or monitoring foreign marketplaces without a regional price grid. Here, it is important to just get into the right country to see the localized version of the site and currency. In such cases, data center proxies with country-level targeting solve the task quickly and without overpaying for detail that is not used.
Country-level targeting is also suitable for testing geo-specific advertising at the exploratory stage: if you want to see what competitive advertising looks like in different countries, city accuracy is not needed at all — only the change of country matters.
When city targeting is critical
City accuracy becomes mandatory where the platform itself changes content or logic based on the region. A classic example is Wildberries and Ozon: prices, product availability, and delivery times vary by warehouse region and buyer's city. If you monitor competitor prices for one region while the proxy resolves in another, you will receive distorted data and make decisions based on incorrect prices.
Avito is another scenario where city targeting is critical. An ad posted "from Moscow" but with an IP from another region looks suspicious to the platform's anti-fraud system and may be hidden from local listings or outright rejected. Sellers who post ads in multiple cities simultaneously need a pool of IPs with real city ties — here, residential proxies work well as they belong to real home connections in specific localities.
For SMM agencies managing accounts of local businesses (cafes, salons, stores in a specific city), city accuracy affects who Instagram and TikTok show content to in the "recommendations" and "interesting" sections. If the account "sits" in another city, the algorithm may decide that the audience is irrelevant and reduce organic reach.
When the provider (ASN) matters
Provider-level targeting is the narrowest and most expensive, and it is not always necessary. The main scenario is services with strict anti-fraud measures that check ASN and connection type: banking applications, streaming platforms with regional licenses, and some verification systems of marketplaces during seller registration.
A separate case is accounts tied to a mobile number of a specific operator. If registration in Instagram or TikTok occurs with an MTS number while the IP resolves as wired internet from another provider, it creates a slight but noticeable discrepancy in the device's digital fingerprint. For such scenarios, mobile proxies are suitable — they not only guarantee the city but are also tied to a real mobile operator, which covers the provider-level check.
It is important to understand: paying extra for ISP targeting is justified only if the specific platform genuinely checks ASN. For most advertising accounts and SMM tasks, this level of detail is not used by algorithms, and overpaying for it does not yield measurable results.
How to check actual geo accuracy before purchase
A proxy seller may claim "city targeting," but in reality, they may be selling country-level IPs with approximate regional accuracy. You can check this in a few minutes:
- Connect a test proxy and open an IP checking service (ipinfo.io, whoer.net, or similar) — compare the declared city with the actual geolocation result.
- Check the ASN and provider name in the output — if city-level or ISP-level targeting is claimed, a specific operator should be displayed, not a general data center.
- Open a local service that knows your region accurately (for example, a local weather or delivery site) and check if it correctly identifies the city through the proxy.
- Request demo access or a trial period from the proxy provider for a small pool of IPs before purchasing a large volume — this is standard practice for B2B proxies.
If after checking the city or provider does not match the claims — this is a reason to reconsider the choice of provider, rather than overpaying for detail that does not actually exist.
Setting up geo in anti-detect browsers
After selecting a proxy with the desired level of targeting, it is important to correctly link it with the profile in the anti-detect browser so that the geo parameters match at all levels — from IP to time zone and system language.
In Dolphin Anty, when creating a profile in the "Proxy" section, the IP, port, username, and password are specified, and below is the "Timezone" and "Geolocation" block, which is recommended to be synchronized automatically with the proxy IP to avoid desynchronization between the IP city and the profile system's time zone.
In AdsPower, a similar logic applies: when adding a proxy in the profile settings, there is a geo check button ("Check") that will show the country, region, and provider based on the IP data — this is convenient to immediately see if the actual targeting matches what the proxy provider promised.
In Multilogin and GoLogin, the process is similar: the geo and time zone of the profile are tied to the proxy IP, and it is recommended to avoid manually setting a time zone different from what is determined by the IP — this is one of the typical reasons why an account with a "correct" proxy still comes under suspicion.
Common mistakes when choosing targeting
The first mistake is purchasing provider-level targeting "just in case" when the task does not require such precision. This increases costs without improving results because the platform simply does not check ASN.
The second mistake is the opposite: saving on city-level where regional accuracy is critical, for example, when monitoring marketplace prices or placing local ads on Avito. In this case, the data is distorted, and decisions are made based on incorrect information.
The third mistake is trusting the declared targeting without verification. Many providers sell IPs with approximate geolocation, passing it off as accurate city-level. Without independent verification through geolocation services, it is easy to overpay for something that does not actually exist.
The fourth mistake is desynchronization between the proxy geo and other profile parameters: browser language, time zone, regional system settings. Even an ideal city-level proxy will not help if the other profile parameters indicate a different region.
Checklist: what to pay for and what is unnecessary
- Advertising across the country, general parsing, access to geo-content — country-level is sufficient, no need to pay extra for city targeting.
- Monitoring prices on Wildberries/Ozon by regions, Avito ads from a specific city, local SMM — city-level is needed.
- Banking services, streaming with anti-fraud, accounts tied to a mobile operator — ISP/provider-level targeting is justified.
- Before purchasing any level of targeting — check actual geo through services like ipinfo.io, rather than relying solely on the tariff description.
- Synchronize proxy geo with time zone and profile language in the anti-detect browser — otherwise, precise targeting will not yield results.
Conclusion
The accuracy of proxy targeting is worth the money only to the extent that it is verified by the specific platform. For broad advertising campaigns and general parsing, country-level is sufficient. For regional tasks — monitoring marketplaces, local ads, hyper-local SMM — city targeting is needed. And paying extra for the provider is justified only where the service genuinely checks ASN, such as in banking and streaming anti-fraud systems.
Before purchasing a large pool of IPs, always check the declared targeting in practice, rather than relying on the tariff description. If the task requires flexibility between broad and precise geo, consider residential proxies — they cover both country-level and city-level scenarios with real IPs from home users, reducing the risk of blocks regardless of the chosen level of detail.