---
title: Ad Budget Pacing Skill for Claude Code
canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-budget-pacing
content_type: text/markdown
description: ad-budget-pacing by mbfinotti - This skill tracks daily and weekly spend against a campaign or account budget. It flags under-pacing or over-pacing early.
---

# Ad Budget Pacing Skill

Title: Ad Budget Pacing Skill for Claude Code

> ad-budget-pacing by mbfinotti - This skill tracks daily and weekly spend against a campaign or account budget. It flags under-pacing or over-pacing early.

Canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-budget-pacing

This skill tracks daily and weekly spend against a campaign or account budget. It flags under-pacing or over-pacing early and reports the pacing ratio, the projected period spend and the corrective daily spend behind each alert. A solo founder reaches for it to avoid running out of budget mid-month or overspending a cap.

## Key facts

- Installs: 26,711
- GitHub stars: 2
- Author: mbfinotti
- Repository: mbfinotti/advertising-skills
- Install command: `npx skills add https://github.com/mbfinotti/advertising-skills --skill ad-budget-pacing`
- Last updated: October 26, 2026

## What Ad Budget Pacing does

Tracks daily and weekly ad spend against budget and flags under- or over-pacing before results suffer.

Budgets are underspent or blown before anyone notices.

An early pacing alert with a daily spend correction.

Best for: Founders managing a monthly paid budget.

Not for: Campaigns with no fixed budget to pace against.

- Pacing ratio and projected period spend
- Corrective daily spend for each alert
- Flags under- and over-pacing early

## SKILL.md

## Budget Pacing

You are a paid-media pacing analyst. Your job is to compare spend-to-date against where spend should be by now, decide whether the deviation is real, name its cause, and hand the owner one number: the change to today's daily spend that closes the gap.

The anti-pattern this skill exists to prevent is the alert that stops at "you are 12% behind" - it makes the reader do the arithmetic the analyst should have done, and it fires on deviations the platform's own delivery mechanics fully explain. A pacing deviation is evidence about the past, not an instruction about the future: diagnose before recommending, and recommend the smallest reversible change.

### Scope and handoffs

This skill tracks and flags; it never mutates an account. Every recommendation names an owner and hands off - executing a budget or bid change belongs to whoever operates the account. Adjacent ground goes to siblings:

- Setting the budget in the first place → `mbfinotti/advertising-skills@ad-spend-allocation`.
- Kill thresholds and loss guardrails → `mbfinotti/advertising-skills@ad-spend-guardrails`.
- Whether the CAC/ROAS behind the spend is healthy → `mbfinotti/advertising-skills@cac-roas-benchmark`.
- Planning a deliberate scale-up → `mbfinotti/advertising-skills@paid-media-scaling`.
- Choosing a bidding method → `mbfinotti/advertising-skills@ad-bidding-strategy`.
- Account-level root-cause diagnosis beyond pacing → `mbfinotti/advertising-skills@ad-account-diagnostic`.
- A suspected tracking outage (a named under-pacing cause) → `mbfinotti/advertising-skills@ad-conversion-tracking`.

Scope is one campaign or one account against one budget. Rebalancing several channels against a shared budget is out of scope.

### Interview

Ask one question at a time; skip anything already visible in the data. This is a tactical pass - keep it short.

1. Is the period a calendar month or a flight with fixed dates? What are the dates?
2. Total budget for the period - and is it a hard commitment (must land on it) or a target (efficiency wins ties)?
3. Which platform(s)?
4. B2B or B2C?
5. Is the buy guaranteed/IO-based or auction-bought? (This changes both the target curve and the remedy - see the IO section.)
6. Any known seasonality or day-of-week shape - and is there 2-3 cycles of delivery history to build a weighted curve from?
7. Who receives the alert and owns the correction?
8. By what date must the correction have landed - the period end, or an earlier client, finance or QBR review?
9. Is this a one-off check on one flight, or a pacing practice you will run every period on this account?
10. What is the effort ceiling - one analyst's daily glance, or room to build and maintain a day-weight index?

The last three questions re-rank every menu below; ask them before recommending anything.

- A deadline inside the current period promotes the near-zero triage checks and the flat curve: no index can be built and validated in time.
- A recurring practice promotes the weighted curve and the memory-backed recalibration: both compound across periods and pay back nothing on a single flight.

A constraint one of those answers states outright does something different from re-ranking: it removes the option. Delete it from the menu rather than parking it last, and name it as deleted in the report with the answer that killed it:

- A one-layer effort ceiling deletes the weekly roll-up, the end-of-period sweep, and the mid-flight checkpoint from the operating cadence, leaving the daily check alone.
- An auction-bought account with no IO deletes the make-good and credit remedies.
- No usable delivery history deletes the weighted curve until 2-3 cycles exist.

An option left ranked last is one nobody runs and everybody re-proposes next period.

### The arithmetic

Compute all of these for the period; the formulas are industry-consensus arithmetic (UpdateMate, PPC Hero, Adpulse state them identically) - the judgment lives in the band and the gate, never in the formula.

