Multi-Accounting: Browsers and the Rules That Keep Accounts Alive

Multi-accounting gets discussed as a technical problem and usually fails on an organisational one. Here is both halves.

What links accounts

Platforms link accounts through several groups of signals, and they are not equally strong.

Network. One exit address. Covered by proxies.

Environment. The browser fingerprint: system characteristics, fonts, graphics. Covered by an antidetect browser and profile separation.

Behaviour. Identical actions at identical times, identical speed, identical paths through the site. Covered only by discipline.

Data. Emails in one pattern, phones from one range, one card, one delivery address, similar names.

The underrated point: the last group is the strongest. Technical signals require analysis and produce a probability; the same payment card across five accounts is a direct link requiring no analysis at all.

The practical conclusion: flawless technical setup with careless data is pointless.

Isolation

Three levels, and the first is mandatory.

Profiles. Each account gets its own profile with its own cookies, storage and fingerprint. Separate windows of one ordinary browser are not profiles: they share state.

Addresses. One address per account or small group. Stable, not rotating - see rotation.

Physical separation for particularly valuable accounts: a separate machine or virtual machine. Expensive but decisive.

A practical detail people forget: isolation must be permanent. An account that once logged in from the wrong profile or the wrong address is linked forever: the platform recorded it, and fixing it later changes nothing.

Data discipline

Here nothing is solved by tooling, only by process.

• Emails from different sources, not a template with a number. A sequence like name1, name2, name3 is read automatically.
• Phones from different ranges, where phones are needed.
• Different payment methods. One card across ten accounts is the most direct way to link them.
• Different delivery addresses, where delivery exists.
• Plausible profile data. A profile with no avatar, no description and no activity looks like exactly what it is.
• Record keeping. A table mapping accounts, profiles, addresses and data. Without it you will eventually log into the wrong one.

Behaviour

The most underrated part.

Different activity hours. Ten accounts working strictly nine to six is a pattern.

Different speeds. No human performs an action half a second after a page loads.

Different paths. If every account walks the site the same way, that is visible.

Warm-up. A new account that immediately performs the target action is suspicious. Ordinary activity beforehand raises survival substantially.

Gradual rollout. Ten registrations in an hour is a pattern. Ten over two weeks is not.

Where people fail

Five typical failures, by frequency:

1. Identical data despite perfect technique.
2. Logging in from the wrong profile. Once is enough, and the link is permanent.
3. Rotation instead of a stable address for accounts.
4. Identical behaviour.
5. No record keeping. A month later you cannot remember which account is which and you mix them up.

How the platform sees all this from its side: fighting multi-accounting. What actually triggers bans: why accounts get banned. The overview is in the proxy guide.