# UTM Parameters Explained: A Clean Tracking System for SaaS

Create consistent UTM source, medium, and campaign tags with a naming convention that survives analytics reports and team handoffs.

By Revfaro · 2026-11-03

## Quick answer

UTM parameters are labels added to campaign URLs to help analytics systems recognize where visitors came from. The most useful fields are source, medium, and campaign. Consistency matters more than the number of parameters.

## Key takeaways

- Give source, medium and campaign different jobs.
- Test the final redirected link, not just the URL you typed.
- Keep personal data and internal navigation out of campaign tagging.

## Understand each UTM field

Source describes the publisher or platform, such as newsletter or linkedin. Medium describes the channel type, such as email or paid_social. Campaign names the initiative, such as spring_launch. Content distinguishes two creatives or placements, while term is usually reserved for search-keyword information when relevant.

A URL might use ?utm_source=newsletter&utm_medium=email&utm_campaign=launch_week&utm_content=footer. The values are your taxonomy, not a universal platform guarantee.

## Create and enforce a naming convention

Pick lowercase values, underscores or hyphens, and a limited vocabulary. Decide whether social should be organic_social or paid_social and forbid casual variants such as Social, socials, and sm. Maintain an owner-reviewed campaign link sheet or generator.

Use canonical names for platforms and distinguish creators or partners through content or a documented campaign key. Never put email addresses, personal data, or secret tokens in UTM values.

## Verify landing and conversion events

Click a tagged URL through a normal browser, then navigate and register. Confirm the original campaign survives the relevant journey according to your attribution policy. Redirects, cross-domain checkout, and client-side routing can lose source information.

Reconcile with paid platform reports without expecting exact equality: blockers, bot filters, time zones, and counting models differ.

## Avoid attribution inflation

Do not add UTMs to ordinary internal website navigation. Doing so can distort acquisition context or session classification, depending on the tracker. Keep a versioned naming dictionary and audit unknown values monthly.

## Build and verify one concrete campaign URL

For an illustrative launch newsletter, use a URL such as:

```text
https://example.com/pricing?utm_source=founder-letter&utm_medium=email&utm_campaign=november-launch&utm_content=main-cta
```

The source names the publication; medium describes the distribution method; campaign identifies the initiative; content distinguishes the placement. None of these values identifies the subscriber. Keep the source stable when next month's newsletter runs, and change the campaign when the initiative changes.

In Revfaro, [Link builder](/docs/campaign-links/) helps create campaign links. Test the final URL after email or social redirects, and verify the source, channel and campaign in the resulting visit. Store a plain canonical link for ordinary navigation inside your own website. `utm_content` is collected with the visit; do not assume every possible campaign field has a dedicated dashboard tab. Keep a link register containing the owner, destination, publication date and intended decision so another team member can interpret the results later.

## Related reading

- [Dark Social Attribution: Measuring Traffic from Private Shares](/blog/dark-social-attribution-measuring-traffic-from-private-shares/)
- [What Is Direct Traffic? Why It Does Not Always Mean Brand Demand](/blog/what-is-direct-traffic-why-it-does-not-always-mean-brand-demand/)


## Frequently asked questions

### Do I need all five UTM parameters?

No. Source, medium, and campaign provide a strong baseline; add content or term only when decisions require that detail.

### Are UTM parameters a complete attribution solution?

No. They label campaign links; you still need reliable session, conversion, identity, and payment events.
