MARKETING

Untracked Campaign Spend Leak Detector

On a schedule, compares campaigns that incurred ad spend in BigQuery against campaigns present in Salesforce.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList campaigns with spend yesterdayGoogle BigQueryBigQuery
  • ActionList tracked campaign IDsSalesforce
  • LogicDiff spend set against tracked set
  • OutputAlert channel about untracked spendSlack

What it does

Finds the money you cannot attribute. It lists every campaign that spent budget yesterday from BigQuery, checks whether each one exists as a tracked campaign in Salesforce, and flags any spend going to campaigns with no attribution mapping, so dollars stop disappearing into an untracked bucket.

When to use it

Use it when your attribution numbers never add up because new campaigns get launched in ad platforms before anyone wires up UTM or campaign records in the CRM. It is the early-warning system for marketing ops to catch tracking gaps within a day instead of at quarter close.

How it works

  1. 1A daily schedule triggers the check.
  2. 2Query BigQuery for all campaign IDs with non-zero spend yesterday.
  3. 3Query Salesforce for the set of known, tracked campaign IDs.
  4. 4In a logic step, compute the set difference: spending campaigns absent from the CRM.
  5. 5If the leak set is empty, exit quietly; otherwise continue.
  6. 6Post the offending campaigns and their wasted spend to Slack so ops can wire up tracking the same day.

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 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.