UTM tags that survive being shared

UTM parameters are the five extra words you bolt onto the end of a URL so the analytics at the far end can say where a visitor came from. They are old, ugly, and still the most widely understood way to answer "which campaign brought this person here?" — because your destination reads them, not the platform that carried the link.

Three of them do the actual work. Source is where the visit came from as a place: facebook, newsletter, partner-site. Medium is how it travelled: social, email, cpc, qr. Campaign is which push it belongs to: spring-sale, launch-week. Term and content are optional and only earn their place when you are splitting paid keywords or A/B testing two versions of the same ad, and most people should leave them empty rather than filling them with something meaningless.

The rule that keeps a report readable is consistency, and it is broken more often than anything else here. UTM values are case-sensitive and treated as opaque strings, so Facebook and facebook are two rows in your report, as are newsletter and news-letter, and email and e-mail. Nobody notices until three months of data have accumulated across six spellings and the totals no longer mean anything. Pick one casing — lowercase — write your conventions down somewhere the whole team can see, and treat that document as the source of truth rather than each person's memory.

Now the part specific to short links, and the reason the builder on this site works the way it does. The tags belong on the destination, behind the redirect — not on the short link you publish. When you shorten a tagged URL, the tags travel inside the stored destination and get applied at the moment the redirect fires. Your visitor sees eighteen clean characters; your analytics still receives every parameter.

That matters because a long tagged URL is precisely the shape that breaks in the wild. Chat apps wrap it across two lines and cut the tappable region at the break. Some platforms truncate the visible text. Others strip query strings when they rewrite links for their own tracking. A short link is a single opaque token with nothing to wrap and nothing worth stripping, and the tags are not exposed to any of that.

It is also worth being clear about what UTM tags do not do, since this is where people over-invest. They tell your destination's analytics about the visit. They do nothing whatsoever for the short link's own click count — that number is recorded before the redirect and knows nothing about parameters. So if your plan is to compare three channels by giving one short link three different tag sets, you will get three identical short links and one undifferentiated click count.

The technique that actually works is to combine the two. One short link per channel gives you clean per-channel counts on this side, working even where referrer data does not exist — chat apps, QR scans and typed addresses all arrive with no referrer at all. Tags on each destination give the far end its attribution. Neither substitutes for the other, and together they cost about a minute to set up.

A few habits keep the whole thing honest. Never tag an internal link on your own site: the tag restarts the session in most analytics tools and you end up attributing your own visitors to your own newsletter. Never tag a link you did not create the destination for — tagging somebody else's URL pollutes their reporting, not yours. And do not change a link's tags mid-campaign, because the history then mixes two schemes and stops being comparable with itself.

Finally, remember that a tagged URL is public. Anybody can read q3-promo-v2-final off the address bar, which leaks your internal planning vocabulary to anyone paying attention. Name campaigns the way you would if a customer might read them out loud, because sometimes one does.