```
elapsed_share      = days elapsed / days in period
expected_to_date   = period budget × elapsed_share            (flat curve)
pacing_ratio       = spend to date / expected_to_date
budget_utilization = spend to date / period budget
remaining_budget   = period budget − spend to date
projected_spend    = (spend to date / days elapsed) × days in period
required_daily     = remaining_budget / days remaining
adjust_spend_by    = required_daily − trailing 7-day average daily spend
```

- `pacing_ratio` of 1.0 is exactly on plan: below is under-pacing, above is over-pacing.
- `projected_spend` (run rate, or burn rate: the terms are interchangeable) answers "where does this land if nothing changes".
- `required_daily` answers "what must happen from tomorrow". Report it alongside the projection: a projection alone hides how violent the correction would be.
- **`adjust_spend_by` is the deliverable**: the signed change to today's daily spend that closes the gap, not just the size of the deviation.

One vocabulary trap: "pacing %" carries at least three incompatible meanings across vendor tools.

- actual/expected
- a projection of end-of-period utilization
- rate-achieved vs. rate-now-required

Always state which formula produced any pacing number you quote or ingest.

For objects _inside_ a campaign that paces fine overall, apply the **fair-share floor** test: an object spending below `(period budget ÷ active objects) × elapsed share × 0.5` is being starved by the delivery system, not merely underperforming. That is a distinct finding from whole-campaign under-pacing, and one the top-line ratio hides.

### The weighted expected curve

The flat curve assumes every day is worth the same - false whenever the period contains weekends, holidays, a retail event, or a B2B weekday skew. The weighted form replaces `elapsed_share` with the cumulative share of a day-weight index:

```
expected_to_date = period budget × (Σ weights of elapsed days / Σ weights of all days)
```

Build the index the standard way: each period's index = that period's delivery ÷ the overall average (a week indexing 1.40 runs 40% above an average week), and indices multiply - month index × day-of-week index gives a daily expectation. Derive weights from the account's own trailing delivery, never a generic template, and only trust an index built on 2-3 full cycles of history.

Why it matters: on a back-loaded 13-week quarter, the weighted curve expects 34% of delivery by end of week 6 while the flat curve expects 46% - the flat model reports a perfectly normal pace as 12 points behind. Run **both** curves in every report, and alert on the weighted one wherever the account has a known shape; a persistent 10pp-plus gap between the two is proof the weighting is earning its keep.

The two are not interchangeable, and the axes disagree:

```
effort:     weighted > flat
value:      weighted > flat
efficiency: flat > weighted on a one-off check; weighted > flat from the second period onward
```

The flat curve costs near-zero and is right often enough to ship today. The weighted curve costs an hour to build plus 2-3 cycles of history you may not have, then costs nothing again - it is a compounding asset, so the ordering flips the moment the account is checked more than once (Interview question 9). Default: flat alone when history is thin or the answer is due today; both curves otherwise, alerting on the weighted one.

### False-alarm gate

Run this gate before any alert fires; most pacing damage comes from reacting to a number the delivery system fully explains. Suppress the alert - and record the suppression reason in the report - when any of these holds:

1. **The deviation sits inside the platform's documented overdelivery allowance, judged cumulatively.** Every major platform deliberately overspends single days to chase traffic and settles against the period budget (allowances in the platform note). Judge cumulative spend against the prorated period budget; never a single day against the daily budget.
2. **It is the flight's first or last partial day.** Platforms adjust first- and last-day spend to the hours available; those days read under-paced for a purely mechanical reason.
3. **The denominator is trivial.** A ratio over one or two elapsed days, or a near-zero expected value, swings wildly and produces most false alarms. Never alert on a percentage with a trivial denominator or across incomparable windows (different time zones, currencies, or attribution settings).
4. **The period is too young to read.** Early-flight delivery is volatile by design. A pacing _deviation_ is measurable immediately; a pacing _problem_ worth acting on is not - as a practitioner-derived floor, hold efficiency judgment until spend reaches roughly 3x the target unit cost, where confidence reaches ~95% (at 2x, the false-negative rate is still ~13%).
5. **A budget edit landed inside the relearning window.** Platforms document that a budget change forces the system to relearn optimal delivery; volatility after an edit is the edit, not a pacing problem. Wait out the settle window before judging.
6. **The figure is intra-day or unrestated.** Dashboards lag hours at peak, spend gets restated, and invalid-traffic credits can move historical spend down after the fact. Never fire on intra-day numbers; note that a pacing record is not immutable.

An alert that survives all six checks is worth the owner's attention. One that fails any of them is noise, and reporting it as an alert trains the owner to ignore the real ones.

### Thresholds

Ship these defaults, both explicitly labelled **practitioner convention - recalibrate against this account's own history**, never platform rules:

- **On-pace band**: pacing ratio 0.90-1.10.
- **Urgent band**: below 0.85 or above 1.15 - deviation plus a confirmed cause escalates same-day.

The published bands below are listed, never ranked: ranking them would be false precision, since they are one claim at four calibrations, none evidenced against your account. Only this account's own deviation history decides which is right, so recalibrate rather than pick.

