How Many Mobile Proxy Lines Does My Team Actually Need?

Someone on a forum asks: we are a small team managing accounts and ad checks for a few clients, how many mobile proxy lines should we buy? The replies usually range from one to fifty with no reasoning. Here is the reasoning. The number is not about traffic, since every line carries unmetered data, and it is not about addresses, since every line rotates. It is about separation and simultaneity: how many things must be apart, and how many must run at once.

Start with what must be separate

Write down the units that should never share an address. For most teams those are clients. Two clients' accounts seen from one carrier address at the same time is the kind of overlap you are paying to avoid, so each client is at least one line. If one client has several brands that must also look unrelated, each brand is a line. If a team works per seat rather than per client, each seat is a line.

This first count is the floor. A team with six clients has at least six lines. There is no way to make that smaller without putting two clients on one address, and you should not.

Then count what must run at the same time

Within one client, how many accounts or tasks run simultaneously? If one person runs one client's three accounts one after another, one line is enough; the profiles take turns on the same address and that is normal behaviour for a household or a phone. If three people run that client's accounts at the same moment, three profiles on one line are still one address doing three things at once, which is fine for small numbers and gets odd for large ones.

A practical threshold most teams use is a handful of accounts per line per client. Beyond that, add a second line for the client. The price per line is flat at the list price, so the decision is purely about how the activity looks from the outside.

Add metros the clients care about

If a client's work is local, their line should sit in their metro. A client in Houston gets a Houston line; a client in Miami gets a Miami line. If a client is national, pick any metro. If one client needs two cities at once, that is two lines, because one line exits from one metro at a time. Moves between metros are free and keep remaining time, so a client whose city changes from month to month can keep one line and move it.

For a team covering eight clients in five cities, this step rarely adds more than one or two lines beyond the client count.

Keep one or two lines for the team itself

Teams need lines that belong to no client: for checking how a page renders from a US carrier address, for verifying a competitor's visible ad from a given metro, for testing a new tool before pointing it at client work. One general line, two for a busier team, usually on 5G in a large metro. These lines are where new staff learn the tools without touching a client.

Buy the spikes as short lines

Campaigns, audits and one-off regional checks do not need permanent lines. A daily line is $5 on 4G or $6 on 5G; a weekly line is $27 or $31; an hourly line is $2 for two hours on 4G or $3 on 5G, then the same per extra hour up to four hours, and if the task stretches to a day, the hours already paid count toward the daily price. Budget a small floating amount for these rather than buying monthly lines you will not use in week three.

This keeps the permanent fleet equal to the structural need and lets the variable need come and go. The dashboard shows short lines next to permanent ones, so label them with the campaign name and let them expire.

Worked examples

A two-person agency with four clients in three cities: four client lines in the clients' metros, one general line, five monthly lines in total, plus the odd daily line for campaigns. A six-person team running a single national client's many accounts: one line per seat, six lines in two or three metros for variety, one general line, seven in total. A solo operator with two clients: two client lines and nothing else, adding an hourly line when something needs a look from elsewhere.

In every example the count comes from separation and simultaneity, not from data or address volume. The fleet grows when a client is added or a client's activity outgrows a line, and shrinks by letting monthly lines lapse when a client leaves, with unused whole units credited back if you remove a line early.

• Floor: one line per client (or per seat).
• Add: a second line for any client with many simultaneous accounts.
• Add: a line for each additional city a client needs at the same time.
• Add: one or two general lines for the team.
• Variable: daily, weekly or hourly lines for campaigns.

When to buy and when to wait

Buy the floor on monthly terms with auto-renew on. Buy everything else as you need it. A team that starts with the floor and adds a line each time a real conflict appears ends up with the right fleet; a team that guesses high ends up relabelling idle lines. Stock varies by metro and carrier, so if a metro you will need is low, order that line first; lines in large metros are usually available at any time.

Frequently asked