LogoLogo
Nimble HomeLoginCreate an Account
  • Home
  • Quick Start Tutorials
    • Tutorial Library
      • Track SEO and SEM Ranking
      • Reddit as a Guerilla Marketing Strategy
  • Nimble Platform
    • Nimble Platform Overview
    • Online Pipelines
      • Supermarkets
        • ASDA
        • Tesco Groceries
        • Sainsbury’s
        • Morrisons
      • eCommerce
      • Restaurants
        • Yelp
        • Tabelog
        • Uber Eats Japan
        • Demaecan
        • Uber Eats US
      • Real Estate
        • Zillow
  • Nimble SDK
    • SDK Overview
    • Web API
      • Web API Overview
      • API Product Specs
      • Nimble Web API Quick Start Guide
        • Introduction
        • Nimble APIs Authentication
        • Real-time URL request
        • Delivery methods
        • Batch processing
        • Response codes
        • FAQs
      • Nimble Web API Functions
        • Realtime, Async & Batch Request
        • Geo Location Targeting
        • Javascript Rendering
        • Page Interaction
          • Wait (delay)
          • Wait for Selector
          • Wait and Click
          • Wait and Type
          • Scroll
          • Scroll to
          • Infinite Scrolling
          • Capturing Screenshots
          • Collecting Cookies
          • Executing HTTP Requests
          • Operation Reference
        • Network Capture
          • Filter by URL Matching
          • Filter By Resource Type
            • Real World Demo: Capturing Ajax Requests
          • Wait for Requests
          • Capturing XHR without Rendering
          • Operation Reference
        • Data Parsing
          • Parsing Templates
          • Merge Dynamic Parser
        • Custom Headers & Cookies
        • General Params
      • Vertical Endpoints
        • SERP API
          • Real-time search request
          • Getting local data
          • Browsing SERP pagination
          • Delivery methods
          • Batch Processing
          • Endpoints and Response Codes
        • Maps API
          • Searching for places
          • Getting information about a place
          • Collecting reviews
          • Delivery methods
          • Batch processing
          • Endpoints and Response Codes
    • Web Retrieval API
      • Web Retrieval API Overview
    • Proxy API
      • Nimble IP Overview
      • Nimble IP Quick Start Guide
        • Send a request
        • Nimble IP Autentication
        • Geotargeting and session control
        • Response codes
        • FAQs
      • Nimble IP Functions
        • Country/state/city geotargeting
        • Controlling IP rotation
        • Geo-sessions: longer, stickier, more accurate sessions
        • Using IPv6 Proxies
        • Response Codes
      • Integration Guides
        • Incogniton
        • Kameleo
        • VMLogin
        • AdsPower
        • FoxyProxy
        • Android
        • Multilogin
        • iOS
        • SwitchyOmega
        • Windows
        • macOS
        • Proxifier
        • MuLogin
        • Puppeteer
        • Selenium
        • Scrapy
    • Client Libraries
      • Installation
      • Quick Start
    • LangChain Integration
  • Technologies
    • Browserless Drivers
      • API Driver-Based Pricing
    • IP Optimization Models
    • AI Parsing Skills
  • Management Tools
    • Nimble Dashboard
      • Exploring the User Dashboard
      • Managing Pipelines
      • Reporting and Analytics
      • Account Settings
      • Experimenting with the Playground
      • Billing and history
    • Nimble Admin API
      • Admin API basics
      • Admin API reference
  • General
    • Onboarding Guide
      • Getting started with Nimble's User Dashboard
      • Nimble IP Basics
      • Nimble API Basics
      • Helpful Resources
    • FAQs
      • Account Settings and Security
      • Billing and Pricing
      • Tools and Integrations
      • Nimble API
      • Nimble IP
    • Deprecated APIs
      • E-commerce API
        • E-commerce API Authentication
        • Real-time product request
        • Real-time product search request
        • Delivery methods
        • Batch Processing
        • Endpoints and Response Codes
      • Unlocker Proxy Overview
        • Unlocker Proxy Quick Start Guide
          • Real-time request
          • FAQs
        • Unlocker Proxy FAQ
Powered by GitBook
On this page
  • How Geo-sessions work
  • Why use Geo-sessions
  • Geo-sessions vs. sticky sessions
  • Creating a new Geo-session
  • Geo-session IDs are Global
  1. Nimble SDK
  2. Proxy API
  3. Nimble IP Functions

Geo-sessions: longer, stickier, more accurate sessions

In the past, businesses used sticky sessions to run multi-step procedures or mimic user behavior. At Nimble, we saw significant room to improve session quality, longevity, and accuracy.

Geo-sessions are our end-to-end upgrade to traditional sticky sessions that provide substantial upgrades across the board. Instead of minutes or hours, Geo-sessions can be maintained for days or even weeks at a time, and provide substantially improved session quality and geotargeting accuracy.

How Geo-sessions work

Geo-sessions improve session stability, longevity, and quality by an order of magnitude. This is achieved through several pioneering methodologies:

These parameters work together to create highly consistent sessions. Even when IP rotation inevitably occurs, the new IP is highly-likely to replace the previous IP so well that it resembles normal ISP IP reassignment, and the session continues normally.

Geo-session peers are selected from within a 175 kilometer radius of the current peer.

Why use Geo-sessions

Geo-sessions provide a reliable and effective solution to several key needs:

Geo-sessions vs. sticky sessions

Both Geo-sessions and sticky sessions have their unique advantages. Geo-sessions offer substantially longer duration, highly-precise and consistent geotargeting, and minimum rotation. On the other hand, sticky sessions rotate unresponsive IPs faster, and may provide faster download speeds due to using a wider range of proxies.

Sticky Session
Geo-session

Session duration

minutes or hours

days or weeks

Rotation sensitivity

Medium: unresponsive IPs are quickly replaced

Low: unresponsive IPs are given time to return

Geotargeting during IP Rotation

Medium: City targeting is the highest precision.

High: maintains precise, tight geographic zone.

Performance

high: uses many IPs and rotates unresponsive IPs.

Medium: algorithmically selects most stable IPs.

Geo-sessions are currently only supported within the US. Support for additional countries is coming soon.

Creating a new Geo-session

To create a new Geo-session, simply use the geosession flag with a random string that will serve as the new Geo-session ID:

Geosession IDs are limited to between 16 to 32 alphanumeric characters (16 characters minimum).

curl -x http://account-accountName-pipeline-pipelineName-geosession-randomGeoSessionString:[email protected]:7000 https://ipinfo.io

For Geo-sessions to work properly, please extend your request timeout to at least 40 seconds on your http client (e.g Chrome/Puppeteer/Selenium/Curl/http code library, etc.).

Geo-sessions can persist for up to 10 days of inactivity before being ended.

Geo-session IDs are Global

Traditional sticky session IDs are limited to your account, meaning:

However, Geo-sessions are global across Nimble's platform. This means:

To help ensure your custom Geo-session ID is unique, Nimble considers additional parameters when identifying a Geo-session. For example, the following request initiates a Geo-session in London, England:

curl -x http://account-accountName-pipeline-pipelineName-country-GB-city-london-geosession-randomGeoSessionString:[email protected]:7000 https://ipinfo.io

If another Geo-session with the same ID is started that targets a different location, this will be considered a separate session, and will receive a different proxy.

Be sure to use the same parameters across requests that share the same Geo-session. If the location targeting is changed, but the Geo-session ID remains the same, a new session will still be initiated.

PreviousControlling IP rotationNextUsing IPv6 Proxies

Last updated 1 month ago