How to Set Up Slack Alerts for Facebook Ad Account Budget Spikes

A CPM spike that starts at midnight and runs until your morning check-in can consume a full day's budget at above-target cost before you see it. For accounts spending £500–£5,000 per day, a single undetected overnight anomaly can cost hundreds of pounds in wasted budget. The fix is simple: get the alert in Slack before you ever open Ads Manager.

This guide covers three methods, from native Meta tooling to automated monitoring — and explains the real limitations of each.

What to Alert On

Before you set anything up, decide which metrics warrant waking you up or interrupting your day. The most actionable triggers for Meta Ads:

• CPM spike >30% vs. your 7-day average — a structural shift, not noise
• ROAS dropping below your profitability floor (e.g., below 2.0x if your break-even is 1.8x)
• Daily spend pacing more than 20% over or under budget — over-delivery burns your budget early; under-delivery means something's wrong with delivery
• Frequency exceeding 3.5 in a 7-day window — leading indicator of creative fatigue before your ROAS has visibly dropped
• CPA exceeding your cost cap by more than 25% — particularly important if you're running cost cap bidding

Alerts on raw numbers (e.g., "CPM above £15") are less useful than alerts relative to your own baseline. A £15 CPM may be normal for your account in November and catastrophic in March.

Method 1: Meta's Native Automated Rules (Email Only)

Meta's built-in automation lives in Ads Manager → Automations → Create Rule. You can configure conditions like:

• Campaign/ad set daily spend exceeds £X
• CPM rises above £X
• CPA exceeds £X

When the condition is met, Meta can send an email notification and optionally pause the affected entity.

Step-by-step:

1. Go to Ads Manager → click Automations in the top navigation
2. Click Create Rule → choose Custom Rule
3. Select the scope: All Active Campaigns, Ad Sets, or Ads
4. Set your condition (e.g., "Daily Spend" → "Is Greater Than" → £200)
5. Set the action: Send Email Notification (to your account email)
6. Set the schedule: Continuously (checks every ~30 minutes)

The limitations:

• Email only — no Slack integration, no push notifications
• 30–60 minute check cadence — not real-time; an anomaly can run for an hour before the rule fires
• Fixed thresholds, not baseline-relative — a £15 CPM threshold set in winter becomes meaningless in Q4 when normal CPM is £22
• No cross-metric intelligence — a simultaneous CPM spike + CTR drop + frequency spike is three separate rules, each needing separate setup

Native rules work as a basic safety net but not as a true monitoring system.

Method 2: Zapier / Third-Party Integrations

Several Zapier templates exist to pipe Meta Ads data into Slack: connect to the Meta Ads API, pull a metric, compare it against a static threshold, and post a Slack message if triggered. Some advertisers also use Google Sheets as an intermediary — Zap pulls daily stats into Sheets, a formula evaluates them, and another Zap posts to Slack if a cell turns red.

The honest trade-off:

• You can get Slack notifications without paying for a dedicated tool
• But you're building and maintaining the logic yourself, and it will break. Meta API versions update, Zap quotas get hit, Google Sheets formulas drift — and you often don't know the monitoring stopped working until you miss an anomaly
• Baseline-relative detection is difficult to build reliably in Zapier; most implementations fall back to static thresholds

Zapier integrations are fine for teams with engineering capacity to maintain them. For most media buyers, the maintenance overhead is the problem.

Method 3: AdEvolver (Real-Time Anomaly Alerts to Slack)

AdEvolver is built specifically for Meta Ad account monitoring, which means the detection logic is already implemented and the Slack integration is native.

Setup:

1. Connect your Meta account — OAuth connection, read-only access. No campaign modifications are made without your explicit instruction.
2. Connect your Slack workspace — from the AdEvolver Settings page, click Connect Slack. You'll choose which Slack channel receives alerts (e.g., #ads-alerts).
3. Configure thresholds — set your baseline preferences: acceptable ROAS floor, CPA cap, frequency threshold. AdEvolver also uses your account's rolling 7-day history as its dynamic baseline for CPM and spend anomalies.
4. Alerts go live — from this point, AdEvolver monitors your account continuously. When an anomaly is detected, a Slack message posts to your chosen channel within minutes of the anomaly's onset.

What makes the alerts useful vs. noisy: The Slack message includes the specific campaign or ad set affected, the metric that triggered it, the current value vs. the baseline, and how long the anomaly has been active. You're not just told "something's wrong" — you're told what, where, and for how long, so you can decide whether to act immediately or monitor further.

For the deeper explanation of what anomalies to look for and why they happen, see Meta Ads Anomaly Detection: Manual vs Automated Monitoring.

Choosing the Right Setup for Your Account Size

| Account Daily Spend | Recommended Setup | |---|---| | < £200/day | Meta native rules (email) as a minimum baseline | | £200–£1,000/day | Zapier if you have engineering time; AdEvolver if you don't | | > £1,000/day | Dedicated monitoring (AdEvolver) — the cost of a missed anomaly exceeds the tool cost within days |

At higher spend levels, the economics of real-time monitoring are clear: catching a single overnight anomaly an hour earlier than a morning email notification would is worth more than the monthly monitoring cost.

Once alerts are live, the natural next step is combining them with an execution layer — so you can act on anomalies without opening Ads Manager. How to Build an Autonomous Ad Account (2026) covers the full monitoring + execution stack.

Get a free ad account audit with AdEvolver.