3 Mar, 2026

5 updates shipped in Pace.

✨ Improved

Improved: Faster Changes page loading

Instant page loads — the Changes page now shows cached data immediately when you navigate to it, then updates in the background. No more loading skeleton flash on every visit.
Lower data usage — the change history query is now capped to the most recent 500 entries, reducing load times and memory usage for workspaces with large histories.

✨ Improved

Pending accounts no longer appear — only active Microsoft Ads accounts are now shown in the Linked Accounts list. Previously, accounts with a pending or inactive status could appear and cause confusion.
All nested MCC accounts now discovered — if your Microsoft Ads setup uses multiple levels of manager accounts (MCCs), all client accounts are now correctly found. Previously, some accounts could be missing if you had more than 100 accounts under a single manager or if a manager link was still pending.
Manager accounts no longer listed as linkable accounts — MCC/manager accounts are now correctly identified and excluded from the account list, so you only see actual advertiser accounts you can link and manage.

✨ Improved

Budget caps are now enforced every 5 minutes — previously, overspend checks only ran when pacing ran (up to 3 times per day). Now a dedicated monitor checks your spend against your budget cap every 5 minutes across all platforms. If your spend exceeds your cap, campaigns are paused within minutes instead of hours.
Smarter campaign resumption — when your spend drops back under your budget cap (e.g., after a budget increase), only the campaigns that were automatically paused are resumed. Campaigns you intentionally paused are left alone.

🚀 New

See account status at a glance — Microsoft Ads accounts on the Linked Accounts page now show a status badge (e.g., "Inactive", "Suspended") next to accounts that aren't currently active. This makes it easy to identify which accounts may need attention before linking them.

✨ Improved

Improved reliability of automated pacing across all platforms — pacing runs are now more resilient to platform-specific delays, expired credentials, and complex account structures.