How to diagnose a Meta ad set that stopped spending
The fixed checklist for under-delivery on Meta: diagnostics, audience, schedule, budget and auction, in the order that finds the constraint fastest.
IntentName the binding constraint on a Meta ad set that will not spend, using Meta's own diagnostics before any theory.
- 5
- Steps
- 6
- Tools
- 4
- Rules
- 3
- Failure modes
When to use it
Use it when
- An ad set spends far below budget.
- Delivery stopped without anyone touching the account, apparently.
Do not use it when
- Accounts in payment failure: fix billing first, nothing else matters until then.
- Deliberate cost-cap strategies, where under-delivery is the design working.
What it needs first
Required
Preconditions
- The ad set identified; the account ticked.
- Enough history to know what normal delivery looked like.
Inputs
adsetrequired- The ad set under diagnosis.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Read Meta's own delivery diagnostics for the ad set first.
Meta usually names the constraint outright; the rest of the pass verifies it.
Read the ad set: status, schedule, budget mode, bid strategy.
Read audience size and overlaps.
Read recent activity: edits reset learning and throttle delivery.
Read insights for the frequency and CPM trend before the stop.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Diagnostics name a constraint (audience too narrow, bid too low, learning limited)
Conclude
That is the finding; quote it and size the fix.
When
The activity log shows edits within 48h of the slowdown
Conclude
Learning reset is the default explanation; expect 3 to 7 days to restabilise before other fixes.
When
Frequency was climbing and CPM rising before the stop
Conclude
The audience is saturating; the fix is audience or creative, not bids.
When
A cost cap or bid cap is set below recent CPA
Conclude
The cap is the constraint working as designed; the decision to raise it is a strategy call, not a bug.
Evidence every conclusion must carry
- The diagnosis quotes Meta's diagnostic string when one exists.
- Every explanation is dated against the delivery drop.
Where the agent stops
- Raising caps, widening audiences or resuming ad sets are Safe Writes after human confirmation.
- Structural rebuilds are proposals with expected side effects stated.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Multiple constraints at once: fixing the first named one may only promote the second; re-run after each fix.
- Weekend and seasonal auction swings mimic delivery problems; compare against the same weekday last month.
- Campaign budget optimisation moves money between ad sets by design; an ad set starving under CBO may be the system working.
What the answer contains
- 01Constraint
- The named binding constraint with Meta's own diagnostic.
- 02Fix
- The proposed change, sized, with its Safe Write preview if applicable.
- 03Expectation
- What delivery should do after the fix, and when to re-check.