Account spending limits are one of the most misunderstood settings in Ads Manager. Advertisers confuse them with billing thresholds, campaign budgets, and account-level restrictions, and the confusion tends to surface at the worst possible moment — mid-scale, when a campaign suddenly stops spending for no visible reason.
What a spending limit actually is
An account spending limit is a self-imposed cap you (or your finance team) set on total spend for an ad account, found under Billing settings. It's a safety control, not a Meta-imposed restriction — you set it, you can raise or remove it, and it simply stops delivery once cumulative spend for the account hits the number you configured.
This is distinct from a campaign or ad set budget, which controls pacing for that specific campaign, and distinct from a billing threshold, which determines how often you're charged as spend accumulates, not how much total spend is allowed.
Why this trips up scaling accounts
The classic failure mode: an account is set up months ago with a conservative spending limit as a precaution, spend climbs steadily, and one day delivery just stops with no policy notice, no restriction, nothing in Account Quality. The team burns hours investigating a 'ban' that's actually just a self-set ceiling reached.
This is especially common on agency or shared accounts where the limit was set during initial account setup by someone who is no longer on the team, and nobody remembers it exists until it's hit.
How to manage limits proactively at scale
If you're running an account toward meaningful daily spend, remove the arbitrary limit entirely or set it high enough that it will never be the constraint — the real safety rail should be your daily budget caps and monitoring, not a forgotten billing setting. Document the current limit (or lack of one) for every account in your portfolio as part of onboarding.
For teams scaling fast, check spending limits alongside payment method health before every major budget increase. A spend cap and a declined card produce identical symptoms — a campaign that stops delivering — but require completely different fixes.
- Check Billing settings, not campaign settings, when delivery stops with no policy flag
- Remove or raise limits proactively before a scaling push, not reactively after it stalls
- Document each account's spending limit status as part of your onboarding checklist
Spending limits vs. account-level restrictions
It's worth being precise about the difference, because the fixes are unrelated. A spending limit is something you configured and can change instantly in Billing settings. An account restriction is Meta's enforcement action tied to policy or risk signals, and it requires an appeal or account-quality remediation, not a settings change — covered in depth in the restricted-account article in this series.
When you see delivery stop, check the spending limit first — it takes thirty seconds to rule out — before assuming you're dealing with a restriction and going down the appeals path.
Building this into your process
Power Ads clients running high-volume agency accounts get this checked as part of standard account monitoring, since a forgotten spending limit on a $30,000/day account is an expensive mistake to catch late. Whether you're on agency infrastructure or your own accounts, the fix is the same: know your limits, document them, and never let a self-imposed cap be the thing that quietly stalls a scale.
Key takeaways
- Account spending limits are self-set caps in Billing settings, not Meta enforcement
- They're a common, invisible cause of campaigns that suddenly stop delivering
- Check Billing before assuming a restriction when delivery halts unexpectedly
- Raise or remove limits proactively ahead of scaling pushes
FAQ
Where do I find my account spending limit?
In Ads Manager, go to Billing settings for the ad account — the spending limit is set and edited there, separate from campaign and ad set budgets.
Can a spending limit cause an account restriction?
No. Hitting a spending limit simply pauses delivery until you raise the limit; it has no bearing on Account Quality or policy status.
