Choose the session model that matches the task.

Before you start

• A list of workflows using or planning to use a proxy
• The persistence and location needs of each workflow
• Access to the AliasMode proxy configuration for testing

Step-by-step

1. 1

   Identify workflows that need a stable identity

   A static proxy keeps the same exit IP until the provider or operator changes it. It fits recurring profile work where the team wants a simple, documented account-to-IP map.

2. 2

   Identify workflows that tolerate a session window

   A rotating network can hold one exit for a provider-defined session window. This can support shorter persistent tasks when the session duration and replacement behavior are clear.

3. 3

   Identify workflows that need fresh exits

   A new exit on each request fits some research or collection jobs. It is a weaker match for a browser profile that must return to one account context over time.

4. 4

   Score each workflow against the checklist

   Ask how long the identity must persist, whether operators work concurrently, what locations matter, how replacements work, and how cost scales per usable IP.

5. 5

   Test the selected plan with real work

   Test the selected plan with the actual workflow before committing a client or account list to it.

The AliasMode workflow

1. 1

   Assign the chosen proxy type to the profile

   Add the static, sticky, or rotating proxy to the AliasMode profile that matches the workflow.

2. 2

   Preflight before sensitive work

   Run the AliasMode proxy preflight to confirm the exit IP and timezone match the plan.

3. 3

   Document the decision

   Record the session type and reasoning in the profile group or tags so the next operator understands the choice.

Verify it worked

• The chosen session type matches the required identity persistence for that workflow.
• A test run confirms the expected location and replacement behavior.
• The cost per usable IP is calculated, not just the headline price.

Cautions

• Per-request rotation on a persistent account profile can break session continuity and trigger extra verification.