Open the Changes tab. Every budget move Pace makes (a pacing adjustment, an overspend pause, a resume) is logged there with who or what made it, the reasoning, and the old and new budget per campaign. The Changes tab is the single source of truth for what Pace did on your account and why. If you manage this for clients, that same log is what proves the work happened when it's time to report.
Find the change fast
- Open the Changes tab.
- Use the Filter (by account, platform, and user) and the date-range picker to isolate the entry.
- Read the User column. Pace means the change was automated: a scheduled run, overspend protection, or a month reset. A teammate's name means a person made it.
- Read the Change summary, and hover any badge for the full explanation.
- Click the Change summary to open the Change Report and read the Reasoning and the Change Log: old budget to new budget, per campaign.
Why it happened
When the change is attributed to Pace, it's one of these:
- A scheduled pacing run. Pace adjusts campaign budgets daily so the month lands on your monthly target, and the reasoning explains the move. See how Pace decides what to change.
- Overspend protection paused at the cap. A monitor checks month-to-date spend against your cap every five minutes and pauses active campaigns when spend reaches it. It's logged as, for example, "3 campaigns paused — spend ($10,540) exceeded budget cap ($10,500)." See how overspend protection works.
- A new month rolling over. On the 1st, in your workspace's timezone, Pace resumes anything overspend protection paused, so the month starts clean. If you've set a different amount for the new month with a budget schedule, the next run paces toward that new number.
When the change is attributed to a teammate, that person made it directly — either editing a budget or a setting, or triggering a manual on-demand run with Pace Now or Pace All. See Pace Now and Pace All.
Every change is bounded and reversible
Every recommendation has to sit between a floor (never below the platform's minimum daily spend) and a ceiling built from your monthly budget, the days left, and the campaign's previous budget. The strictest cap wins. So no single day burns a disproportionate share of your month, and no campaign jumps wildly. Overspend pauses reverse too: when spend drops back under the cap, Pace re-enables only the campaigns it paused.
Sometimes a rail (a hard bound on one ad set) and your account's budget envelope (the total your whole account is allowed to spend) pull in different directions. When that happens, Pace always follows the envelope, so your account-level number wins, and notes the conflict on the change record. You'll see it as a small badge on the row, such as "Capped to safe daily maximum" or "Clamped to platform minimum."
Still looks wrong?
Email [email protected] with the account name, the date and time of the change from the Changes tab, and a screenshot of the Change Report (the Reasoning and the Change Log). Naming the exact entry lets support trace it.