A sticky session tells the proxy gateway to keep giving you the same exit IP for a fixed window (minutes to hours) instead of a new IP on every request. On a mobile network the exit IP belongs to a real phone behind carrier NAT, so a sticky session means "stay on this phone" until the window ends or you release it.
Sticky session vs rotation
- Rotating: every request (or every N seconds) exits from a different device. Good for scraping public pages where each request is independent.
- Sticky: one device for the whole window. Required for anything with a login, a cart, or a multi-step flow, because platforms compare the IP across the session and treat a mid-session change as a hijack.
If your workload sits on the rotating side, USA rotating proxies covers that half in detail: rotation intervals per workload, session parameters, and verifying the exit before you run volume.
How long should a sticky session be?
Match it to the task, not to the maximum the provider allows:
- Login and post on a social account: the length of the session, then release.
- Checkout on a marketplace: until the order confirmation.
- Long automation runs: 30 to 120 minutes, which is how a phone naturally moves between towers, then rotate.
Holding one IP for days does not make it "cleaner"; a real phone changes IP when it moves. Rotating every few seconds during a login is what gets flagged.
Sticky sessions on dedicated vs shared mobile proxies
On a dedicated device you control rotation directly, so every session is effectively sticky until you rotate. On a shared pay-per-GB pool you request stickiness in the connection string (a session ID) and the gateway pins you to a device for the configured window.
In practice the session ID rides in the proxy username. On VoidMob's pool gateway you chain underscore parameters onto your username: <username>_c_US_s_run1_ttl_30m pins every request carrying session ID run1 to the same US device for a 30-minute window. Swap run1 for any new string and the gateway assigns a new device; leave the _s_ parameter off entirely and you get per-request rotation. If you prefer configuration over per-request control, a named proxy list can be set to sticky once and every credential in it behaves that way.
Either way, verify the pin is actually holding: check your exit IP at the start of the flow, then again mid-run. The same address means the session is holding; a new address means the device dropped and the gateway re-pinned you.
Is your session holding? Check your exit IP
1Does a sticky session guarantee the same IP?
For the configured window, yes, unless the device drops off the network. Then the gateway assigns a new device and the IP changes; check the response headers or your IP checker at the start of critical flows.
2Can I hold a sticky session across two accounts?
You can, but you should not: two logins from one IP inside one window look like one operator running two accounts. Use one session per account.
3Is a sticky session the same as a static proxy?
No. Static means one fixed IP for the life of the plan (usually datacenter or ISP). Sticky is a temporary pin on a rotating pool; when the window ends you get a new IP.
Run sticky sessions on real 4G/5G devices
Dedicated devices you rotate on demand, or pay-per-GB pools with configurable session length.