Newsletter campaign tracking with UTM
Email clients usually send no web referrer, so newsletter clicks need UTM tags to be attributed at all. This page gives a recommended utm_medium=email structure with per-send utm_campaign naming, and the hard privacy rule that subscriber identifiers must never appear in a UTM.
Recommended structure
Standardise email as its own medium and give every send a unique campaign name so issues stay separable:
- utm_source=<your-newsletter-name> (e.g. weekly-digest)
- utm_medium=email
- utm_campaign=<per-send label> (e.g. 2026-06-issue)
- utm_content=<optional, to compare links within one send>
Worked example
For a link in the June issue of your weekly digest:
https://example.com/post?utm_source=weekly-digest&utm_medium=email&utm_campaign=2026-06-issue
To compare the header link against the footer link in the same send, add utm_content=header versus utm_content=footer.
Keep subscriber data out
Email platforms make it easy to template per-recipient values, which tempts people to encode a subscriber ID for finer attribution. Do not. Those URLs end up in logs, shared screenshots, and browser history. Use generic, send-level labels and rely on your ESP for individual engagement data.
How it appears in analytics and logs
A visit with utm_medium=email tells you it came from a newsletter rather than the web. A distinct utm_campaign per send lets you compare issues without them collapsing into one row.
Diagnostic use case
Tag every newsletter link so email-driven visits are attributed to the right send, with a per-send utm_campaign that keeps issues separable in reports.
What WebmasterID can help detect
WebmasterID reads utm_medium=email at ingest and attributes the visit to the matching newsletter campaign, so email shows up as a real source even though the email client sends no referrer.
Common mistakes
- Reusing one utm_campaign for every send so issues cannot be compared.
- Templating a subscriber email or ID into a UTM parameter.
- Using utm_medium=newsletter in one tool and email in another, splitting the channel.
Privacy and accuracy notes
Never merge a subscriber's email, name, or account ID into UTM values, even though your ESP can template per-recipient fields. UTM values are logged and shareable; keep them to generic campaign and content labels.
Related pages
- UTM naming conventions that survive reporting
Most UTM data problems are naming problems. Because tools treat utm_source=Reddit and reddit as different values, inconsistent casing and spelling fragment one campaign across many rows. This page gives a convention — lowercase, hyphenated, documented allow-list — that keeps reports clean.
- UTM parameters explained: the five tags and how to use them
UTM parameters are query-string tags you add to a link so analytics can attribute the visit to a campaign even when the referrer is missing. This page explains the five tags, a consistent naming convention, and the hard rule that UTM values are public — so they must never contain personal data or secrets.
- Campaign links (docs)
Build UTM-tagged newsletter links without leaking PII.
Sources and verification notes
- MDN — Referrer-PolicyEmail clients commonly send no referrer, so UTM is required.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.