Pacing one Local Services Ads budget is a manageable weekly habit. Pacing thirty at once is a different problem entirely. Portfolio-level LSA budget pacing is the discipline of keeping many independent weekly budgets funded, on-target, and out of trouble simultaneously—without a master dial to pull, and without the luxury of watching each account the way you would if it were your only one. Done well, it is invisible. Done poorly, it looks like a portfolio where a few accounts are always dark, a few are always over cap, and nobody noticed until the month closed.
There is no master budget—only many budgets
The first thing to accept is that LSA gives you no portfolio-level budget control. Budgets are set per account, so a portfolio is not one big budget to steer; it is dozens of separate weekly budgets, each with its own exhaustion risk, its own under-spend risk, and its own drift. "Portfolio pacing" is therefore a monitoring-and-adjustment problem across many dials, not a steering problem on one. Any tool or process that promises to pace your whole fleet from a single lever is misdescribing how LSA works.
The two pacing failures, multiplied
Every account can fail pacing in one of two directions, and across a portfolio both are usually happening somewhere at any given time:
- The "Wednesday Problem." A budget exhausts by midweek and the account goes dark for the back half of the week—invisible exactly when demand is still flowing. In a portfolio, several accounts can be dark right now while you're looking at the roll-up.
- Silent under-spend. A budget that never gets spent isn't saving money—it's forgoing reachable jobs. Under-spending accounts don't raise alarms the way an overspend does, so they can idle for weeks.
The insidious part at portfolio scale is that these can net out. Two accounts running dry and two under-spending can leave the fleet's total spend looking exactly on plan—while four accounts are individually mispaced. The average lies; the accounts tell the truth.
Manage two views at once
Portfolio pacing requires holding two altitudes simultaneously. The roll-up tells you whether total spend and overall efficiency are on plan. The per-account view tells you which specific accounts are off-target and why. Stop at the roll-up and you fly blind to the accounts that need you; drown in the per-account view and you can't see the whole. You need both, and you need to connect them.
| View | Question it answers | Failure if you rely on it alone |
|---|---|---|
| Roll-up | Is total spend and efficiency on plan? | Hides mispaced accounts that net out in the average |
| Per-account | Which accounts are dry, idle, or over cap? | No sense of the whole; can't prioritize |
| Exceptions | Which accounts need action right now? | —the view you actually act on |
Manage by exception, not by roster
You cannot give thirty accounts equal, careful attention on a schedule that keeps each well-paced—not manually. The habit that scales is exception management: surface only the accounts that have crossed a pacing threshold—running dry early, sitting under-spent, or projecting past their cap—and act on those, while the healthy accounts run untouched. Reviewing every account equally every cycle wastes attention on accounts that are fine and, worse, spreads it too thin to catch the ones that aren't. The goal is to spend your limited attention exactly where the portfolio is off-target.
Protective pacing comes first
Within the exceptions, order matters. Protective conditions outrank growth ones across the whole portfolio, just as they do in a single account. An account projecting past its cap or one that's gone dark midweek during live demand needs handling before you fine-tune a healthy account's budget upward. And the protective moves themselves follow the standard rules: when trimming an over-pacing account, reduce toward a floor rather than pausing—fully pausing an LSA campaign risks weeks of ranking recovery—and when funding a starved one, add in measured steps rather than one big leap that overshoots the sweet spot.
Why cadence is the real constraint
The hard limit on portfolio pacing is how often each account can actually be checked and adjusted. A budget only reveals a pacing problem when someone looks at its trajectory; between looks, a mispaced account is simply losing—either going dark on demand it could have captured or idling on budget it could have spent. An agency reviewing accounts monthly gives each account roughly one pacing check in thirty days, and a weekly budget can run dry and cost a full dark half-week many times before that monthly check arrives. The wider the gap between checks, the more pacing leakage accumulates across the fleet.
This is why portfolios plateau under manual pacing: every account you add stretches the same attention thinner, widening the gap between checks and letting more accounts drift between them. The way past the plateau isn't heroic effort—it's a pacing loop that runs at the same cadence whether the portfolio is five accounts or fifty.
The portfolio pacing loop
- Accept there's no master budget—pace many per-account budgets in parallel.
- Watch roll-up and per-account together; never trust the average, which hides netted-out mispacing.
- Manage by exception—act on the accounts crossing a pacing threshold, leave the healthy ones alone.
- Protect before you grow: handle over-cap and dark accounts first, with floors and steps, not pauses and leaps.
- Hold the cadence: the tighter and more consistent the pacing loop, the less leaks between checks.
Portfolio pacing rewards the same virtues as everything else in multi-market LSA—consistency, protective discipline, and a refusal to trust the average. The operators who pace fleets well are simply the ones who never let an account coast just because it's one among many.
Frequently asked questions
Can I set one budget to pace all my LSA accounts?
No. LSA budgets are set per account, so there is no master budget that spreads across a portfolio. Portfolio-level pacing means monitoring and adjusting many individual weekly budgets in parallel—watching each for early exhaustion, under-spend, or drift past its cap—rather than steering one central dial.
What is the 'Wednesday Problem' in portfolio LSA pacing?
It's when a weekly budget exhausts by midweek and the account goes dark for the rest of the week, missing demand during its dark period. Across a portfolio, this can be happening in several accounts at once while others sit under-spent, which is why per-account pacing visibility matters more as you scale.
How do I keep a whole LSA portfolio on target?
Watch two views at once: a roll-up for total spend and efficiency, and a per-account view that flags which specific accounts are running dry, under-spending, or drifting over cap. Manage by exception—act on the accounts that are off-target while the healthy ones run—rather than judging the fleet on its average.