MARKETING

Overspend Underperformer Pause-Recommendation Alert

Twice weekly, flags UTM campaigns whose spend has crossed a budget cap while ROAS stays below target.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerTwice-weekly schedule fires
  • ActionQuery trailing-window spend and pipeline by UTMSnowflakeSnowflake
  • LogicSelect campaigns breaching spend cap and ROAS floor
  • LogicResolve campaign owner and compose recommendation
  • OutputSend owner-targeted pause alert to SlackSlack

What it does

This workflow catches campaigns that are burning budget without returning pipeline and pushes an actionable recommendation, not just a metric. It identifies UTM campaigns that have both exceeded a configured spend cap and stayed under a target ROAS over a trailing window, then routes each one to its owner with the spend, pipeline, ROAS, and a recommended action.

When to use it

Use it when budgets leak into campaigns that quietly stopped converting, and you want a recurring forcing function that puts a pause-or-keep decision in front of the right person twice a week.

How it works

A twice-weekly schedule triggers the check. The flow queries the warehouse for trailing-window spend and matched pipeline by UTM campaign. A logic step selects only campaigns breaching both the spend cap and the ROAS floor, and looks up each campaign's owner from an ownership map. For each flagged campaign it composes a recommendation message — pause, reallocate, or investigate — with the numbers inline, and delivers it as a direct, owner-targeted Slack alert.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.