MARKETING

UTM Link Check as a GitHub PR Gate

On every pull request touching marketing-site content, scans changed files for campaign links and fails the check if any UTM params violate the taxonomy, blocking the merge.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub PR opened or updatedGitHubGitHub
  • ActionFetch changed files and extract UTM linksGitHubGitHub
  • LogicLint each link against UTM taxonomy
  • LogicDecide pass/fail on any violation
  • OutputPost status check + PR comment with offending linesGitHubGitHub

What it does

Hooks into pull requests on your marketing site or content repo. When a PR changes HTML, MDX, or config files, the flow extracts every URL carrying UTM params from the diff, lints them against your taxonomy, and reports back as a GitHub status check. Malformed tags fail the check with inline file-and-line detail, so bad tracking links never reach production.

When to use it

Use it when your campaign links live in code — landing pages, email templates in the repo, or marketing config — and you want UTM hygiene enforced in the same review gate as everything else engineers ship.

How it works

  1. 1A GitHub pull_request webhook trigger fires on opened and synchronized PRs.
  2. 2The flow fetches the PR's changed files and extracts URLs containing UTM params.
  3. 3A lint step validates each link's params against the required keys and allowed values.
  4. 4A branch decides pass or fail based on whether any violations exist.
  5. 5The flow posts a GitHub commit status (success or failure) plus a PR comment listing each bad link with its file and line, blocking merge until fixed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  3. 3
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  4. 4
    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.