pace.

Alert types explained

A plain-English guide to every Pace alert type: what each one watches for, which platforms it covers, and whether it reaches you at once or in the daily digest.

10 min readUpdated 6 Oct 2026

Pace watches your connected ad accounts and tells you when something needs attention. Each alert type below says what triggers it and where it applies, so you can decide which ones to turn on. To switch them on and choose email or Slack, see set up alerts.

Each alert reaches you in one of two ways. Urgent ones fire the moment they're detected. Lower-urgency ones are collected into a single daily digest at a time you choose, so your inbox and Slack stay quiet in between.

Note: Some of the newer alert types are rolling out to workspaces on the Pro plan and above: metric anomalies, trends, conversion tracking, the dead-morning delivery check, account status, and policy issues beyond Google. Until they reach your workspace, their rows either stay hidden or run the earlier version of the check.

Pacing

Pacing Alert. Fires when an account's spend drifts more than 10% from where it should be for this point in the month. It has three severity tiers (warning, serious, and critical), so a small drift reads differently from a blowout. If an account runs in Daily Floor mode (a minimum daily spend you set), this same toggle instead sends its Daily Floor Shortfall and Heads-Up alerts. Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads, and TikTok Ads.

Overspend Monitor. Fires when Pace pauses or re-enables campaigns to keep an account inside its monthly budget. On Google Ads and Microsoft Ads it also carries the restart alert: if a campaign Pace switched back on has served no impressions two days later, you get one message naming it and the status the platform is showing. See overspend protection for how that works.

Pacing Took Place. A summary after each automated pacing run: budgets adjusted, accounts changed, accounts already on pace, and anything deferred or errored.

Budget rollover and Budget rollover failed. The first tells you last month's underspend or overspend was carried into this month's target, and by how much. The second tells you Pace couldn't work out the carry, so the target was left at its base figure. They're separate switches because one is routine news and the other needs a look. See budget rollover.

Flight ended. A custom flight window reached its end date and Pace stopped managing those budgets, so nothing keeps pacing to a plan that's finished. See custom flighting.

Budget override left in place. A campaign Pace had paused to enforce a $0 group budget was switched back on outside Pace. Pace treats that as a deliberate decision, leaves the campaign running, and tells you rather than re-pausing it.

Budgets needed. A sheet-managed account has no budgets uploaded for the month, so its groups hold still until they arrive.

Budget changes blocked. An ad platform is refusing Pace's budget changes on an account until something is fixed on the ad account itself. Today this covers Meta asking for a verified advertiser, which it needs before it will accept budget changes on ad sets aimed at certain locations. You get one alert per account naming the ad sets affected, not one per run. Pace keeps trying on each run and carries on as soon as Meta accepts the change. Meta Ads.

Performance

Metric anomalies. Pace learns what normal looks like for each account, weekday by weekday, then flags a genuine spike or drop while letting ordinary week-to-week movement pass. It covers spend, conversions, conversion value, cost per acquisition (CPA), click-through rate (CTR), cost per click (CPC), and return on ad spend (ROAS). A change that lines up with a budget move you made won't fire, because that's expected. Accounts on the Basic plan, and accounts still building up history, use a simpler percentage-based check so there's no gap. A large, clear anomaly reaches you immediately; a smaller one waits for the daily digest. Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads, and TikTok Ads.

Delivery Alerts. Two ways an account can go dark:

  • Zero impressions — an active account served nothing. Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads, and TikTok Ads.
  • Dead morning — an account that reliably spends by midday hasn't spent a cent so far today. Catching it before lunch means you can fix a lapsed card or a stalled campaign the same day. It only looks at accounts that spend consistently, checks after midday in the account's own timezone, and respects days you've scheduled off. Google Ads, Meta Ads, LinkedIn Ads, and TikTok Ads.

