MARKETING

Unmatched UTM Spend Anomaly Detector

Runs daily to find ad spend on UTM campaigns that produced zero matching pipeline records, and alerts the marketing-ops channel so broken or mistagged campaigns get caught fast.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionRead yesterday's spend by UTMSnowflakeSnowflake
  • ActionRead pipeline touches by UTM in attribution windowSnowflakeSnowflake
  • LogicIsolate spend with zero matched pipeline above threshold
  • OutputAlert marketing-ops channel if anomalies foundSlack

What it does

This workflow hunts for spend that isn't tying back to anything. It compares yesterday's spend-by-UTM against pipeline records carrying the same UTM tags and surfaces every campaign that spent real money but generated no matched opportunities or leads. These are usually tagging mistakes, broken redirects, or campaigns pointed at dead pages.

When to use it

Use it when UTM hygiene is a recurring problem and you want a daily tripwire instead of discovering a month of wasted, untracked spend at the end of the quarter.

How it works

A daily schedule triggers the check. The flow reads yesterday's spend grouped by UTM from Snowflake, then reads pipeline touch records keyed on UTM over a configurable attribution window. A logic step left-joins spend to pipeline and isolates campaigns with spend above a dollar threshold but zero matches. If any are found, it formats an alert listing campaign, spend, and the suspected cause, and sends it to Slack; if the list is empty, it stays quiet to avoid noise.

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.