Map persistent profiles to stable proxy sessions.

Before you start

• An inventory of active profiles that need proxy access
• Access to each profile's proxy configuration in AliasMode
• A proxy provider account with available IPs

Step-by-step

1. 1

   Count profiles that need a stable proxy

   Count active profiles that need simultaneous or recurring proxy access. Record the account purpose, market, profile owner, selected proxy type, and replacement history.

2. 2

   Add the proxy to the profile

   Add the proxy to the profile and run the preflight check before using it for real work.

3. 3

   Record the exit IP and assignment

   Record the observed exit IP after preflight. Use a static IP or a provider's sticky session when the workflow expects continuity.

4. 4

   Reserve capacity for concurrency and replacement

   Reserve enough active proxies for concurrent profiles and expected replacements.

5. 5

   Change one assignment at a time

   When a proxy needs to change, update one profile at a time, verify the new exit, and update the operating record.

The AliasMode workflow

1. 1

   Assign the proxy in the profile

   Open the profile in AliasMode and add the HTTP, HTTPS, or SOCKS5 proxy details.

2. 2

   Run the preflight check

   Run the AliasMode proxy preflight to confirm the connection, exit IP, and timezone before opening the browser.

3. 3

   Group and tag for capacity planning

   Use groups and tags to track proxy type and review date, then use the agency proxy budget calculator to plan replacement capacity.

Verify it worked

• Every active profile has a recorded proxy protocol, provider, and expected region.
• The observed exit IP from the preflight matches the expected country or region.
• The assignment and review date are logged for each profile.

Cautions

• Changing a proxy without a preflight check can break session continuity for recurring accounts.