Why pacing breaks in multi-platform accounts
Most pacing sheets are a weekly export pasted next to the media plan. By the time someone notices a TikTok ad group that spent its month early, or a Snapchat flight running far behind plan in its last week, the money is gone or the plan is missed. The data exists on each platform; the plan sits in a different file.
Whathead keeps both in one place. The approved plan becomes the baseline, the platforms report live spend, and the board does the arithmetic per campaign and ad set.
What the pacing board shows
| Column | Meaning |
|---|---|
| Planned budget | From the brief, a saved budget plan, or entered manually, with daily or lifetime type |
| Spend to date | Live spend read from the platform |
| Flight progress | Share of the flight elapsed, drawn as a marker on the spend bar |
| Projected total | Spend to date plus the current daily budget for the remaining days |
| Status | Under pace, on track or over pace against the expected range |
| Buying unit | The KPI the line was bought on, for example CPA |
Tolerance by sensitivity
| Sensitivity | Allowed deviation from plan |
|---|---|
| Relaxed | 40% |
| Balanced | 25% |
| Strict | 10% |
Alerts that explain themselves
When pacing drifts, the alert says why in plain numbers: how much was spent, the expected range at this point, how far through the flight the campaign is, the flight length and the tolerance applied. For projections it shows spend so far, the daily budget, the days remaining and the planned total. The same module checks budget type (daily vs lifetime), lifetime maths, flight length, and how the budget is split across ad sets compared with the plan. Alerts follow the Anomaly Engine workflow: an owner, an SLA, email notifications and escalation to a specialist and then a manager.
Set up pacing
Add the plan
Upload the approved brief (XLSX, XLS or CSV), pick live entities from the Ads Manager picker, or enter planned budget, type and buying unit by hand.
Map lines to live campaigns
Link each plan line to the campaign or ad set that delivers it. Saved budget plans can be edited later.
Choose sensitivity
Relaxed, balanced or strict sets how far spend may drift before an alert.
Act from the board
Select rows and raise or lower Meta budgets by a percentage. Campaign budget (CBO) campaigns get one change at campaign level, never one per ad set.
Limits today
Bulk budget changes from the board are sent to Meta only; selected rows on other platforms are skipped with a notice. Google Ads, LinkedIn and Reddit are not on the pacing board. For a Google Ads budget change, Whathead's Google reporting screen has a budget editor.
Frequently asked questions
Is budget pacing included in my plan?
Pacing is part of the Anomaly Engine, which is in early access and enabled per workspace. Contact Whathead to request it.
How is the projected spend calculated?
Spend to date plus the current daily budget multiplied by the days left in the flight, compared with the planned total within the tolerance you picked.
Can it change budgets automatically?
From the board you push a percentage change yourself (0.1% to 50%, up to 100 entities at once). Rule-based automatic budget changes exist for Meta, X and DV360 on critical alerts, when automatic actions are on, and can be undone.
Does it work with lifetime budgets?
Yes. The board handles daily and lifetime budgets and checks that lifetime budgets have the flight dates the maths needs.
Can I pace Google Ads campaigns here?
Not yet. The pacing board covers Meta, Snapchat, TikTok, X and DV360.
Run it from one workspace
Every plan starts with a 14-day free trial. Only successful live work is metered.