Multi-Account Setup Checklist: What to Check Before You Run
Updated:
Before running several accounts, work through six areas: the platform's rules, legitimate account details, the device layer (antidetect profiles), the network layer (one dedicated static proxy per account), day-to-day behaviour, and a record sheet to keep track of it all. Most mass problems do not come from one big mistake but from one small item that was skipped and then repeated on every account. The checklist below works for social media, marketplaces and ad accounts, with links to detailed guides for each part.
1. Platform rules and purpose
This comes first because it shapes everything else. Proxies and antidetect browsers do not make accounts immune to bans; if the way you use an account breaks the terms, no technical setup will save it.
- Read the rules on accounts per person, business accounts, ad accounts and re-creating accounts after a ban.
- Prefer official tools where they exist: business managers, admin roles, partner access. They are usually safer than many separate logins.
- Write down what each account is for and which client it belongs to. If you cannot explain a legitimate purpose for an account, do not create it.
- Never use multiple accounts for self-reviews, fake engagement, promotion abuse or ban evasion.
2. Account details
- Each account has its own email and phone number, genuinely owned by you or your client.
- Turn on two-factor authentication and store recovery codes somewhere safe, away from your work machine.
- Payment details, addresses and business names must be real and belong to the right person or company. Never borrow or buy identities.
- Do not share one card or payment account across accounts you want kept apart; that links them more strongly than any IP.
3. Device layer: antidetect profiles
- One antidetect profile per account. If the idea is new to you, read what an antidetect browser is.
- Keep fingerprints stable and plausible: an OS close to your real machine, parameters that do not change on every launch.
- Never log into the same account from a regular browser and an antidetect profile.
- Skip unnecessary extensions; each one is another thing profiles have in common.
- Handle cookies and sessions as described in cookies and sessions for multiple accounts.
4. Network layer: a proxy per account
Each account needs its own IP, kept for the long term. The table summarises what to check.
- Pick a type: high-volume secondary accounts can use dedicated IPv4, valuable accounts are worth static ISP. See IPv4 or ISP: which to use.
- Spread large batches across several ranges; IP subnets and multiple accounts explains why.
- Align time zone using matching time zone and language to your proxy.
- Test each IP with the proxy checker and the WebRTC leak test before the first login.
| Item | Do | Avoid |
|---|---|---|
| Number of IPs | One IP per account | Several accounts on the same platform sharing an IP |
| IP type | Dedicated IPs not shared with other customers | Free or shared proxies with unknown history |
| Stability | Static IP, renewed to keep it | Constantly changing IPs on accounts that work fine |
| Country | Matches the account's market | IP in one country, account details in another, without reason |
| Alignment | Time zone and language match the IP | Browser clock set to another country |
5. Behaviour
- New accounts start slowly, like real new users: complete the profile and use basic features before posting heavily or running ads.
- Do not perform the same sequence of actions at the same time on every account.
- Do not log into dozens of accounts within a few minutes.
- Give each account its own content; mass duplicate content is a clearer trace than any IP.
- When an account is asked to verify, handle it properly rather than creating a replacement account.
6. Records, access and monitoring
Once you pass a few dozen accounts, most incidents come from confusion: the wrong proxy on a profile, an IP that was not renewed, a former employee who still has access. A simple spreadsheet prevents most of it.
- Working as a team? Read how to share proxies with a team safely.
- Renewing on the dashboard before expiry keeps the same IP, so set reminders from the expiry column.
| Column | Why |
|---|---|
| Account, platform, owner | Know who it belongs to and what it is for |
| Antidetect profile | Avoid opening the wrong profile |
| Proxy IP and expiry date | Renew on time to keep the IP |
| Person in charge | Revoke access when people change |
| Status and incident notes | Spot patterns when several accounts hit the same issue |
Start small before you scale
Do not buy for the whole plan at once. Run a few accounts on a few IPs for one or two weeks, note the results, then expand. For larger orders, read how to test proxies before buying in bulk. Platform-specific advice lives on the multi-account and MMO use case page.
Frequently asked questions
Do I need an antidetect browser if I already have dedicated proxies?
If you run several accounts on the same platform from one computer, yes. A proxy separates IPs only; cookies and fingerprints stay shared without separate profiles.
How many accounts can share one IP?
For accounts on the same platform, keep one account per IP. One IP can serve a few accounts on different platforms belonging to the same person.
If I follow the checklist, am I safe from bans?
No. The checklist reduces linking signals and operational mistakes, but platforms still judge behaviour, content and compliance with their terms.
Which proxy country should I choose?
The country that matches the account's market and details. A Vietnamese shop uses a Vietnam IP; an account serving US customers uses a US IP.
Does an account lose its IP when the proxy expires?
If the proxy lapses, the IP may be assigned to someone else. Renew on the dashboard before expiry to keep the same IP.
A dedicated proxy for every account
Each IP is assigned only to you, stays fixed for the rental and is kept on renewal. Automatic activation after payment and 24/7 ticket support.
See pricing