MARKETING

Rotate Ad Spend Off CTR-Decaying Creatives

Pulls daily per-creative ad metrics from BigQuery, flags variants whose 3-day CTR has dropped a set percentage below their rolling 14-day baseline.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires the fatigue scan
  • ActionQuery per-creative metrics from BigQueryGoogle BigQueryBigQuery
  • LogicCompute 3-day CTR vs 14-day baseline
  • LogicFlag creatives decaying past threshold with live spend
  • OutputPost ranked pause-and-reallocate list to SlackSlack

What it does

This workflow watches each active ad creative for early fatigue and tells your media buyer which variants to pause before performance collapses. It compares a creative's recent click-through rate against its own healthy baseline, so a strong-but-tiring ad gets caught while it still has salvageable spend.

When to use it

Run it when you maintain a rotating library of paid social or display creatives and want a daily, evidence-backed call on what to retire. It is built for teams whose spend outpaces their ability to eyeball every variant.

How it works

A daily schedule fires the run. The flow queries BigQuery for per-creative impressions, clicks, and spend, then computes each creative's trailing 3-day CTR and 14-day baseline. A logic step flags any creative whose recent CTR sits more than the configured threshold below baseline and still carries meaningful spend. Flagged creatives are sorted by wasted-spend impact and written to Slack as a ranked block, naming each variant, its decay percentage, and yesterday's burn. The buyer pauses and reallocates from one message.

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.