Most arbitrageurs and SMM specialists make the same mistake: they either buy too small a proxy pool and end up with a chain of bans, or they overpay for an excessive number of IPs "just in case." In reality, calculating a proxy pool for multi-accounting is a specific math problem that depends on the platform, type of proxy, and the intensity of actions on the profiles. In this article, we will discuss how to calculate the exact number of unique IPs for 100 profiles without wasting your budget.
Why You Can't Just Take 1 IP for 1 Profile
The logic of "100 profiles = 100 IPs" seems correct, but in practice, it is either excessive or risky — depending on the platform. Let's break down both cases.
If you manage 100 Instagram accounts for an SMM agency and log into each 2-3 times a day for 10-15 minutes, the strict binding of "1 IP = 1 profile forever" is an overpayment. A residential IP that is idle 23 hours a day can be used more efficiently through scheduled rotation, while maintaining session uniqueness for each account.
On the other hand, if you are farming and running ads on Facebook Ads with high budgets, saving on IPs can cost you more than losing an advertising account. Facebook builds a relationship graph between accounts not only by IP but also by browser fingerprint, cookies, and behavior. However, a shared IP across multiple active ad accounts is the first signal for the anti-fraud system that the accounts are linked. The result: one banned account can lead to a chain ban.
The correct approach is to count not the number of profiles, but the number of simultaneously active sessions and the risk level of the platform. These are the two key parameters of the formula we will discuss next.
Proxy Pool Calculation Formula
The basic formula for calculating the IP pool looks like this:
IP Pool = Number of Profiles × Platform Risk Factor
The risk factor is a conditional value from 0.3 to 1.0, indicating how strictly the platform detects links between accounts:
| Platform | Risk Factor | IPs for 100 Profiles |
|---|---|---|
| Facebook Ads | 1.0 (strict) | 90-100 unique IPs |
| TikTok Ads | 0.9 | 80-90 unique IPs |
| Instagram/TikTok (organic, SMM) | 0.5-0.6 | 50-60 IPs with rotation |
| Google Ads | 0.7 | 70 unique IPs |
| Wildberries/Ozon (price monitoring) | 0.3 | 30 IPs with rotation are sufficient |
| Avito | 0.6 | 60 unique IPs |
An important nuance: the risk factor decreases if you spread activity over time (not logging into all 100 profiles simultaneously), and increases if you are working with payment data or advertising budgets — there, any link between accounts leads to immediate blocking of the entire chain.
Residential, Mobile, and Data Center Proxies: Which to Choose
The type of proxy affects the final number of IPs in the pool just as much as the platform does. Different types of proxies are perceived differently by anti-fraud systems, and this directly impacts the required pool size.
| Proxy Type | Trust Level of Platforms | When to Use |
|---|---|---|
| Residential Proxies | High | Instagram, TikTok, Facebook — primary working tool for farming |
| Mobile Proxies | Maximum | Facebook Ads, TikTok Ads — where the risk of banning is highest |
| Data Center Proxies | Medium/Low for social networks | Parsing Wildberries, Ozon, Avito — does not require high trust |
Practical conclusion: for 100 profiles on Facebook Ads, it is wiser to take 60-70 mobile or residential IPs with proper rotation than 100 data center IPs, which the platform will recognize as a proxy network instantly. Conversely, for price monitoring on marketplaces, 100 data center addresses will be much cheaper and will handle the task without risk, as the marketplace's anti-fraud system is focused on protection against parsing, not on detecting multi-accounting.
Calculating for Specific Platforms
Let's consider three real scenarios with exact figures that can be used as templates for your calculations.
Scenario 1: Arbitrageur, 100 Facebook Ads Accounts. Here, the risk factor is at its maximum — 1.0. Each account needs a dedicated unique IP that does not change throughout the account's lifecycle (from registration to the last ad campaign). The result: 100 static mobile or residential IPs, tied 1:1. It is not worth saving here — the cost of a banned account with an advertising budget exceeds the cost of an extra 20-30 IPs.
Scenario 2: SMM Agency, 100 Instagram and TikTok Accounts for Clients. Access to profiles occurs on a schedule, not simultaneously, and without advertising transactions. Here, a pool of 50-60 residential IPs with a sticky session (binding for 24 hours to a specific profile) and subsequent rotation can be applied. This reduces costs by almost half without increasing bans, provided the rule is followed: one IP — one profile within a single session, without parallel logins.
Scenario 3: Seller, Monitoring Prices on 100 Product Cards on Wildberries and Ozon. Here, we are not talking about profiles, but about parsing requests. A pool of 20-30 data center IPs with automatic rotation for each request is sufficient — marketplaces block based on the frequency of requests from one IP, not on the fact of multi-accounting. This is the most budget-friendly scenario of the three.
Static IP vs Rotation: Which is Safer for Profiles
A separate question when calculating the pool is whether rotation of IPs is needed or if the profile requires a constant static address. The answer depends on the type of activity:
- Static IP (sticky, from 24 hours to indefinitely) — mandatory for Facebook Ads, TikTok Ads, Google Ads accounts. The platform sees the same IP at each login, which looks natural for a real user.
- Session Rotation — suitable for parsing marketplaces and social networks without authorization. Each new request comes from a new IP, reducing the risk of rate-limit blocks.
- Scheduled Rotation (every 12-24 hours) — a compromise option for SMM profiles without high risk: the IP changes not during the active session, but between them.
A common mistake is using a rotating pool for advertising accounts. If the account's IP changes every few minutes while working with Ads Manager, Facebook's anti-fraud system perceives this as a sign of hacking or bot activity and blocks the account instantly, regardless of the advertising budget size.
Budget Calculation Example for 100 Profiles
Let's put everything together with a specific example of mixed load: the agency manages 100 profiles, of which 40 are Facebook Ads accounts, and 60 are organic Instagram accounts for content management.
| Profile Group | Proxy Type | Mode | Number of IPs |
|---|---|---|---|
| 40 Facebook Ads Accounts | Mobile | Static, 1:1 | 40 |
| 60 Instagram Accounts | Residential | Sticky 24 hours + rotation | 35-40 |
The result: instead of 100 static IPs according to the "naive" formula, 75-80 addresses are actually required with proper distribution according to activity types. Saving 20-25% of the pool without increasing the risk of bans is the goal of accurate calculation.
Setting Up Proxies in Anti-Detect Browsers
After calculating the pool, the next step is to correctly assign IPs to profiles. In anti-detect browsers like Dolphin Anty, AdsPower, Multilogin, GoLogin, or Octo Browser, this is done at the profile creation level:
- Open the settings of the new profile → "Proxy" section.
- Select the connection type — HTTP, HTTPS, or SOCKS5 (for mobile and residential proxies, SOCKS5 is usually recommended).
- Insert the connection details: IP, port, username, password, provided by the proxy supplier.
- For advertising accounts, enable the "Sticky session" option to ensure the IP does not change with each login.
- Check the geolocation and time zone of the profile — they must match the geo of the IP address; otherwise, the anti-fraud system will notice the discrepancy.
- Save the profile and test the connection through the built-in IP check before the first launch.
Most anti-detect browsers allow you to import a list of proxies in bulk via CSV or direct insertion of strings in the format IP:port:username:password, which saves time when setting up 100 profiles at once — there is no need to manually enter data into each profile.
Common Mistakes in Pool Calculation
- One IP for multiple advertising accounts "to save money." This is a direct path to a chain ban: as soon as one account is banned, the platform checks the entire IP and the accounts associated with it.
- Using data center proxies for Facebook Ads and TikTok Ads. Such IPs are easily identified as server-based, and advertising accounts get blocked during verification.
- Ignoring geolocation. If a profile is registered from Russia, and the proxy is connected from Germany without prior "warming up," this triggers a security check.
- Calculating the pool without considering peak load. If 100 profiles log in simultaneously at 9 AM, and the pool is calculated for even distribution throughout the day, some sessions will operate with overlapping IPs.
- Lack of backup IPs. The pool should include 5-10% spare addresses in case some IPs end up on the platform's blacklists at the time of launch.
Conclusion
Calculating a proxy pool for 100 profiles is not a universal number but a formula that depends on the platform, type of activity, and risk level. For Facebook Ads and TikTok Ads accounts, almost complete 1:1 binding with static mobile or residential IPs is required. For organic profiles on Instagram and TikTok, 50-60% of the number of accounts is sufficient with proper rotation. For parsing marketplaces like Wildberries and Ozon, the pool can be reduced to 20-30 addresses with automatic rotation for each request.
If you are launching advertising campaigns or farming accounts with a high risk of blocking, we recommend considering mobile proxies — they provide the highest level of trust from platforms. For everyday management of social media profiles, residential proxies with flexible sticky session settings work well, and for price parsing and competitor monitoring on marketplaces — economical data center proxies. Proper distribution of IPs across these three types is the key to calculating the pool without overpaying.