UTM parameters can make campaign reporting far more useful, but they do not need to turn public URLs into long, fragile strings. This guide provides a reusable checklist for building clean campaign redirects, preserving attribution through each hop, avoiding accidental SEO problems and validating links before they are published.
Overview
UTM link tracking works by adding query parameters to a destination URL. Analytics platforms can then identify details such as the campaign source, medium and name. For example:
https://www.example.co.uk/sale?utm_source=newsletter&utm_medium=email&utm_campaign=spring_sale
This is useful when you control the link placement, but it may be less suitable for printed material, social posts, QR codes, partner promotions or adverts where a short, memorable URL is preferable. A campaign redirect adds a separate public URL, such as example.co.uk/go/spring, which forwards visitors to the full tracking URL.
A redirect does not replace sound analytics configuration. It is simply a routing layer. The final destination must contain the parameters your reporting system expects, and the redirect must pass them through reliably. Use a server-side redirect or an appropriate platform rule where possible, rather than relying on a script that loads after the page.
| Approach | Best suited to | SEO and measurement considerations |
|---|---|---|
| Direct tracked link | Email, owned content and digital adverts | Simple to implement; the full query string is visible and must be named consistently. |
| Short link | Print, presentations, social profiles and QR codes | Convenient, but confirm that the short URL resolves to the intended tracked destination. |
| Tracking redirect | Campaign links that need a stable public URL | Keep the redirect chain to one hop and use the appropriate status for the intended permanence. |
| Canonical URL | Controlling the preferred version of similar pages | A canonical is not a tracking mechanism and should not be used as a substitute for a redirect. |
For a permanent campaign alias or retired landing page, review the difference between a 301 and 302 redirect before implementation. A temporary promotion may need different handling from a stable branded route.
Checklist by scenario
1. Direct links in email or digital content
- Choose the final landing page before adding parameters.
- Use lowercase values unless your analytics convention deliberately distinguishes case.
- Check that the page is accessible over the intended HTTPS URL.
- Build the UTM string using your agreed naming template.
- Test the link in a private browser window and confirm that the landing page loads.
- Verify that analytics records the expected source, medium and campaign values.
Direct links are usually the simplest option when URL length is not a concern. Avoid adding tracking parameters to internal navigation unless there is a specific reporting reason; doing so can create fragmented page URLs and make attribution harder to interpret.
2. Short links and campaign redirects
- Create a descriptive public path, such as
/go/member-offer, rather than an unexplained code. - Set the destination to the complete URL, including the UTM parameters.
- Use one redirect hop from the public path to the final landing page where practical.
- Preserve the destination query string and check whether the redirect service replaces or appends parameters.
- Confirm that the short link works on mobile and desktop if both are part of the campaign.
- Record the owner, purpose, destination, launch date and review date in a link register.
For a QR code, point the code at the stable short link rather than embedding a changeable final URL. This gives you a route that can be updated when the campaign destination changes, provided the short link remains under appropriate control.
3. Paid campaigns and partner links
- Separate the traffic source from the advertising platform or partner name in your naming convention.
- Define whether
utm_mediumdescribes the channel, such asemail,paid_socialorpartner. - Use a consistent value for the campaign across adverts, landing pages and reporting views.
- Check whether the advertising platform adds its own parameters or redirects.
- Confirm that auto-tagging, if enabled in a platform, does not conflict with your manual tagging approach.
- Test the final click path after any tracking template or advert substitution is applied.
4. Site migrations or changed landing pages
Do not treat campaign redirects as a replacement for a full redirect map. If a landing page moves, update the campaign destination and review existing links. For broader changes, use the redirect mapping and pre-launch checklist to document old and new URLs, status codes and test results.
A redirect that points to another redirect can work, but unnecessary hops add complexity and latency. Review redirect performance and crawl paths using the guidance on measuring redirect performance.
Reusable UTM naming template
Agree the convention before a campaign starts. A practical template is:
utm_source={origin}&utm_medium={channel}&utm_campaign={campaign_name}&utm_content={variant}
- utm_source: the platform, publisher or origin, such as
newsletter,linkedinorpartner_acme. - utm_medium: the channel, such as
email,organic_social,paid_socialorprint. - utm_campaign: the shared campaign identifier, such as
spring_sale_2026. - utm_content: the creative, placement or variation, such as
hero_ctaorversion_b.
Example:
https://www.example.co.uk/offers?utm_source=customer_email&utm_medium=email&utm_campaign=spring_sale_2026&utm_content=hero_cta
Keep values readable and avoid spaces, inconsistent punctuation and unexplained abbreviations. If several teams create links, maintain a shared glossary and decide who can introduce new source or medium values. The exact parameters and reporting behaviour depend on the analytics platform, so check its current documentation before changing a live convention.
What to double-check
Query-string preservation
Follow the link step by step and inspect the address at the final page. Confirm that all required parameters remain present. A redirect rule, hosting platform, campaign tool or application framework may remove, replace or duplicate query strings.
Destination accuracy
Check the final page, not just the first response. Test the correct language, product, offer, device experience and sign-in state where relevant. A successful HTTP response does not prove that the visitor has reached the right campaign page.
Indexing and canonicalisation
Tracking parameters can create multiple URL variants for the same content. Keep the preferred page URL clear, use internal links consistently and ensure the page’s canonical setup reflects the intended primary URL. A canonical tag suggests a preferred version; it does not forward visitors. Avoid using a campaign redirect to conceal an unrelated destination or to create an open redirect. See the open redirect security checklist if destination input can be controlled by users.
Rule order and loops
Check that the campaign rule is evaluated before broad HTTP-to-HTTPS, www-to-non-www or domain-forwarding rules where your platform requires a particular order. A conflict can create a redirect loop or an unexpected destination. The redirect rule precedence guide covers common ways to diagnose this.
Privacy and data handling
Do not place names, email addresses, telephone numbers or other unnecessary personal information in UTM values. Treat campaign parameters as potentially visible in browser history, server logs, analytics interfaces and copied URLs. Review your organisation’s privacy and data-retention requirements, especially when links are shared across partners or embedded in printed material.
Common mistakes
- Changing capitalisation:
Email,emailandEMAILmay be reported as different values. - Using spaces or special characters: These can be encoded inconsistently and make filtering difficult.
- Tagging only some campaign links: Incomplete coverage produces misleading comparisons.
- Overwriting existing parameters: A redirect that drops required parameters can break attribution.
- Adding multiple redirects: Chains make testing and diagnosis harder. Point each public campaign URL directly to the final tracked destination where possible.
- Using a 301 for a short experiment without a plan: Permanent redirects may be cached by browsers and intermediary systems. Choose the status code deliberately and consider caching behaviour.
- Assuming a short link is automatically safe: Test the destination, restrict editing access and review old links periodically.
- Counting redirect hits as landing-page sessions: Reporting should be based on the analytics event or session recorded at the destination, not merely on a redirect request.
If a link behaves differently in different environments, run a redirect checker, inspect response headers and compare the route from HTTP to HTTPS and from www to non-www. For wider troubleshooting, use the redirect loop guide.
When to revisit
Use this checklist before every major campaign, seasonal planning cycle and printed or QR-led promotion. Revisit it sooner when your analytics property, consent approach, advertising platforms, redirect provider, CMS or hosting stack changes.
At each review:
- Export or inspect the current source, medium and campaign values used in reporting.
- Remove obsolete naming variations from new campaign plans, while preserving historical data labels.
- Test a sample of existing short links and campaign redirects from a mobile connection and a normal desktop browser.
- Confirm that final destinations, query strings, canonical URLs and consent-dependent analytics still behave as intended.
- Check for chains, loops, broken landing pages and unexpected parameter duplication.
- Update the link register and document any changed rule, owner or destination.
A small pre-launch test prevents many attribution gaps. Keep the naming template, redirect inventory and test results together so the next campaign can be checked quickly rather than rebuilt from memory.