Choosing identifiers#
- Random and unique per logical session: a short hash of the account name or task id works well.
- Never reuse an identifier across unrelated jobs, or they will share an exit and a reputation.
- Keep them short and alphanumeric; providers cap the length and the character set.
Identifier scope#
A session id is scoped to your account and to the location parameters used with it: the same id with -cc-de and with -cc-fr are two different sessions. It is also scoped to the gateway: residential and mobile keep separate session tables.
How it works at ProxShift#
On ProxShift the parameter is -sid-, up to 32 characters (a-z, 0-9), combined with -ttl- for the lifetime. Omit it and every connection rotates.