The right traffic package equals your real daily consumption across all working accounts, multiplied by the number of days it should last, plus a buffer for spikes. There is no universal per-account figure: it depends on how many accounts you run, how often each one connects, and what it does. Buying blindly means either running out mid-campaign or paying for data you never use, so measure first, then buy.
Count Your Active Accounts
Count only the accounts that actually work through the proxy right now, not spares or backups sitting in reserve. An account whose profile isn't open doesn't consume traffic.
- Facebook campaigns: how many ad accounts are live? Include all ad accounts across your different BMs.
- Instagram accounts: are you warming them, posting content, or just holding them? Active posting burns more data than idle holding.
- Google Ads: each account needs its own sessions. Count only accounts with active campaigns.
Be honest here: if only part of your accounts run ads, size for that part.
Estimate Sessions Per Account
A session is one connection to the account: each login, status check, or automated action counts as one. How many sessions an account needs per day depends on the job it does:
- Checking performance: few sessions, light data.
- Launching new campaigns: more sessions, plus creative uploads.
- Warming or farming: the most sessions, whether you do it manually or with software.
- Idle holding: an occasional login or none at all.
If you're using an anti-detect browser with residential proxies for 20+ sessions of account warming, that's heavy traffic. Logging in only to check stats is light. For more on how much traffic a single account consumes, see the dedicated guide.
Calculate Daily Data Consumption
Daily consumption is accounts × daily sessions × average data per session. The per-session figure is the one you need to measure yourself: checking feed and ads uses little, while uploading creatives or loading reports uses much more.
To get it, run your normal workflow for the first few days, note how much the package balance dropped, and divide by the number of sessions. Multiply the daily total by the days the package should last. This is your baseline.
Add Buffer for Testing and Mistakes
Your baseline isn't your final number: add a buffer for work outside the daily routine:
- Testing new accounts before they go live
- Re-checking accounts after platform updates
- Connection failures forcing a re-login
- Setting up new campaigns or creatives
- Passing checks and verification
Size the buffer by how predictable your work is: steady holding needs a small margin, while frequent launches and new accounts need a bigger one.
Account Type Matters
Different account formats burn traffic differently, so count each type as its own group and add the groups up.
- Rental accounts: consumption follows what you do on them. Holding and status checks are light; daily ad work is heavier.
- Farm accounts: heavy usage while you're actively warming them with 20+ sessions. Budget more.
- Autoregs: need more sessions early on for warming, so their traffic is front-loaded.
- KING PZRD: steadier, moderate usage once they're running campaigns.
If some of your accounts are farms under active warming and the rest are rentals on hold, don't apply one average figure to all of them. Calculate each group separately and sum the results.
Geographic Spread and Data Use
Spreading accounts across geos doesn't divide the traffic: every account still consumes its own share, just through a proxy in its own location. Geo changes how you plan, not how much you need.
For accounts in Ukraine, Poland, and the USA, calculate consumption per geo separately, then add the results up. Don't average them, or the geos with the heaviest workload will be underestimated.
Choose Your Package Size
Pick the package tier that covers your baseline plus buffer, not just the baseline. Going below means the package runs out mid-campaign; going far above means paying for traffic you never use. If you're torn between neighboring tiers, take the larger one: a proxy dropping in the middle of account work can cause problems with the ad account.
This math applies to residential proxies only: mobile proxies are sold by time, so there's no gigabyte count to plan for them.
Monitor and Adjust
After the first package, compare your actual usage with the estimate and size the next one accordingly. If the package ran out before the planned date, go up a tier; if a large part was left over, you can go down.
Consumption changes when you add accounts, launch heavier campaigns, or switch to more active warming, so recalculate whenever your workflow shifts. If usage jumps without an obvious reason, check why a package drains faster than planned.
FAQ
How do I calculate how much residential proxy traffic I need?
Multiply the number of working accounts by daily sessions per account and by your measured data per session, then by the number of days the package should last. Add a buffer on top for testing, re-logins, and checks.
Does an idle account use proxy traffic?
Only while its profile is open and sending requests. Accounts held in reserve and not opened don't consume traffic, and occasional logins to hold an account use very little.
Which accounts use the most traffic?
Accounts under active warming, such as farms with 20+ sessions, and fresh autoregs during early warming. Accounts that are only held and checked use the least.