Sticky Session

A sticky session pins your requests to one exit IP for a defined time or task, rather than rotating the address on every request. It is the opposite of a rotating pool. Stickiness matters whenever a site ties state to your IP — logging in, filling a multi-step form, holding a shopping cart — because a mid-flow IP change can look like account theft and break the session. It is closely related to session persistence, though persistence is the broader idea of maintaining continuity across a series of requests.

Selecting an exit does not automatically rotate every request. Configure your client for the issued endpoints, preserve stateful sessions and respect applicable limits. s4m has selectable public exit configurations. Use the endpoint or profile issued for the protocol and location selected in your account. A dedicated IP is exclusive during its assignment under the service terms. Prior history, assignment duration, availability and supported bindings still matter. Related topics: scraping, rate limits, datacenter proxies, dedicated IP.

To pin a task to one address, either request a sticky session from a rotating provider or use an inherently stable exit such as an s4m dedicated IP, which never changes because it is yours. Combine the stable IP with consistent cookie handling so both the network and application layers signal one visitor — that pairing is the essence of session persistence. Reserve rotation for stateless, high-volume scraping, where spreading requests across IPs beats staying on one.