MARKETING

Daily Spend-vs-Pipeline Anomaly Escalation

On a schedule, compares each campaign's blended cost-per-opportunity from BigQuery and Salesforce against its trailing baseline.

CategoryMarketing
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule after data load
  • ActionFetch trailing + current spend by campaignGoogle BigQueryBigQuery
  • ActionFetch opportunities by campaignSalesforce
  • LogicCompute CAC baseline and flag degradations
  • OutputRaise incident for breached campaignsPagerDutyPagerDuty

What it does

Watches attribution efficiency and pages a human only when it breaks. It computes today's blended cost-per-opportunity per campaign by joining BigQuery spend with Salesforce opportunity counts, compares each campaign to its own trailing 14-day baseline, and raises a PagerDuty incident for any campaign whose CAC spiked past the configured threshold.

When to use it

Use it when budget is large enough that a runaway campaign can burn thousands before anyone notices in a weekly review. It is for growth ops teams who want exception-based alerting on attribution quality, not another dashboard nobody opens.

How it works

  1. 1A daily schedule fires after data lands.
  2. 2Query BigQuery for per-campaign spend over the trailing window plus today.
  3. 3Query Salesforce for opportunities created per campaign over the same window.
  4. 4In a logic step, compute each campaign's CAC baseline and today's value, then flag degradations past the threshold.
  5. 5If nothing breaches, exit; otherwise raise a PagerDuty incident per offending campaign with the spend and CAC delta attached.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  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.