
- The reliable rule: one account, one address, one browser profile
- A platform links accounts not only by IP but also by browser fingerprint and cookies
- A shared address is acceptable when the accounts are openly linked anyway: one store's team
- Every platform has its own rules on the number of accounts, and a proxy does not override them
The short answer: one. The rule "one account, one address" is the most reliable, and the reasons are explained below. But there are situations where a shared address poses no risk, and situations where a separate address is not enough.
How platforms link accounts
Social networks, marketplaces and ad systems try to work out which accounts belong to the same person. To do that, they compare signals:
- IP address: the simplest signal, two accounts regularly logging in from the same address;
- browser fingerprint: screen, fonts, time zone, system version;
- cookies and local data: they stay in the browser after login;
- behavior and account data: phone, email, payment details, activity time.
The address is only one of the signals. That is why a separate proxy without a separate browser profile does not solve the problem: the fingerprint and cookies remain shared. More in the glossary: browser fingerprint.
When one address for several accounts is acceptable
- Employees of one company work with one account or with accounts that openly belong to that company anyway.
- The platform itself allows several accounts per user and does not hide this in its rules.
- You use a mobile address: carriers put hundreds of subscribers online through one IP, so a shared address is ordinary there in itself. But the other signals still have to differ.
When each account needs a separate address
- You run accounts for different clients, and they must not be linked to each other.
- You have several stores or ad accounts with different business details.
- A restriction on one account must not affect the others.
| Situation | Address | Browser profile |
|---|---|---|
| One account, one person | its own | its own |
| A team and one shared account | shared by the team | each employee has their own |
| Accounts of different clients | separate for each | separate for each |
| Several stores of one owner | separate for each | separate for each |
How to set up your workspace
- Create a separate profile for each account in an antidetect browser.
- Assign each profile its own proxy from the account's country.
- The address must not change during the session. Prokso has ports from 10000 to 20000 for this: each one holds a single address for 1 to 120 minutes. Give each account its own port.
- Set the time zone and language in the profile to match the address country.
- Label the profiles and ports so you do not mix up which address belongs to which account.
Step-by-step settings for specific programs are in the guides section, and the general procedure is in the multi-accounting use case.
Which proxy type to take
For logging in to accounts, people take residential or mobile addresses: platforms expect the owner to log in from home or from a phone. Datacenter addresses are a worse fit for this; they are kept for collecting open data without logging in to an account.
Common mistakes
- One proxy with rotation on every request for logging in to an account: the platform sees a user who appears from a new place every second.
- Different addresses but one browser profile: the accounts are linked by fingerprint and cookies.
- An address from one country, a time zone from another.
- An abrupt change of login country for an account that has been active for a long time.
FAQ
Can I run two accounts from one IP?
Technically yes, but the platform will see the shared address and may link the accounts. If they must not be linked, each one needs its own address and its own browser profile.
Is changing the IP enough to keep accounts from being linked?
No. Platforms also look at the browser fingerprint and cookies. You need a separate profile for each account.
Which proxy type is better for accounts?
Residential or mobile with an address that does not change during the session. Datacenter proxies are a worse fit for logging in to accounts.


