Connect Slack to Pace, and your pacing alerts, overspend pauses, weekly reports, and the Pacing Took Place run summary post straight into the Slack channels you choose. Set one default channel for the workspace, then route any client's notifications to that client's own channel.
Slack delivery runs alongside email, so you can send the same alert to both or pick one.
Note: Slack is a Pro plan feature, available on Pro, One, and Enterprise. Basic workspaces can't connect it. Connecting or disconnecting affects every member of the workspace.
What you'll need
- A Pace workspace on the Pro plan or above.
- A Slack workspace where you can approve app installs.
- The public channel you want Pace to post into by default.
Connect Slack
- Open Settings and select the Notifications tab. The Slack card sits at the top, above Alerts.
- Click Connect Slack. Pace sends you to Slack's own approval screen.
- On Slack's screen, choose the Slack workspace to install into, then approve. This screen is Slack's, not Pace's.
- Slack returns you to Settings, now connected but without a default channel yet.
- Set Default channel for this workspace to the channel you want and click Save. Pace joins that channel automatically so it can post there. Use the built-in Search channels… box to filter the list, which is sorted A–Z. Alerts, Sparks and weekly reports all go here unless an account picks its own channel.
- In the Alerts card, tick Slack on each alert type you want.
Once connected, the Slack card shows a Connected to: badge with your Slack workspace name, the default-channel dropdown, and a Disconnect Slack button.
Route a client to its own channel
Every ad account can override the workspace default and send its notifications to its own channel, ideal when each client watches a separate Slack channel.
- In your accounts list, open the account's settings with its gear icon and scroll to the Notifications section.
- Set the Slack channel to the client's channel. The first option, Use workspace default, keeps the account on the workspace channel.
- Save.
You pick that channel once and everything Pace sends for the account follows it: alerts, Sparks, and the weekly report. Beside it, Email recipients does the same job for email.
An account override always wins. Leave the account on Use workspace default, and its notifications follow the workspace channel instead. To silence one account's alerts without touching its pacing, weekly report, or Sparks, turn the Alerts switch off further down the same section.
Send one notification type somewhere else
Open Advanced in the same section if a client wants Sparks and the weekly report in different channels. It holds a Sparks channel, a Weekly report channel, and a Weekly report email list, each of which applies to that one thing. Leave any of them on Use account channel or Use account recipients and it inherits the account fields above.
Accounts that already split their routing this way show a Custom badge on the Advanced row, so you can spot them without opening the section.
Note: A few events stay workspace-wide and ignore per-account routing: the Pacing Took Place run summary, plus the plan's Spend Limit Warning and Spend Limit Exceeded billing alerts.
What lands in Slack
Every alert you enable posts as a one-way message. Depending on what you turn on, that includes pacing alerts with severity tiers, overspend pauses, the Pacing Took Place run summary, ad policy issues across Google, Meta, LinkedIn, Microsoft, and TikTok, Pace Insights, and the weekly performance report as a formatted metrics grid. Which alerts exist and how each one behaves lives in setting up alerts.
Lower-urgency alerts don't post one at a time. They're collected into a daily digest that posts as a single grouped message per channel, so a channel that's routed to a client sees only that client's accounts. Urgent alerts still post the moment they happen.
Some messages carry a link button, like View Changes, that deep-links back into Pace. Those are shortcuts into the app. You don't approve or pause anything from inside Slack.
Disconnect Slack
In the Slack card, click Disconnect Slack and confirm Disconnect in the dialog. This removes the connection from Pace and stops all Slack notifications across the workspace. Reconnect any time by authorising again.
Troubleshooting
- You approved the wrong Slack workspace. If you belong to several Slack workspaces, it's easy to pick the wrong one on Slack's screen. Disconnect, then reconnect and choose the right one.
- The channel you want isn't in the dropdown. The picker lists public channels only, so private channels don't appear there.
- Messages aren't landing. Pace joins the channel it's given automatically, but if that didn't happen, invite the Pace app to the channel in Slack.
What Pace can see in your Slack
Pace posts into the channels you choose; it never reads your Slack conversations. The connection uses four Slack permissions and nothing more: post messages, post to the single channel you approve during setup, see the names of public channels, and join public channels. None of them grant access to your message history or search, so Pace can't read what your team writes. The connection is stored in your workspace's private data and never logged.