MARKETING

Pause campaign rollout when live field CWV breaches budget

On a short schedule it checks Cloudflare RUM for the active campaign's landing page.

CategoryMarketing
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFrequent schedule during campaign
  • ActionRead p75 LCP/CLS from Cloudflare RUMCloudflareCloudflare
  • LogicRequire two consecutive breaches (state in Airtable)AirtableAirtable
  • ActionFlip Vercel launch flag to heldVercelVercel
  • OutputPage on-call channel in SlackSlack

What it does

This workflow is a circuit breaker for live campaigns. It samples real-user Core Web Vitals on a tight interval while a campaign is active, and if performance degrades past budget twice in a row it automatically holds the rollout, records the breach, and escalates, so a degraded page stops receiving fresh paid traffic.

When to use it

Use it during high-spend launch windows where a sudden perf regression (a bad deploy, a runaway third-party tag) would waste budget fast. The two-consecutive-check rule avoids flapping on a single noisy sample.

How it works

  1. 1A frequent schedule triggers during the campaign window.
  2. 2The workflow reads p75 LCP and CLS from Cloudflare RUM for the active page.
  3. 3A logic step requires two consecutive budget breaches before acting, tracking state in Airtable.
  4. 4On a confirmed breach it flips the Vercel launch flag to held and writes the breach record.
  5. 5It pages the on-call channel in Slack with the metric, value, and trend so someone can intervene.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect VercelDeploys, runtime logs, analytics.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.