Trend Alerts. Some problems never spike, they drift. This watches a roughly six-week direction in CPA, CTR, CPC, conversions, and ROAS, and flags only the moves that hurt: cost per result climbing, or conversions and ROAS sliding. It needs a consistent multi-week move before firing, so one bad week doesn't set it off. Trends always arrive in the daily digest. Google Ads, Meta Ads, LinkedIn Ads, and TikTok Ads.

Conversion Tracking. A broken conversion tag is expensive because everything else looks fine. This fires when an account records normal spend and clicks but zero conversions on an account that normally converts. It reaches you immediately, and you get an all-clear when conversions resume. It won't fire on weekdays the account doesn't usually convert on. Google Ads, Meta Ads, LinkedIn Ads, and TikTok Ads.

Creative Fatigue. Fires when ad frequency climbs past 4.0, a sign your audience is seeing the same creative too often. Meta Ads, LinkedIn Ads, and TikTok Ads.

Ad Policy Issues. Flags ads and assets a platform has marked disapproved or limited. Google Ads gives full detail, including Performance Max asset-group disapprovals, with the specific reason and evidence. Meta Ads, LinkedIn Ads, and Microsoft Ads report disapproved and under-review ads with the platform's reason where it's provided. TikTok Ads reports a count of affected ads plus a deep link into the platform, since TikTok doesn't expose per-ad reason text.

Intelligence

Findings. AI-generated findings about an account's performance, delivered in-app. You opt in or out per account rather than workspace-wide. See Findings.

Record Broken. Fires when an account sets a new all-time performance record, with the previous best for context. Every platform.

Billing

Spend Limit Warning and Spend Limit Exceeded. These track your Pace plan's managed spend against its limit, not any single account's platform billing. They stay workspace-wide.

Account status

Ad account status. Watches each connected account's health on the platform side. Pace tells you right away when a connected account is suspended, disabled, or closed, and on Meta Ads, LinkedIn Ads, Microsoft Ads, and TikTok Ads it also catches a billing hold, a payment grace period, or a drained prepaid balance. You get an all-clear once the account is serving normally again. Google Ads exposes account-level suspension and closure rather than billing status, so its alerts cover the serving side.

Note: This is your ad account's own payment and serving status inside the platform, not your Pace subscription. Your plan and managed-spend limits live under Billing.

Connections

Google sign-in stopped working. Fires when a connected person's Google sign-in stops working, for example because someone removed Pace from their Google account. The alert names the person and says which linked accounts use their login, so you know who to reconnect. It comes once per outage, and a brief Google hiccup doesn't raise it. It goes to the bell, and by email to every owner and admin plus your workspace's alert email recipients, on every plan. On Pro and above it also goes to your default Slack channel when Slack is connected. If an account is left with no connected person who can reach it, that account's own alert channel or recipient list gets a note about just that account. There's no switch for it in Settings, because the affected accounts can't be paced until someone reconnects. Any workspace member can reconnect. Reconnect from Manage profiles on the Google Ads card. See connect Google Ads.

LinkedIn sign-in expired. The LinkedIn equivalent. The bell alert names the person and the accounts affected, and email and Slack reach the same people as other sign-in alerts. See connect LinkedIn Ads.

Other sign-ins stopped working. Meta Ads, Microsoft Ads, TikTok Ads, Reddit Ads, Amazon Ads, and X Ads raise the same kind of alert when their login stops working. It goes to every owner and admin plus whoever gets the affected accounts' alerts, in the bell and by email, and in Slack on Pro and above. Each person gets one message per outage. See reconnect or remove an ad account.

