Vazante

Agencies

Managing multiple ad accounts without losing control

The routine, structure and tooling for running many ad accounts at once: what to check daily, what weekly, and how to spot problems before the client does.

Also available in: Português · Español

Running ten accounts is not running one account ten times. The work changes character: it stops being optimisation and becomes prioritisation. The skill that decides the outcome is not knowing how to adjust a bid — it is knowing which of the ten accounts deserves attention today.

The real problem: where to look

With one account, you review everything. With ten, reviewing everything every day is impossible and pointless: most accounts, most days, are fine and need nothing. The cost of running many accounts is not in the adjustments. It is in the time spent discovering which ones need adjusting.

So the routine gets built backwards from what feels intuitive: the whole-portfolio view first, then detail on the two or three that moved.

A routine that survives volume

Daily, ten minutes. One view with every account: today's spend, results, cost per result. You are not analysing, you are hunting anomalies. An account that spent triple, one that spent nothing, a campaign with a full budget and zero conversions.

Weekly, per account. The real analysis, compared against the equivalent previous week. CTR, CPM and frequency enter here, following how to analyse a Meta Ads campaign.

Monthly, business level. Cost per customer, margin, which channel carries the result. That is the client conversation, not the platform one.

If the daily block takes more than fifteen minutes, the problem is not discipline. It is that the portfolio view does not exist and is being rebuilt by hand every morning.

Structure: decide once, benefit forever

Naming convention. A fixed pattern with platform, objective, audience and date. Not bureaucracy: it is what lets you read a ten-account report without opening each one to work out what a line means.

User-level access, never shared passwords. On Meta, access arrives through the client's business portfolio; on Google, by invitation to your user. When the relationship ends, the client revokes and nobody changes passwords.

One place for the change log. What changed, when and why, per account. In a month nobody remembers whether the improvement came from the new creative or from the expensive season ending.

Onboarding an account without inheriting chaos

Every new account arrives with history: campaigns nobody can explain, audiences built by someone who left, exclusion lists with no rationale. The temptation is to start optimising immediately, which means optimising something you do not understand.

A first week spent mapping — what is running, what it costs, what the target is, what was tried before — pays for itself within the month. Write it down in the same place you keep the change log, so the next person does not repeat the archaeology.

The second thing worth doing before touching anything: agree the target number with the client in writing. Accounts inherited without an agreed target produce reports that nobody can judge, and disagreements that surface in month three.

Signals only the portfolio view reveals

Some diagnoses are invisible account by account and obvious in aggregate:

SignalReading
CPM rises across all accounts in the same weekAuction, seasonality. Not your operation
Rises in one account onlySomething changed there
Several accounts with high frequency at onceSmall audiences and budgets that grew
One account with no spendCard declined, campaign paused, limit hit

That last case costs the most and is the easiest to miss: an account that stops spending raises no alarm, it produces silence. Across ten accounts, a weekend with no delivery can go unnoticed until Monday.

Dividing work across two or more people

Splitting by account is the most common arrangement and the worst: each person knows their accounts and nobody knows the portfolio, so holidays become a problem and shared signals go unnoticed. Two alternatives work better:

By task type. One person does the daily sweep across all accounts; another does the week's deep analysis. The first detects, the second resolves.

By rotation. Accounts rotate each quarter. It costs some context and buys something more valuable: nobody is indispensable, and inherited problems surface.

Both make the per-account change log non-optional. Without it, rotation moves the problem rather than solving it.

The tool matters less than the view

People argue about which software to use and rarely about which view they need. The view that sustains a multi-account operation has three properties, whatever produces it:

  • Every account on one screen, same metric, same period.
  • Comparison against the previous period, not just today's value.
  • The ability to drill down without changing context or refiltering everything.

A well-built spreadsheet has all three, and for a while it is enough. It stops being enough when the cost of updating it starts competing with the time available to analyse — usually somewhere between the fifth and eighth account.

The three expensive mistakes

1. Applying one standard to every account. A cost per lead of US$ 30 can be excellent in one account and terrible in another. Without a written target per account, comparisons mean nothing.

2. Changing the wrong account. It happens when many tabs are open and names look alike. Confirming the account name before each action feels excessive until the first time it happens.

3. Reporting the same thing to everyone. Each client has a different objective. A single template saves time and produces reports nobody reads, which costs more than the time it saved.

The handover test

A useful way to check whether your structure actually works: imagine handing one account to a colleague tomorrow, with you unreachable for a week. How long would they need to understand what is running and why?

If the answer is more than an hour, the problem is not workload — it is that the account exists mostly in your head. Naming conventions, a change log and a written target per account are what turn that from a risk into a routine.

This matters beyond holidays. An operation where every account depends on one person's memory cannot grow, because every new client makes the bottleneck worse rather than better.

When to stop taking accounts

The signal is not a number: it is when the weekly block starts getting skipped. If deep analysis slips two weeks running, the portfolio has passed what the current structure supports. From there, every new account degrades the service on all the others, and that shows up in renewals before it shows up in any metric.

For the deliverable side, continue with client reporting for small agencies and the weekly ad report. To set the fee that sustains this routine, see how much to charge for ads management. The pricing page shows the account limits on each plan.

Frequently asked questions

How many accounts can one person handle well?

It depends on complexity, not count. Eight simple accounts with one objective each are easier than three with several platforms, many products and long sales cycles.

Single dashboard or account by account?

A single view to find where to look, and the platform itself for deep work. The mistake is using only one of the two.

How do I get access to client accounts without sharing passwords?

Through business portfolio access on Meta and user-level invitations on Google Ads. Never shared credentials: access is granted to your user and revoked when the relationship ends.

How do I avoid making changes in the wrong account?

Consistent naming, a fixed campaign naming convention, and confirming the account name before every action. Most serious mistakes are context errors, not judgement errors.

Read next