MARKETING

UTM Link Linter: Block Malformed Tracking URLs Before Launch

Validates every campaign tracking link queued in an Airtable launch table against your UTM naming rules.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekday morning schedule fires
  • ActionFetch Queued links from Airtable launch tableAirtableAirtable
  • LogicLint each UTM: params, casing, allowed values, encoding
  • ActionWrite Pass/Fail verdict and reason to Airtable rowAirtableAirtable
  • OutputPost go/no-go summary to SlackSlack

What it does

Reads campaign links staged for launch in Airtable, runs each one through a deterministic UTM hygiene check (required params present, lowercase, no spaces, approved source/medium values, no double-encoded ampersands), and writes a Pass/Fail verdict plus a human-readable reason back to each row. It finishes by posting a launch-readiness summary to Slack.

When to use it

Run this as the final gate before a marketing launch when links are assembled in a shared Airtable base. It catches the silent attribution killers — uppercase mediums, `utm_campaign` typos, trailing spaces — that would otherwise scatter traffic across phantom campaign rows in your analytics.

How it works

  1. 1A scheduled trigger fires each weekday morning and pulls rows from the Airtable launch table where Status is Queued.
  2. 2For each link, the linter parses the query string and checks required UTMs, casing, allowed source/medium values, and encoding integrity.
  3. 3A branch routes clean links to a Pass path and flagged links to a Fail path with a specific reason string.
  4. 4Each verdict and reason is written back to its Airtable row.
  5. 5A Slack message summarizes total checked, passed, and a bullet list of every failure so the owner can fix before launch.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  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.