MARKETING

Weekly UTM Drift Tracker with Trend Snapshot

Every week, measures what share of tracked links conform to your UTM taxonomy, stores the score in a Postgres history table.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Monday 08:00)
  • ActionRead last 7 days of links + prior scorePostgreSQLPostgres
  • LogicCompute conformance % and worst dimension
  • ActionAppend new score to trend tablePostgreSQLPostgres
  • LogicFormat week-over-week drift
  • OutputPost trend snapshot to SlackSlack

What it does

Turns UTM hygiene into a trackable KPI. Once a week it pulls recent link data, computes a conformance percentage (clean links over total), appends that score to a Postgres trend table, and compares it to the prior week. The Slack summary shows the current conformance rate, the direction of drift, and which source or medium degraded most.

When to use it

Use it when one-off audits aren't moving the needle and you need a recurring scorecard to hold campaign owners accountable. The stored history lets you chart hygiene over a quarter and prove whether enforcement is working.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2A Postgres query reads the last seven days of link rows and last week's stored score.
  3. 3A scoring step computes the conformance percentage and isolates the largest declining dimension.
  4. 4A step writes the new score and timestamp back to the trend table.
  5. 5A logic step formats the week-over-week delta and direction.
  6. 6The trend snapshot is posted to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.