MARKETING

Trip a Budget Guardrail When Creative CPA Creeps Up

On a schedule, reads cost-per-acquisition by creative from BigQuery, detects sustained CPA inflation that signals fatigue.

CategoryMarketing
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule triggers the CPA check
  • ActionQuery per-creative CPA trend from BigQueryGoogle BigQueryBigQuery
  • LogicDetect sustained CPA creep past tolerance
  • ActionOpen a Linear budget-cut task per offenderLinearLinear
  • OutputAlert the channel in SlackSlack

What it does

This workflow guards efficiency by catching creatives whose cost per acquisition is steadily climbing — a downstream symptom of fatigue that CTR alone can miss. When a variant's CPA creeps past its tolerance for multiple days, the flow turns it into an owned, trackable budget-cut task.

When to use it

Use it when you manage to a CPA or ROAS target and want fatigue caught at the conversion layer, not just the click layer. It is ideal for performance teams who act through a ticketing system.

How it works

A schedule triggers the check. The flow queries BigQuery for per-creative CPA across a trailing window and a logic step identifies variants showing sustained creep beyond their target tolerance, filtering out one-day noise. For each confirmed offender it opens a Linear task assigned to the channel owner with the creative, its CPA trend, and a recommended budget reduction. A Slack alert summarizes the cuts so the team sees them immediately.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  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.