MARKETING

Daily field-data CWV regression watch from Cloudflare RUM

Each morning it pulls real-user Core Web Vitals from Cloudflare for your live landing pages, compares them to yesterday's baseline.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionPull p75 RUM CWV from CloudflareCloudflareCloudflare
  • ActionLoad baseline from AirtableAirtableAirtable
  • LogicFlag pages over budget or regressing
  • OutputPost ranked table to SlackSlack

What it does

This workflow monitors Core Web Vitals from real visitors, not synthetic labs. It reads Cloudflare RUM p75 LCP, CLS, and INP for each tracked landing page once a day, diffs against the stored baseline, and surfaces only the pages that got worse so the team isn't drowning in green dashboards.

When to use it

Use it after launch, when synthetic Lighthouse scores look fine but field data tells the real story. Good for catching slow third-party tags, image regressions, or CDN issues that only show up under real traffic and would quietly erode campaign ROI.

How it works

  1. 1A daily schedule triggers the run.
  2. 2The workflow queries Cloudflare Web Analytics RUM for p75 LCP, CLS, and INP per landing-page path.
  3. 3It loads the prior baseline from Airtable and computes per-page deltas.
  4. 4A logic step flags any page exceeding budget or regressing beyond a threshold.
  5. 5If flags exist, it posts a ranked Slack table and writes today's values back to Airtable as the new baseline.

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