A rotating pool gives you a new address on each request, which breaks anything that needs continuity, such as a login followed by a few page views. A sticky session is the middle ground: you ask the pool to hold one exit, and requests that carry the same session identifier keep leaving from the same address.
How providers implement it
Most vendors put the session identifier in the proxy credentials, usually as an extra segment in the username or password. Change the identifier and you get a new exit; drop it and you are back to rotating on every request. The exact syntax differs by vendor, so copy it from your provider's dashboard or documentation rather than from another vendor's example.
What sticky is not
- It is not static. On a residential network the exit is someone's device. If it goes offline, the session ends early and you get a new address mid-flow.
- It has a lifetime. Providers cap how long they hold a sticky exit, usually minutes to hours, not the weeks or months of a static IP.
- It cannot be allowlisted. Nobody can add a sticky residential exit to a firewall, because it will not be yours tomorrow.
Test it yourself
Send a handful of requests with the same session and check that the exit holds, then wait and check again to see how long it lasts. Log the exit IP on every request in production so you can see when a session broke.
On ProxyHive
ISP and datacenter IPs are static, so they need no session: the address holds for the term you pick. For residential session control, see the options on your order in the dashboard at https://app.proxyhive.io. Rotating vs static proxies covers when sticky is enough and when you need a static address.