Pacing Console docs

How pacing works

Available onFirst month freeProEnterprise

Pacing Console judges each campaign against what it should have spent by the exact hour its spend was pulled, on its own schedule and flight dates, then projects the month end from that run rate.

The idea in one picture

Most pacing sheets compare spend with a straight line through the calendar month at the end of the day. Pacing Console compares spend with what should have been spent by the hour the number was pulled, counting only the days the campaign is meant to run. A campaign pulled at 3 pm is judged against 62.5% of today, not all of it.

How pace is judgedCumulative spend over the month. The expected line rises from zero to the budget across the active days. On day 12 the actual spend sits above the expected line, so pace is above 100%, and the projected line continues the run rate to month end, above the budget. Day 1Month endData pulled
Actual spendExpected (ideal pace)ProjectedBudget

In the picture, the campaign has spent a little more than expected by the time its data was pulled, so its pace is above 100%. If it keeps that run rate, it finishes above budget: that is the Projected number.

The four numbers behind every row

NumberWhat it means
ExpectedThe share of the budget that should be spent by the hour the data was pulled, counting only active days inside the flight dates.
PaceSpend divided by expected. 100% is exactly on plan.
ProjectedMonth-end spend if the campaign keeps its month-to-date run rate.
Daily to hitThe daily budget that spends exactly what is left by month end.

The exact formulas are in the Glossary and formulas.

Schedules and flight dates change the expected line

  • Pacing curve: Even, weekdays only counts Monday to Friday only. Saturday and Sunday add nothing to expected spend.
  • Front-loaded expects more spend early in the flight (the first day counts 1.5 days, the last 0.5) and Back-loaded the reverse. The budget stays the same; only the expected line, the pace and the daily amount to hit budget follow the curve.
  • Flight starts and Flight ends narrow the month to the days inside the flight. Before the flight starts, expected is zero; after it ends, the campaign shows Not in flight, or Over budget if it kept spending.
  • A Budget plan by month replaces the monthly budget for that month only.

How a status is chosen

Each campaign gets one status, checked in this order:

StatusWhen
PausedYou set the campaign's Status to Paused in Pacing Console.
Not in flightToday is outside the flight dates and nothing was spent. If it spent, it is Over budget.
No dataNo spend has arrived for the campaign this month.
No budgetNo monthly budget, no month plan and no daily budget from the platform.
Over budgetSpend to date is already above the month's budget.
OverpacingPace is above 100% plus your tolerance, or the campaign spent before its schedule started.
UnderpacingPace is below 100% minus your tolerance.
Not startedExpected spend is still zero and nothing has been spent.
On pacePace is within 100% plus or minus your tolerance.

The tolerance is Pacing tolerance (%) in Settings, Business and pacing: 10% by default, from 1% to 50%. With 10%, anything from 90% to 110% pace is on pace. A client can have its own band: on the Clients page, open the client and set On-pace band for that client. Its campaigns then use that band on the board, in alerts and in Autopilot; leave it empty to use the workspace's.

Budget cycles that start mid-month

For clients billed on another day, set Budget cycle starts on in Settings, Business and pacing. With the 15th, pacing runs from the 15th to the 14th of the next month: the expected spend, pace, run-out, alerts and Autopilot count from that day, spend before it is left out, and the budget is the plan of the month the cycle starts in. The header reads Day 8 of 30 · budget cycle Nov 15 to Dec 14. The default, the 1st, is the calendar month. Charts by day and month still show calendar months.

Freshness

Every row shows when its data last arrived and from which source (script, Google Ads API, LinkedIn sync, TikTok sync, manual entry or daily import). Data older than Flag data older than (hours) (12 by default) is marked stale and the board shows Data has stopped. Demandbase and 6sense send spend by day, so they are flagged only after 48 hours.

Platforms report spend with a delay of up to a few hours. A small gap right after midnight is normal, and LinkedIn counts days in UTC, so a LinkedIn day ends at 7 pm Eastern in winter.

Was this page helpful? If something is missing, unclear or wrong, tell our support team.

Last updated