MARKETING

Weekly UTM Spend-to-Pipeline Reconciliation Rollup

Every Monday, joins last week's ad spend (by UTM campaign) against closed and open pipeline in your warehouse, computes cost-per-opportunity and ROAS per campaign.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday 7am schedule fires
  • ActionQuery last week's spend by UTM campaignGoogle BigQueryBigQuery
  • ActionQuery pipeline opportunities joined on UTM keyGoogle BigQueryBigQuery
  • LogicCompute ROAS and cost-per-opp; flag below floor
  • OutputPost ranked rollup to Slack channelSlack

What it does

This workflow reconciles paid-media spend against the pipeline it actually generated. It pulls spend keyed by `utm_campaign` and matches it to opportunities tagged with the same UTM in your CRM warehouse, then derives cost-per-opportunity, pipeline value, and ROAS for each campaign. The result is a single ranked digest your team reads first thing Monday.

When to use it

Use it when spend lives in one system and pipeline in another, and nobody has a trustworthy weekly view of which campaigns are paying for themselves. Ideal for growth or demand-gen teams running a standing Monday revenue sync.

How it works

A Monday 7am schedule fires the run. The flow queries BigQuery for the prior week's spend grouped by UTM campaign, then queries pipeline (opportunities, stage, amount) joined on the same UTM key. A logic step computes ROAS and cost-per-opp and flags campaigns below a configurable ROAS floor. The ranked table — best to worst — is formatted and delivered to a Slack channel with the underperformers called out at the bottom.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  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.