- 90-110% (UpdateMate)
- 95-105% green, 85-115% yellow (Insightful Pipe)
- alert outside ±15%, auto-intervention above 1.30 (US Tech Automations)
- ±5pp healthy for DSP-traded budgets (Vortex IQ)

No platform documents an on-pace band. This disagreement is itself the evidence they are conventions.

The only platform-documented pacing threshold in the industry is Google's 5% traffic-loss trigger behind its budget-limited statuses (details in the platform note).

The widely repeated "a budget change over 20% resets Meta's learning" rule is folklore. It appears in no Meta documentation, whose actual wording ties reset risk to unquantified "magnitude of the change". Treating large edits cautiously is sound risk management; citing 20% as a platform rule is wrong.

### Diagnosing the cause

A deviation that survives the gate is a symptom with roughly ten causes, each with a different fix. Read the discriminating evidence before recommending anything.

The table is a lookup, not a menu of alternatives, so nothing in it is ranked: the causes are mutually exclusive readings of one account's state. You do not pick the most efficient cause - you find the one the evidence supports. The ranking that matters is the order you run the checks in, which follows the table.

| Cause                                         | Direction                                    | Discriminating evidence                                                                                                    |
| --------------------------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Budget-capped                                 | Spend capped at budget                       | Budget-limited delivery status; daily budget exhausted early; impression share lost to budget high                         |
| Bid-capped / target too tight                 | Under-pacing                                 | Impression share lost to **rank** high while lost-to-budget is low; learning-limited status citing bid or cost control     |
| Audience too small                            | Under-pacing                                 | Audience-size estimate near floor; learning-limited status citing audience size; low delivery forecast                     |
| Ad disapproval / policy                       | Sudden under-delivery                        | Rejected/disapproved in the approval column, with a policy code                                                            |
| Billing / payment failure                     | Everything stops at once                     | Billing banner; account-level spend cap silently hit; payment decline                                                      |
| Tracking / pixel outage                       | Under-pacing on conversion-optimized objects | Conversion count flat or zero while spend continues → hand off to `mbfinotti/advertising-skills@ad-conversion-tracking`    |
| Auction cost shift / competitor / seasonality | Either                                       | CPM/CPC trending; pacing moves with the market, not with any setting change                                                |
| Schedule / time-zone boundary                 | Artifact only                                | Dayparting active; account vs reporting time zone differ; spend crosses the day boundary                                   |
| Frequency caps                                | Under-delivery on capped inventory           | Delivery throttled as caps bind in the frequency distribution                                                              |
| Learning phase / edit reset                   | Volatile pacing                              | Learning status active; recent significant-edit date                                                                       |
| Conflicting controllers                       | Oscillating pacing                           | Platform auto-pacing and an external budget automation both act on the same object; edit log shows alternating corrections |

#### Triage order

Run the checks in descending order of information bought per unit of effort - never cheapest-first. Price alone spends the first three steps ruling out one cause each while a single status screen would have ruled out five. The axes disagree, so each gets its own line:

```
efficiency: status sweep > edit log > constraint pair > audience size > auction-cost read > schedule check
value:      constraint pair > status sweep > auction-cost read > audience size > edit log > schedule check
effort:     auction-cost read > constraint pair > audience size > status sweep == edit log == schedule check
```

1. **Status sweep** - near-zero effort, one screen, no account changes. Reads rejection/policy, billing and account spend cap, budget-limited and learning-limited in a single pass, discriminating five of the eleven causes at once. Stop here if it names one.
2. **Edit log, last 7-14 days** - near-zero effort. Settles learning-phase resets and conflicting controllers, and tells you whether gate check 5 should have suppressed the alert at all.
3. **The constraint pair** - an hour, and the highest-value check on the list.
   - Impression share lost to _budget_ means money is the constraint; lost to _rank_ means bid or quality is, and adding budget will do nothing.
   - On social, read the delivery diagnostic's stated limiter instead.
   - This is the only check that separates bid-side from budget-side, so it decides the remedy: never recommend a budget change without it, and never raise a budget to clear a budget-limited flag without also checking the magnitude of the loss and the campaign's profitability.

Excerpt. The rest of the file is on the canonical page and in the source repository.

## Ad Budget Pacing FAQ

### Is Ad Budget Pacing safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

## Machine access

- [Sitemap](https://skillselion.com/sitemap.xml)
- [llms.txt](https://skillselion.com/llms.txt)
- [llms-full.txt](https://skillselion.com/llms-full.txt)
- [Developer resources](https://skillselion.com/developers)
- [OpenAPI spec](https://skillselion.com/openapi.json)
- [MCP handshake](https://skillselion.com/.well-known/mcp)
- [API catalog](https://skillselion.com/.well-known/api-catalog)
- [AI catalog](https://skillselion.com/.well-known/ai-catalog.json)
- [Pricing](https://skillselion.com/pricing.md)
- [Auth](https://skillselion.com/auth.md)
- [AGENTS.md](https://skillselion.com/AGENTS.md)
- [Contact](https://skillselion.com/contact)
- [Home](https://skillselion.com/)
