UTM Link Builder

The five parameters, precisely

UTM parameters are five query-string fields that analytics tools — GA4 and nearly everything else — read to answer one question: where did this visit come from? They are plain text appended to a URL, invented for Urchin (the U in UTM) and unchanged since. Their power and their danger are the same property: the values are free-form. Nothing validates them, so your discipline is the only thing standing between clean reports and a channel called “Email” that is really three channels.

One structural detail: GA4 assigns traffic to its default channel groups by pattern-matching source and medium. A medium of email lands in Email; cpc and other paid patterns land in the paid channels; unrecognized inventions land in Unassigned, where reports go to die. Stay inside the recognized medium vocabulary and spend your creativity on campaign names instead.

Naming conventions that keep analytics clean

Every rule here exists because someone’s quarterly report fragmented without it.

• Lowercase, always. Values are case-sensitive, so Email and email split into two rows and no one ever merges them back. The tool warns on any uppercase in the three required fields.
• Dashes, not spaces. A space encodes to %20 and makes reports read like ransom notes. spring-launch, never spring launch.
• One name per thing. Decide once that your email list is newsletter — not also email-list, mailing, and crm depending on who built the link that day.
• Campaign names follow a pattern. 2026-07-summer-sale sorts chronologically, dates itself, and tells a stranger what it was. Put the date in the name; do not mint a new campaign per send, which fragments one effort into forty rows.
• Keep a registry. A shared one-page sheet of allowed sources, mediums, and the campaign pattern beats every tool. This builder validates format — case, spaces, URL correctness — but it cannot know that marketing already calls the partner program partner, not partners.

The classic inversion deserves its own line: utm_source=email is wrong. Email is the medium — the kind of channel. The source is the specific place the link lived: newsletter, mailchimp, a list name.

Where UTMs belong — and where they must never go

Tag links that arrive from places your analytics cannot see into: email campaigns, social posts, paid placements, partner links, PDFs, podcast show notes, QR codes on print. In every one of those, the tag is the only way the visit gets attributed to the work.

Never tag internal links. Clicking a UTM-tagged banner on your own homepage restarts attribution mid-visit: analytics treats it as a new session from homepage-banner, and the visitor’s real origin — the search, the referral, the campaign you paid for — is overwritten. The corruption is silent; the numbers still look like numbers. Internal campaigns have their own mechanisms (events, content groups); UTMs are strictly for inbound. Two smaller placement rules: with Google Ads auto-tagging on, do not also hand-tag final URLs — the two systems can conflict — and never put names, emails, or anything sensitive in UTM values, because they are visible in the address bar, server logs, and every copied link.

Copied links are also why tagged URLs drift: when someone shares your tagged URL, their audience’s clicks still credit the original campaign. It inflates the tagged source slightly. There is no fix; just know it when a number looks too good.

A workflow that holds up

Build the link at send time, from the registry, not from memory — the moment someone types a source value freehand is the moment the taxonomy forks. Before the campaign ships, click the tagged link yourself once and watch it arrive in your analytics’ realtime view with the source and medium you expect; a thirty-second check that has caught more broken tracking than any audit. For print and offline, the order is fixed: build the tagged URL first, then shorten it or encode the QR code, because redirects preserve the query string. And once a month, open the Unassigned channel in GA4 — it is where every typo, every uppercase Medium, and every invented value quietly accumulates, and it is the earliest warning that the conventions are slipping.

What the presets encode

The preset chips fill source and medium with pairs that match how GA4 groups channels: google / cpc, facebook / paid, instagram / social, linkedin / social, twitter / social, newsletter / email, youtube / video, and partner / referral. Treat them as defaults, not law — swap newsletter for your actual list name if that distinction earns its keep — but change the medium only if you know which channel group the new value maps to.

Honest limitations

This tool builds a correct URL: required fields enforced, values encoded, existing non-UTM parameters preserved, old UTM parameters replaced rather than duplicated, and the fragment kept at the end — with a warning, because single-page apps that route on # can drop query strings entirely. What it cannot do is measure anything (that is your analytics), shorten links, verify the page exists, or enforce your taxonomy beyond case and spacing. The registry, the discipline, and the weekly habit of checking Unassigned traffic remain human work.