PhantomFundamentals
Rotating vs. Sticky Proxies
Rotating proxies request a different route frequently, often on every request. Sticky proxies ask the gateway to reuse one route for a session identifier and a limited lifetime. The right choice depends on whether your task values diversity or continuity.
The practical difference
Rotation is a routing instruction, not a promise that every request receives an IP never seen before. Sticky lifetime is also a requested maximum: a residential device can disconnect before that time.
| Behavior | Rotating | Sticky |
|---|---|---|
| Route reuse | Usually changes per request | Reuses a session when available |
| Best fit | Independent fetches and coverage checks | Multi-step flows and consistent browsing |
| Configuration | No session tag | Session ID plus lifetime |
| Main tradeoff | Less continuity | Smaller eligible pool over time |
How sticky session IDs work
The proxy password carries an eight-character alphanumeric session ID and a lifetime. Reusing the same complete credentials asks the gateway to resolve the same session. Creating a new ID creates a separate session.
PhantomProxies can generate independent session IDs in bulk. Available lifetimes run from one minute through seven days, but continuity still depends on the selected residential route remaining online.
password_country-us_session-a1B2c3D4_lifetime-30mWhen to use each mode
Use rotation for separate public-page checks, broad sampling, and tasks where one response does not depend on the last. Use sticky mode when a permitted workflow has cookies, a cart, or several navigation steps that expect a consistent network identity.
Do not use rapid rotation to evade access controls or overwhelm a destination. Concurrency should reflect the target's rules and capacity, even when a proxy network does not impose a session limit.
A simple selection rule
If losing continuity would invalidate the next request, start sticky. If each request is independent and coverage matters more than continuity, start rotating. Test with a small sample before scaling either configuration.