Check Meta budget pacing mid-month
Mid-month pacing on Meta: run rates against intention, the platform's budget model read correctly.
IntentWhether Meta spend lands the month on target, with the platform's own budget mechanics respected.
- 2
- Steps
- 3
- Tools
- 2
- Rules
- 1
- Failure modes
When to use it
Use it when
- Mid-month, every month.
Do not use it when
- The first days of the month: run rates on two days are noise.
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.
Read budgets and their modes.
Compute month-to-date run rates and project.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Projection misses intention by more than 10%
Conclude
Flag now with the daily delta: month-end surprises are mid-month findings ignored.
When
CBO moves money between ad sets
Conclude
pace the campaign, not the ad set, wherever CBO runs.
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.
- Ad set budgets under CBO are advisory: reading them as caps misprices the month.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.