Sticky-or-rotate controls: hold one IP or rotate per request
One gateway, two behaviours. Some jobs need the same IP held steady through a multi-step flow; others need a fresh IP on every request. The sticky-or-rotate switch gives you both on one gateway, and which one you get comes down to how you frame the credential — no separate accounts, no second endpoint.
Two behaviours, decided in the request
Whether you hold one IP or draw a fresh one comes down to how you frame the credential — no separate accounts, no second endpoint.
Sticky sessions: hold one IP
Add a session token and the gateway pins a single mobile IP to it for the TTL you set — anything from seconds to days. Every request carrying that token leaves through the same address. This is where logins, cart and checkout flows, account QA runs, and anything that has to read as one continuous user belong. The IP holds until the TTL lapses or you retire the session.
Per-request: fresh every call
Drop the session token, or set rotate-per-request, and each call draws a new exit from the live mobile pool. This is the mode for crawlers, bulk data pulls, and ad-verification fan-out — anywhere spreading traffic across many IPs is what beats per-IP rate limits. A request won't reuse the previous IP unless the pool happens to hand it back.
Switch modes without re-architecting
Both modes share the same gateway, credentials, and code path. You decide sticky or rotate per request, so a single worker can hold a session to log in and then fan out per-request for the crawl that follows. No second integration, no separate proxy product, no credential juggling — the switch lives in the request.
Rotate on command, too
There is a middle setting too: hold a sticky IP, then force a rotation the moment your code calls for it — after a 429, after a checkout, on whatever schedule you keep. Sticky for stability, per-request for spread, on-command for the precise moments. One gateway handles all three.
One gateway, three control modes
Sticky by token
Attach a session token and pin one mobile IP for a TTL from seconds to days — logins, carts, QA runs.
Per-request rotation
Drop the token and each call draws a fresh exit — crawlers, bulk pulls, ad-verification fan-out.
On-command rotate
Hold a sticky IP and force a swap exactly when your code says — after a 429, a checkout, or on schedule.
One integration
Both modes share the same gateway, credentials and code path; the switch lives in the request, not the account.
Sticky-or-rotate at a glance
Sticky-or-rotate questions
What does sticky-or-rotate mean?+
How long can a sticky session hold one IP?+
Do I need separate accounts for each mode?+
Can I force a rotation on a sticky IP?+
Wire up your first switch
Sizing the pool
Mixing steady sessions with high fan-out? Check the pricing for per-IP rates, then create an account and flip between sticky and rotate in under 90 seconds.
Test the rotation before you pay
Take the pool for an hour, free — no card. Watch IPs rotate on your schedule and hold sticky sessions where you need them, then pick a plan.