Diagnose a Meta spend drop fast
The Meta spend-drop sequence: activity log, delivery diagnostics, then auction signals.
IntentWhy Meta spend fell: edits, delivery constraints, or auction.
- 3
- Steps
- 3
- Tools
- 2
- Rules
- 1
- Failure modes
When to use it
Use it when
- Meta spend fell hard against its norm.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Confirm the drop and scope.
Check the activity log around the date.
Run delivery diagnostics on the affected ad sets.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Edits precede the drop
Conclude
Learning reset: 3-7 days of instability is the price already paid; do not compound it with more edits.
When
Diagnostics name a constraint
Conclude
Quote it: Meta usually says why, and the quote beats any theory.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- CBO reallocates between ad sets by design: an ad set's drop under CBO can be the system working.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.