Geo Location Targeting
Last updated
Last updated
Geo-targeting is the ability to route requests through proxies located in specific geographical locations. This capability is particularly valuable for data collection that varies based on the user's geographic location, which can be crucial for businesses that require localized content or need to adhere to regional regulations and settings at scale.
Geo-targeting is an actual feature of Nimble IP, but it is exposed via Nimble API
Built on top Nimble IP our premium Residential Proxy product offering, with high reputation, fast performance, and high availability worldwide to ensure requests always get through and are never rate limited. Nimble's Proxy help users with:
Geo-Restrictions: Some businesses only operate in certain countries, or may localize information by the user's locale. Nimble AI Browser again uses residential proxies to empower users to send requests for anywhere in the world - ensuring access and localized data accuracy.
SEO and Market Research: Companies can see how their or competitors’ websites appear in different regions, which is crucial for strategies involving search engine optimization (SEO) and localized marketing analysis.
Unlocking: Helps in mimicking the behavior of local users, reducing the likelihood of being blocked by the target websites which might have anti-scraping measures in place.
Supported by real-time, asynchronous, and batch requests.
url
Required (In case of Web API Endpoint)
URL | The page or resource to be fetched. Note: when using a URL with a query string, encode the URL and place it at the end of the query string - Web API endpoint.
country
Optional (default = all)
String | Country used to access the target URL, use ISO Alpha-2 Country Codes i.e. US, DE, GB
state
Optional (default = null)
String | State used to access the target URL, use ISO Alpha-2 Country Codes i.e. NY, AZ, CA
city
Optional (default = null)
String | City used to access the target URL, use ISO Alpha-2 Country Codes i.e. brooklyn, paris, london
locale
Optional (default = en-US)
String | LCID standard locale used for the URL request. Alternatively, user can use auto for automatic locale based on geo-location.
A simple real-time request with state targeting and locale set to EN, meaning the request will be routed from New York State and the LCID standard will be set to English (which is the default value).
Targeting a state is only available when the country parameter is set to US.
Supported endpoints: , , and .
Not supported endpoints: .
You can retrieve a comprehensive list of supported countries, states, and cities by using the of the Admin API.
See the full list of
