What a platform sees
On every visit a site records the IP address, the browser and the cookies. An agency managing thirty client accounts from one office looks, from the platform's side, like one address with thirty logins. Some platforms accept that. Many restrict it, and a problem on one account can spread to the rest.
The setup
- Give each account its own browser profile, so cookies and browser details stay apart. An antidetect browser does this.
- Give each profile its own sticky session: the same username for all, except the session ID.
- Pick the country the account is really used from, and do not change it.
- Write down which session ID belongs to which account.
A username for one account looks like this. For the next account, change only the session ID.
Sticky username
USERNAME-country-us-time-600-session-a1b2c3d4What undoes it
- Pasting the same finished line into several profiles. The session ID is the same, so the address is the same.
- Letting the session time run out mid-visit, so the address changes while you are logged in.
- Moving an account between countries from one day to the next.
- Logging in once without the proxy "just to check". The platform now has your real address on that account.
A note on rules
Separate addresses are a way to keep unrelated accounts from being lumped together. They are not a way round a platform's limit on how many accounts one person may hold. Check the rules of the platform you work on, and see our acceptable use policy.
Questions
Is a sticky session the same address forever?
No. It holds for the session time, and can end early if the connection behind it drops. Sites accept an occasional change within the same country and provider far more readily than a change of country.
Residential or mobile?
Residential for most desktop work. Mobile for platforms that are mostly used on phones.