UTM Builder & Governance Registry: Kill the 'Facebook / facebook / FB' Mess

The problem this kills

Every marketer on the team builds tracking links their own way. One types Facebook, another types facebook, a third writes FB. Someone fat-fingers emial instead of email. A campaign is summer_sale in one link and Summer-Sale-2026 in the next. None of it is wrong, exactly — but when it lands in your analytics, those are four different sources and three different campaigns, and your "top channels" report is quietly lying to you.

So you spend the first hour of every reporting cycle cleaning up the same free-text chaos, mapping FB and Facebook back together by hand, and praying nobody invented a new spelling this month. You don't need to keep doing this, and you don't need to be a developer to fix it.

What you'll build

A simple internal web tool that makes a correctly-tagged link the only easy way to build one. A marketer pastes the destination URL, picks a source, medium, and campaign from your approved lists (or types one), and the tool validates every parameter against your allowed values — forcing lowercase, catching typos, and rejecting free-text junk. If everything matches your rules, it builds a clean tagged link instantly and saves it to a shared registry. If something is non-standard — a source nobody's seen before, a campaign name that breaks your convention — the link is held and an ops admin reviews it: approve the new value (it joins the allowed list) or correct it, and only then does the link become "official" in the registry. The whole registry is searchable and exports to CSV in one click.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — what your current link-building process looks like, where your analytics live, exactly how you name sources, mediums, and campaigns today, your real allowed-value lists, your typical and peak link volumes, who's allowed to approve a new value, and the messy edge cases (auto-tagged ad platforms, agency-built links, paid vs organic conventions) — and then it tailors the validation rules, the data model, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the builder form, the allowed-value validation, the duplicate warning, the admin approval queue, the registry with search, and the CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today, with the registry as your single source of truth and a clean CSV out, no integration required.

The governance it includes (this is the point)

This is real marketing-ops tooling, so it ships with the controls a team needs to trust the data: login so only your team can build links, row-level security so you only ever see your own organization's registry, a complete audit trail of who built, approved, corrected, or rejected which links and when, a hard human-approval gate so any non-standard value is held for an ops admin before it's saved as official, and duplicate guards keyed on the full tagged URL so the same link can't be created twice for the same destination and campaign. Lowercase and allowed-value enforcement are baked into the builder itself, so bad data can't get in by accident.

Who it's for

Marketing-ops leads, demand-gen marketers, and analytics owners who keep finding the same channel spelled three different ways and are tired of cleaning up UTM chaos before every report. If you can describe how your team is supposed to name things, you can build the tool that enforces it.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your first governed tracking link drop into a clean registry the same afternoon.