MARKETING

Untagged & Mismatched Revenue Quarantine

On new Stripe payments, checks whether the customer carries a valid UTM tag matching a known BigQuery campaign and logs any untagged or unrecognized-campaign revenue to Airtable…

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe payment succeededStripeStripe
  • ActionConfirm campaign exists in spend tableGoogle BigQueryBigQuery
  • LogicRoute untagged / unknown-campaign revenue
  • OutputAppend flagged revenue to Airtable queueAirtableAirtable

What it does

It protects attribution data quality at the source. Every time a payment succeeds, it inspects the customer's UTM tags and verifies the campaign actually exists in your BigQuery spend table. Revenue that is untagged, or tagged to a campaign nobody is spending on, gets quarantined into an Airtable cleanup queue.

When to use it

Use it when your ROAS numbers feel off because revenue isn't reliably tagged, or when sales-assisted and organic deals leak in without UTMs. It gives ops a concrete worklist instead of a vague 'attribution is broken' complaint.

How it works

  1. 1A Stripe payment-succeeded event triggers the workflow.
  2. 2The customer's `utm_campaign` and related tags are read from Stripe metadata.
  3. 3A BigQuery lookup confirms whether that campaign exists in the spend table.
  4. 4A logic branch routes the payment: tagged-and-known revenue passes through untouched; untagged or unknown-campaign revenue is flagged.
  5. 5Flagged records are appended to an Airtable quarantine table with amount, customer, raw tags, and reason for manual attribution fix.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  3. 3
    Connect AirtableBases, tables, views, automations.
  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.