MARKETING

Block campaign launch when Vercel preview fails Core Web Vitals budget

When a Vercel preview deployment for a landing page finishes, it runs a Lighthouse audit and blocks the campaign-ready flag if LCP or CLS exceed budget.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVercel preview deployment succeedsVercelVercel
  • ActionRun Lighthouse audit on preview URLBrowserbase
  • LogicCompare LCP and CLS to budget
  • ActionSet launch-ready flag / hold launchVercelVercel
  • OutputPost pass/fail verdict to SlackSlack

What it does

This workflow turns Core Web Vitals into a hard gate on your campaign launch. Every time a landing-page branch ships a Vercel preview, it audits LCP, CLS, and TBT against budgets you set, then either marks the page launch-ready or holds it and tells the channel exactly which metric failed.

When to use it

Use it when a marketing or growth team pushes paid traffic to landing pages and a slow or janky page silently burns ad spend. It prevents a launch from going live on a preview that would tank conversion before anyone manually checks Lighthouse.

How it works

  1. 1A Vercel deployment-ready webhook fires when a preview build for the landing-page project succeeds.
  2. 2The workflow pulls the preview URL and runs a headless Lighthouse audit against it.
  3. 3A logic step compares LCP (<= 2.5s) and CLS (<= 0.1) to budget.
  4. 4On pass, it sets a launch-ready flag and posts a green verdict to Slack. On fail, it holds the launch and posts the failing metric plus the preview URL so the team can fix before spending.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect BrowserbaseHeadless browsers, sessions, replays.
  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.