MARKETING

Block promotion when a new third-party tag pushes the landing page past its weight budget

On each Vercel preview, audits the third-party scripts loaded on key landing routes against a JavaScript and request budget.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVercel preview deployment readyVercelVercel
  • ActionCapture third-party scripts + sizesBrowserbase
  • LogicCheck tags vs allowlist + JS budget
  • ActionPromote preview if within budgetVercelVercel
  • OutputHold + post offending tags to SlackSlack

What it does

Guards the most common cause of landing-page CWV decay: third-party tags. On every preview it inventories the third-party scripts and their transfer size on key routes, compares them to an approved budget, and blocks promotion when a new analytics, chat, or ad tag pushes blocking JavaScript over the line.

When to use it

Use it when marketing and growth add tags through tag managers faster than engineering can review them. It makes the script budget enforceable at deploy time instead of discovered later in field LCP and INP.

How it works

  1. 1A Vercel preview deployment-ready webhook fires.
  2. 2The flow loads each tracked route in a headless browser and captures the third-party request list with sizes.
  3. 3A logic step diffs the inventory against the approved tag allowlist and the total JS weight budget.
  4. 4If within budget, it promotes the preview through the Vercel API.
  5. 5If a tag is new or over budget, it holds promotion and posts a Slack breakdown of the offending scripts and added weight.

Set it up

What you configure once, before turning it on.

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