Sticky session proxies
One address held across a sequence of requests, so a multi-step flow does not change identity halfway through.
Pick this when
A sequence of requests has to look like one visitor.
- Set with
- Rotation 0, alongside a session identifier
- Identifier
- A string you choose — letters, numbers and underscores, up to 64 characters
- In parallel
- Several named sessions on one credential pair; two names can share an address
- Bounded alternative
- A 5 to 60 minute window, whose end you set rather than discover
How it works
You pass a session identifier when building the connection, and requests carrying that identifier keep the same outbound address.
This is what a login, a cart or a checkout needs. Rotating mid-flow generally invalidates the state the site is holding for you.
Sessions are named, so several run in parallel under the same credentials without interfering with one another. What we have not measured is whether two names land on two different addresses — so treat them as lines kept apart, not a promise of one address each.
How it differs
Against its nearest neighbours, by name. If one of these describes your situation better, the row is a link.
Where it fits
Use it for
- Authenticated sessions that must persist across requests
- Multi-step flows — search, then filter, then paginate
- Any workflow where a mid-sequence IP change would drop server-side state
Do not use it for
- High-volume stateless collection, where holding one address concentrates traffic on it
- Work that benefits from spreading requests widely — use per-request rotation instead
- Jobs that open a session per item and never close one, on the assumption that nothing is counting
Sticky sessions concentrate your traffic on fewer addresses. Use them for the part of the job that needs continuity, and rotate for the part that does not.
A real connection
One credential pair covers everything. Type, country, rotation and session all travel inside the username, so you never provision a second proxy user to change one of them.
http://user-Ex4mpleUser12345-type-residential-session-cart_7f2-country-IT-rotation-0:YOUR-SECRET@geo.g-w.info:10080Requests carrying the same session value keep the same address. Several names run in parallel on one credential pair, each keeping its own flow intact — but we have not measured that two names land on two addresses, so plan for them sharing one.
Questions
- How long does a sticky session last?
- Longer than one request, and that is the limit of what we can honestly tell you. Rotation 0 asks for the address to be held against that session name; no documentation from the network puts a duration on it, names what ends it, or promises it survives a pause, and we have not timed one. If you need a bound you can plan against, use timed rotation instead — a 5 to 60 minute window ends when you said it would.
- How many sessions can I run at once?
- Several, distinguished by the identifier you choose. The network documents no limit and we have not measured one, so there is no number we can honestly quote — and that silence is not a guarantee no ceiling exists. Treat a session as something you open and release rather than an unbounded pool: one session per concurrent worker scales, one per item does not.
- What if the address goes offline mid-session?
- On residential and mobile this can happen — the underlying connection is not yours. Write the workflow so a step can be retried, rather than assuming an address will survive an arbitrarily long job.
- Should I use sticky for everything?
- No. Sticky concentrates your volume on fewer addresses, which is the opposite of what stateless collection wants. Use it for the part of the job that needs continuity.
The same on every type
These four do not vary by proxy type, so they are worth stating once rather than six times. One balance covers all of it.
- Protocols
- HTTP and SOCKS5, one port each. Destinations on 80, 443 and 8080
- Targeting
- Country always; then a state or a city, in unaccented letters, digits and underscores; ASN by number
- Rotation
- Per request (-1), sticky (0), or 5 / 10 / 15 / 20 / 60 minutes
- Rate
- $3/GB, sent plus received
Where this comes up
- A price is only meaningful alongside where it was observed. Get the location wrong and you are monitoring a number nobody is actually offered.
Price monitoring
- Infringing listings are frequently hidden from the market where the brand’s legal team is sitting, and shown only where they are being sold.
Brand protection
Where the address comes from
Pick exactly one.
- IP classThe target rejects hosting ranges but does not need a carrier address.
Residential proxies
- IP classNothing is blocking you yet, or a predictable round trip matters more than provenance.
Datacenter proxies
- IP classResidential was rejected too, or the platform expects a carrier address.
Mobile proxies