Daily Meta Ads spend anomaly alerts in Slack

By General Input

Every weekday at 8am, get a Slack alert flagging runaway spend, broken tracking, and CPA drift in your Meta Ads account, with plain English next steps.

Integrations

  • Meta Ads
  • Slack Bot

Type

Agentic Task

Categories

  • Marketing

Every weekday at 8am in my local time zone, run a spend and pacing anomaly check on my Meta Ads account and post the result to a single Slack channel.

Data pull: use Meta Ads to list the campaigns in the account, then pull yesterday's performance metrics at the account level, campaign level, and ad set level (spend, impressions, CPM, CTR, CPA, ROAS, and conversions). Also pull the last 7 days of daily metrics per campaign so the agent can compute a trailing 7 day average for spend and CPA.

Anomaly detection: for each active campaign, decide whether any of these three conditions are true, and flag it if so.

1. Runaway spend: yesterday's spend was more than 150% of that campaign's trailing 7 day average daily spend.

2. Broken tracking: yesterday's spend was above a minimum floor (default $50) but attributed conversions were zero.

3. CPA drift: yesterday's CPA was more than 50% higher than the trailing 7 day average CPA.

Skip any campaign that is still in the LEARNING phase or has fewer than 3 days of delivery history, because the baselines are unreliable there. The agent should reason about what qualifies rather than treat these rules as brittle absolutes: if a campaign has been paused most of the week or its baseline is clearly noisy, note that and move on.

Output: post a single message to a Slack channel (I will pick the channel at setup) using the Slack bot. Structure the message like this.

Header line: a red, yellow, or green status. Red if there is at least one runaway spend or broken tracking flag. Yellow if there are only CPA drift flags. Green if nothing is off.

Account summary: one line with yesterday's total spend, total conversions, blended CPA, and ROAS for the account.

Per flagged item: campaign name, anomaly type, the specific numbers that triggered it (yesterday's value vs the 7 day baseline), and a one line recommendation. Use these recommendations: 'Pause or investigate' for runaway spend, 'Check pixel and conversion setup' for broken tracking, 'Lower budget or refresh creative' for CPA drift. The agent can rewrite these to fit the situation.

If everything looks healthy, post a short green message confirming the account looks fine and list yesterday's totals so I know the check ran.

Setup inputs I should be asked for: the Meta Ads account (or accounts) to monitor, the Slack channel to post to, the send time and days, the runaway spend multiplier (default 150%), the zero conversion spend floor (default $50), and the CPA drift threshold (default 50%).

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them