What is a UTM parameter
Guide · Glossary & Definitions · 4 min read · last verified 2026-07-29
A UTM parameter is a short tag appended to the end of a URL that tells analytics where a click came from — which campaign, which channel, which specific link — so that traffic arriving on a page can be traced back to the exact thing that sent it, rather than collapsing into a generic bucket like "referral" or "direct." The tag rides along in the URL itself; nothing needs to be installed for it to work, which is also why it is so easy to apply inconsistently across a team with no single owner.
The five tags and what each one answers
A full UTM string is built from up to five parameters, each answering a different question about the same click:
https://example.com/pricing
?utm_source=newsletter
&utm_medium=email
&utm_campaign=spring-launch
&utm_content=hero-cta
&utm_term=ai-visibility
Source answers who sent the traffic — a specific newsletter, a specific ad network, a named partner. Medium answers what kind of channel it was — email, paid social, organic social, cost-per-click. Campaign answers which initiative the click belongs to. Content differentiates two links that point to the same destination, such as two calls to action inside one email. Term is the oldest of the five, built for paid-search keywords, and the one most likely to sit unused outside search campaigns. None of the five are required by the browser or the destination page — a URL with no tags at all still works exactly the same for the person clicking it. The tag exists purely for whatever is reading the URL on the receiving end, which is also why a missing or malformed one fails silently: the link still works, and the only casualty is the row of data that should have described it.
What UTMs can see, and the edge they cannot
A UTM only registers if the link carrying it gets clicked with the tag still attached. A link copied into a text message, pasted into a private chat, or forwarded without the query string intact arrives at the destination looking like direct traffic — or like nothing traceable at all — because the channel it actually traveled through left no record a URL parameter can capture; that gap is most of what dark social describes. A related gap sits on the AI side: whether a given AI assistant preserves an outbound link's tracking parameters, rewrites the link, or strips it entirely is something to check directly for that specific product rather than assume, since it varies and can change without notice — one reason AI referral traffic shows up undercounted in a dashboard built to trust the tag.
The naming-convention problem
Dark social and AI assistants sit outside anything a tag can reach. Inconsistent tagging does not — it is the failure a convention can prevent, and it looks like five people tagging one campaign five different ways. "Newsletter," "newsletter," and "email-newsletter" look interchangeable to a person. A UTM value travels as a literal string, though, so a difference in case or spelling arrives on the other end as a different value entirely — one line in a report becomes two or three partial ones, and none of them shows the whole picture. Attribution modeling consumes whatever UTM values arrive downstream; a model built on fragmented tags inherits the fragmentation rather than repairing it; there is no modeling step that reliably reconstructs "newsletter" and "email-newsletter" as the same source after the fact.
Four rules that keep the tags usable
Four rules head off the failure modes above: lowercase only, hyphens instead of spaces or underscores, a fixed short vocabulary for medium rather than free text — email, paid-social, organic-social, cpc, referral, and little else — and one shared reference document that is the single place anyone checks before typing a new value instead of guessing at what the last campaign used. A generator or shared sheet only works if using it is faster than typing a tag from memory; where the lookup costs more time than a guess does, it gets bypassed, and each bypassed value arrives in the report as a new one.
Where the tag's job ends
Once a click lands with its tags intact, the UTM's job is finished — what happens next, whether that visitor converts or what they eventually buy, is attribution's job, not the tag's. Whether the tagging itself was applied correctly at all is a mechanical check that belongs on a pre-launch QA pass, caught before a campaign ships rather than discovered afterward in a report that no longer adds up. And UTMs describe only the clicked, tagged path a person took to a page; a citation inside an AI-generated answer is a different kind of visibility with no click and no tag involved at all. That citation is something to measure directly, not a hole in the click data to be patched over: Magrios puts a standing list of buyer questions to assistants and keeps a record of which domains the answers cite. It does not tag links, read a URL's parameters, or attribute clicks — a citation is a different observation than a visit, and it is recorded as one.