Decide which actions belong to one session before choosing a rotation mode.
Check which steps need to stay together
A public-page check can be independent: its result does not depend on what happened on the previous page. A signed-in workflow may be different, with several steps sharing account and session context.
Write down the start and end of the task. If an IP change between those steps would disrupt the task, test whether the connection keeps the same exit throughout.
A sticky session is not a permanent IP
Sticky mode requests the same exit for a period. How long it lasts depends on the supported duration, resource availability and any interruptions. Confirm the selected product’s conditions before relying on a particular session length.
A monthly payment period describes billing. Check separately how long the exit stays assigned and whether any connection details can change when you renew.
Test the behaviour your workflow needs
- Check the exit inside the actual browser or script.
- Run a short version of the intended sequence and check again.
- Record errors separately from changes in the observed IP.
- Recheck after changing settings or replacing a resource.
Match IP rotation to the task
Changing exits can fit independent research batches. If you need a defined set of connections, check how long the product retains them and which session conditions apply.
Rotation does not guarantee access to a target website, and keeping an exit does not guarantee account acceptance. Review the returned content as well as connectivity.