Data source disconnected. Fires when one ad account stops sending data to Pace while its login still works. Usually a client removed Pace's access, for example from their manager account or Business Manager, or the account was closed. Each account in the message comes with a plain reason. It covers all eight platforms: Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads, TikTok Ads, Reddit Ads, Amazon Ads, and X Ads.

  • Severity: critical, so it doesn't wait for the digest. Pace needs two failed checks about two hours apart before it alerts, so it usually arrives within a few hours of the loss. It only covers accounts Pace has seen working at least once.
  • Who gets it: every workspace owner and admin, plus whoever gets that account's alerts (its own Slack channel and recipient list, or the workspace defaults). It goes to the bell and by email on every plan, and to Slack on Pro and above when Slack is connected. If a client removes a batch of accounts at once, each person gets one message listing their accounts, and a client contact only sees their own. When data flows again, you get an all-clear.
  • Muting: only an owner or admin can mute it, one account at a time, from the three-dot menu on the alert. Members don't see that option.
  • Why the account's Alerts switch doesn't silence it: that switch quietens an account's routine alerts. Losing access to the account means Pace can't pace or report on it, so owners and admins always hear about it. Its row in Settings is locked on for the same reason.

Where you'll see it in Pace, not just your inbox. A red strip across the top of every page names the affected platforms for as long as any account is disconnected, and the account's own page carries the same strip. On Linked Accounts, the affected row also carries a Not reachable badge. All three clear on their own once the account is fixed. There's nothing to dismiss.

For what each reason means and how to fix it, see why isn't my ad account syncing.

Sensitivity and the daily digest

Two workspace settings shape how the newer alerts behave, both on the Alerts card in Settings → Notifications:

  • Sensitivity — a single low / medium / high dial for the metric anomaly and trend checks. Low surfaces only large, unambiguous changes; high gives earlier, more frequent heads-ups. Medium is the default.
  • Digest time — the hour your daily digest arrives. Everything non-urgent is grouped into that one send, routed the same way your alerts are, so a client's digest only mentions that client's accounts.

Muting one alert type on one account

If a single alert type gets noisy on a single account, silence it there without turning it off everywhere. Every per-account alert row carries a three-dot menu with Mute {type} alerts for this account, and the mute covers the bell, Slack, email, and the digest. Pacing, overspend enforcement, Findings, and your weekly report keep running, so muting stops the notification while the automation carries on. It's available on every plan, and it holds until someone reactivates it. The one exception is Data source disconnected, which only an owner or admin can mute. See your alerts inside Pace.

What's Pro and what's not

Email delivery works on every plan. Slack delivery, per-client routing, and the newer alert types need the Pro plan or above: metric anomalies, trends, conversion tracking, the dead-morning delivery check, account status, and policy issues beyond Google. If you turn on account status and later drop below Pro, the alerts you already switched on keep running.

Was this helpful?

Your feedback helps us improve the help centre.

Related articles

Set up alertsTurn on the right Pace alerts, send each one to email or Slack, and route any client's notifications to their own channel, all from workspace Settings.Your alerts inside PaceRead every alert Pace sends without leaving the app — the bell, the home page, and each account's own Alerts tab — plus a one-click mute for noisy ones.Findings: what Dot flags automatically for youFindings are cards from Dot that surface the anomalies and opportunities across your accounts worth attention. For a few cases Dot attaches a fix you can apply, which only pauses things, switches off a network or ad slice, lowers bids at weak times, or adds negative keywords, and never touches budgets. Formerly called Sparks.Stop your ad accounts from overspendingYour monthly budget is a hard ceiling. When an account reaches it Pace holds every campaign at $1 a day, or pauses them until the 1st if you ask it to.Budget rolloverCarry an underspend or overspend from one month into the next so a month that lands off target gets corrected rather than lost. Switch it on per account.Pace a budget to a flight, not a monthPace an account or campaign group to its own start and end dates, weighted phases, or a repeating cycle, so your budget matches how the campaign runs.Connect Google AdsConnect Google Ads, link the accounts you want paced, and add a Google sign-in for each person on your team. Manager accounts and nested sub-MCCs work too.Why isn't my ad account syncing?Your ad account stopped updating? Find the cause in a minute (an expired connection, an unlinked account, or a permission change) and get it syncing again.