MARKETING

Nightly CWV trend audit on production landing routes with baseline drift report

Runs every night against the live marketing routes, stores LCP/CLS/INP to a warehouse for trending.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule
  • ActionAudit production landing routesBrowserbase
  • ActionAppend metrics to BigQueryGoogle BigQueryBigQuery
  • LogicCompare to trailing 7-day baseline
  • OutputPost drift digest to SlackSlack

What it does

Catches the slow-creep regressions that no single deploy causes — a CMS image swap, a new marketing tag, or growing third-party weight. It audits production landing routes nightly, persists the metrics for long-term trends, and surfaces routes drifting past budget.

When to use it

Use it as a standing health check independent of the deploy gate. It's the right fit when content editors and tag managers change the live site outside the code path, so deploy-time gates alone miss the regression.

How it works

  1. 1A nightly schedule triggers the run.
  2. 2The flow audits each production landing route and collects LCP, CLS, and INP.
  3. 3It writes the results as a dated row into BigQuery for trend history.
  4. 4A logic step compares tonight's numbers to the trailing 7-day baseline and flags drift beyond the budget.
  5. 5It posts a Slack digest listing healthy routes, drifting routes, and week-over-week change.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BrowserbaseHeadless browsers, sessions, replays.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  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.