Build campaign tracking URLs that your analytics will actually group correctly. Enter the destination and the campaign parameters and you get a properly encoded link, with the three required fields flagged if any are missing. Values are lowercased and hyphenated by default, which matters more than it sounds: analytics platforms treat UTM values as case-sensitive strings, so 'Newsletter' and 'newsletter' split into two rows in your report and the campaign looks half as effective as it was. Existing query parameters on the destination are preserved, and any UTM parameters already on the URL are replaced rather than duplicated, so re-tagging a link that was tagged before does the right thing. It runs entirely in your browser — no account, no link shortener, and no record of where you are sending traffic.
| Parameter | Required | Means | Example |
|---|---|---|---|
| utm_source | Yes | Where the traffic came from | newsletter, google, facebook |
| utm_medium | Yes | The type of channel | email, cpc, social, referral |
| utm_campaign | Yes | The promotion it belongs to | spring-launch, black-friday |
| utm_term | No | Paid search keyword | running-shoes |
| utm_content | No | Tells two similar links apart | header-cta, footer-cta |
| utm_id | No | Your own campaign identifier | 2026-q1-004 |
utm_source, utm_medium and utm_campaign. Source is where the traffic comes from, medium is the channel type, campaign is the promotion it belongs to. utm_term and utm_content are optional, and utm_id is for your own campaign identifier if you use one.
Because analytics platforms compare these values as exact strings. Tag one link 'Email' and another 'email' and you get two rows in the report for the same channel, splitting the numbers. Lowercasing everything is the simplest way to never hit that, which is why it is on by default.
Medium is the kind of channel — email, cpc, social, referral. Source is the specific origin within it — the name of the newsletter, google, facebook. A useful test: medium should be one of a small fixed set you reuse everywhere, source can be many.
No. Existing query parameters are preserved exactly. If the URL already has UTM parameters they are replaced rather than added again, because a URL with two utm_source values is ambiguous and different platforms pick different ones.
Generally no. Tagging a link between two pages on your own site restarts the session attribution in most analytics tools, so the original source of that visit is lost. UTM parameters are for traffic arriving from outside.
No. The URL is built in your browser. Destinations and campaign names — which can reveal unannounced launches — are never sent to a server, logged, or stored.
The base URL is parsed with the browser's own URL constructor, which handles existing query strings, fragments, ports and internationalised domains correctly rather than by string concatenation. A bare domain with no scheme is assumed to be https rather than rejected, since that is what people paste; anything that is not http or https is refused, which also rules out javascript: and data: URLs. Each UTM value is trimmed, optionally lowercased, and has internal whitespace collapsed to hyphens — analytics platforms treat these values as case-sensitive strings, so Newsletter and newsletter become two separate rows in a report, and a space, while legal once encoded, tends to fragment reports in practice. Values are written with searchParams.set rather than appended, so an existing utm_source on the URL is replaced instead of duplicated; a URL carrying the same parameter twice is ambiguous and platforms disagree on which wins. Clearing a field removes its parameter entirely. Encoding is handled by URLSearchParams, so reserved characters are escaped correctly.