← ClaudeAtlas

facebook-ads-budget-pacinglisted

Use for "am I on track with my Meta budget", "will I overspend this month", "how much should I be spending a day", "which ad sets are capped", "we underspent and I don't know why", "why won't this ad set spend", or a mid-month spend check — even when the user never says "pacing". Also use when someone needs to know whether adding budget to an ad set would do anything at all. Meta / Facebook Ads only.
coupler-io/skills · ★ 33 · AI & Automation · score 72
Install: claude install-skill coupler-io/skills
# Facebook Ads Budget Pacing **Tells you whether you land on budget this month, and which lever actually moves the spend.** Meta does not spend the number you type. It paces to a daily budget but is allowed to run up to 75% over on any given day and balance across the week, ad sets in learning underspend on purpose, and a campaign-budget campaign quietly starves the ad set you care about in favour of the one that is cheaper to fill. So the account both overspends and underspends at once, and the daily figure in Ads Manager tells you almost nothing about where the month ends. **What you get back** - **A month-end projection** with the required daily spend to hit the number, and the over or under in currency and in percent. - **The pacing verdict per campaign** — on track, running hot, or unable to spend — with the reason attached to each, because those three need opposite actions. - **The ad sets that are genuinely capped**, separated from the ones that simply cannot find delivery. Adding budget only helps the first kind. - **A reallocation** that holds total spend constant: where to take it from, where to put it, and the ceiling on each line. - **A coverage statement** — what could and could not be checked. **Read-only.** It never changes a budget or a bid. ## How to run this **Three calls to a spoken answer:** find the dataset → schema and *coverage verdict spoken out loud* → one combined query. **Two calls** when the dataset is already known. Overriding rule