UTM tracking helps you tell a newsletter visit from a social post or partner placement. The useful part is the campaign label, not the identity of the person who clicked.
This guide shows small teams how to name links, keep personal details out and test attribution. If you're still choosing a tool, start with our European web analytics buyer's guide and web analytics directory.
UTM parameters are labels added to a destination URL so a compatible analytics tool can identify a campaign. Start with three fields and add detail only when it supports a real decision.
| Parameter | Question it answers | Example |
|---|---|---|
| utm_source | Where did you share the link? | newsletter |
| utm_medium | What kind of channel is it? | |
| utm_campaign | Which initiative does it belong to? | product-demo |
| utm_content | Which placement or version? | footer-link |
For example, a fictional SaaS company could share this link in its newsletter:
https://example.com/demo?utm_source=newsletter&utm_medium=email&utm_campaign=product-demo&utm_content=footer-link
If the destination already has a query string, append new parameters with an ampersand rather than a second question mark. Use a URL builder to avoid broken syntax, then check the finished link.
Choose lowercase names and a consistent separator, such as hyphens. Plausible's campaign documentation notes that UTM tags are case-sensitive, even though its Sources view consolidates some naming variants. Don't rely on that consolidation to clean up your campaign reports.
Keep a shared sheet with the destination, source, medium, campaign, content label and person responsible. Agree on names before several people promote the same launch. A newsletter and a LinkedIn post can share a campaign name while keeping different source and medium values.
Avoid putting email addresses, customer names, account IDs or private details into UTM values. Use a label such as partner-webinar, not an attendee's email address. Keep campaign names broad enough that they don't reveal sensitive information about the audience.
Plausible's data policy says it discards URL query parameters except supported campaign and referral parameters. That exception matters: a privacy-focused analytics tool can still receive the campaign text you choose to send.
Review the whole URL, not only the UTM fields. A clean campaign name doesn't fix a destination path that contains a customer's name or an existing query string with private information. Use a public landing page rather than a personalised account or document link for campaign measurement.
Tag external placements you control, such as newsletters, partner posts and social profiles. Leave ordinary links between your own pages untagged. Plausible's UTM guide advises against internal UTMs because they can interfere with acquisition attribution. Measure an internal button separately if you need to assess its use.
For ideas about external channels worth testing, see our guide to where to promote your European SaaS. Give each placement a consistent label rather than creating a different campaign for every click.
A link can open the right page while losing its campaign labels along the way. Test the actual placement, including any shortener or redirect, before a launch.
Use this short check:
Analyse website traffic with a simple, lightweight tool. Made and hosted in the EU, it's GDPR-compliant by design and requires no cookie banners.

Plausible supports the five standard UTM fields and lets you filter campaign traffic by configured goals. It's one option for teams that want to compare campaign visits and conversions without building a person-level tracking system.
Plausible documents a testing trap: campaign attribution applies to the first pageview of a new session. Clicking another tagged link during an active session doesn't replace that attribution. Its documentation defines a session as remaining active until 30 minutes after the last pageview.
For that reason, it recommends testing with a device and network combination that hasn't visited recently. If you can't see your test, check session timing and redirects before renaming the campaign or assuming the script is broken. For another analytics product, check its own attribution rules rather than applying Plausible's behaviour to it.
Start with the decision you want to make: which newsletter placement earns demo requests, or which partner sends relevant visitors? Compare campaigns over the same reporting window and use a goal that reflects that decision. Visits alone don't establish business value.
Plausible describes its conversion attribution as last-click: the source of the visit leading to the conversion receives credit. It doesn't reconstruct a person's full journey across devices or days. Don't interpret a campaign report as proof that earlier content had no influence.
If your privacy review calls for excluding campaign parameters, Plausible documents a way to strip them before sending analytics requests. The trade-off is less campaign detail; referrer-based reporting remains, with missing referrers falling under Direct / None. Check the instructions against your installed version before changing the script.
This is measurement guidance, not legal advice. Campaign labels don't settle consent, notice or other privacy requirements. Review your complete setup and applicable rules rather than treating a cookieless tool as blanket approval.
Start your next campaign with a shared naming sheet, one public destination and a tested link. Keep the labels about the promotion, not the people receiving it.
Review results against one useful outcome, then reuse the naming system. Consistent campaign data is easier to act on than a dashboard full of near-identical labels that nobody can explain.