MARKETING

Spend-Without-Revenue Campaign Alert

Hourly check that flags any UTM campaign accumulating ad spend in BigQuery with zero matching Stripe revenue over a rolling window, and pages the channel to pause it.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHourly schedule
  • ActionRolling 72h spend per campaignGoogle BigQueryBigQuery
  • ActionMatching Stripe revenue per campaignStripeStripe
  • LogicKeep spend-over-floor + zero-revenue campaigns
  • OutputAlert Slack with pause recommendationSlack

What it does

It catches the most expensive marketing failure mode: campaigns burning budget that produce no revenue. On a rolling window it compares spend to revenue per UTM campaign and alerts the moment a campaign crosses a spend floor while still showing zero attributed Stripe revenue.

When to use it

Run this when you have several live campaigns and want an early-warning tripwire rather than discovering wasted spend at end-of-month. Tune the spend floor and window to your typical conversion lag.

How it works

  1. 1An hourly schedule triggers the check.
  2. 2BigQuery returns rolling 72-hour spend per `utm_campaign`.
  3. 3Stripe revenue for the same campaigns and window is pulled and totaled.
  4. 4A logic step keeps only campaigns where spend exceeds the floor AND revenue is zero, accounting for the conversion-lag window.
  5. 5If any qualify, a Slack alert lists each offending campaign, its burned spend, and a recommended pause. If none qualify, the run ends silently.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect StripeCustomers, subscriptions, payments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.