A short link with UTM tags behind it is the standard unit of campaign tracking: clean enough to put in a tweet or on a poster, and tagged so the visit shows up under the right campaign in your analytics. The arrangement only works if the shortener delivers the tags intact, and not every one does.
Choosing short links with UTM parameter support means knowing what to test for. This guide covers how the two pieces fit together, four checks that separate shorteners that preserve your tags from ones that quietly drop them, and a build-and-test routine that keeps campaign tracking reliable.
How a short link and UTM tags work together
A campaign link has two layers.
- The destination URL carries the UTM parameters:
https://example.com/offer?utm_source=newsletter&utm_medium=email&utm_campaign=oct-launch. Your web analytics reads them on arrival and files the visit under the campaign. - The short link sits in front:
go.example.com/oct-launch-email. It records the click, then redirects to the destination with the query string attached.
Each layer measures something the other cannot. The short link counts clicks from channels your site never sees, such as print, podcasts and chat, and counts them before any script loads. The UTM tags connect the visit to the rest of the campaign inside your analytics, where conversions are measured. Build the destination with the tags first, then shorten it. The UTM playbook covers naming in depth.
Four checks before you choose a shortener
| Check | How to run it | What failure looks like | | --- | --- | --- | | Parameters survive the redirect | Create a tagged link, follow it with a redirect checker | Final URL missing or rewriting your tags | | No redirect chain | Count the hops | Two or more redirects before the destination | | Destinations are editable | Change a tag on a live link | A new slug instead of an edit | | Click fields and bot filtering | Click from a phone, check the report | A count with no referrer, device or bot flag |
Parameters survive. The shortener must redirect to exactly the URL you gave it. Some platforms normalise URLs, append their own tracking parameters, or drop ones they do not recognise. Run one tagged link through the redirect checker and read the final URL.
No chains. A shortener that redirects through an interstitial or a second domain adds latency and another place for parameters to fall off. One hop, straight to the destination.
Editable destinations. A campaign changes mid-flight. If the only way to change the UTM tags behind a link is to make a new link, every copy already shared is now wrong and your report splits in two. LinkPilot links keep their slug while the destination, tags included, is edited in the dashboard.
Click fields and bots. The short link's own report should show referrer, device, country and a bot flag per click. Email scanners click every link within seconds of delivery; without a bot flag the report cannot be read.
Beyond the four: a custom domain so the short link carries your brand, tags or collections to group campaign links, an API to create links in bulk, and team roles so one person's edit cannot break another's campaign. The custom domain shortener guide covers the rest of the checklist.
Build the links
- Agree the convention first. Lowercase, hyphens, the same
campaign token in
utm_campaign, in the link's tag and in the slug. Write it where the team can see it. - Build the destination in the UTM builder. It produces the URL without typos or stray spaces, which are the usual cause of a campaign appearing twice in analytics.
- Shorten it with a slug that names campaign, channel and placement, on your branded domain, and tag it with the campaign and the channel.
- One link per placement you will compare. Two placements sharing a link is a question you can never answer.
- Test: open from a phone, confirm the redirect lands with every tag intact, confirm the click appears in the report with the right device. Run the redirect checker once more.
Keep UTM data consistent
Most UTM problems are human. The fixes are organisational.
- One builder, one convention. Nobody types a UTM parameter by hand.
- A fixed vocabulary for source and medium:
newsletter,linkedin,partner;email,social,paid,qr. Capitalised variants split your reports. - Optional parameters have rules.
utm_contentfor the placement,utm_termonly for paid search. Decide once. - Cross-team coordination. Marketing, sales and customer success sharing one convention means one analytics view, not three.
Measure and reconcile
Read the short link report for reach and channel split, with bots
excluded and unique clicks first. Read web analytics for what
happened after arrival, grouped by utm_campaign. Compare unique
clicks to sessions and expect the site to show 10 to 30 percent fewer.
A larger gap means a slow destination, a redirect chain or stripped
parameters, which the redirect checker will find. The campaign
reports guide
has the monthly routine.
Mistakes to avoid
- Shortening before tagging, which leaves the tags out entirely.
- Changing tags by making a new link, which splits the history and strands the shared copies.
- Personal data in UTM values. A customer's email in
utm_contentends up in logs, browser history and shared reports. Use opaque identifiers or none. Why URLs leak sensitive information explains the consequences. - Not retesting after a destination change. A landing page that moved behind a redirect of its own can start dropping parameters without anyone changing the short link.
- Trusting "UTM support" on a feature list. Run the four checks. They take ten minutes and settle it.
Short links with UTM parameter support are the normal case on a good shortener. The point of choosing carefully is to make sure yours is one of them before the campaign, not after the report.