How to use this tool
- Enter the destination HTTP(S) URL.
- Fill in source, medium and campaign; term and content are optional.
- Build and inspect the parameter table before copying the link.
How the operation works
The builder sets UTM values through the URL API, which encodes values and retains unrelated parameters. A supplied field replaces an existing field of the same name. Empty optional fields leave existing values unchanged. Source and campaign spelling remain as entered so you can follow your own naming convention.
What each UTM field means
utm_source — the platform or publisher sending traffic (newsletter, twitter, partner-blog). utm_medium — the marketing channel (email, cpc, social, affiliate). utm_campaign — the promotion or initiative (spring_sale_2026). utm_term — optional paid keyword or audience segment. utm_content — optional creative variant (hero_banner, footer_link).
Source and campaign are required for useful reports. Term and content are optional; empty optional fields leave any existing values unchanged rather than writing empty strings.
Naming rules that keep reports readable
Agree on case before creating many links: Email and email become different values in downstream reports. Prefer lowercase snake_case or kebab-case. Spell the medium from a fixed list so totals group correctly. Do not put personally identifying information in campaign fields—analytics tools receive them as-is.
A supplied field replaces an existing field of the same name. Unrelated query parameters and the #fragment are preserved. Spelling of source and campaign remains exactly as typed so your convention is not “helpfully” rewritten.
Example builds
Base: https://example.com/pricing?lang=en Source: newsletter · Medium: email · Campaign: autumn_launch Result: https://example.com/pricing?lang=en&utm_source=newsletter&utm_medium=email&utm_campaign=autumn_launch
The existing lang=en parameter stays. A second build with the same source/medium but a different campaign replaces only utm_campaign; other UTM fields you filled remain. Inspect the parameter table before copying the link.
What UTM tags do and do not do
UTM parameters are labels for analytics systems that choose to read them. They do not guarantee that a visit is collected, attributed or attributed to the campaign you intended. They are not encryption, not shorteners and not a substitute for server-side campaign configuration.
This builder does not use a remote shortener or tracking service. The resulting URL is a normal link you can paste anywhere. For cleaning old campaign fields from a shared link, use URL Cleaner.
Building a consistent set
Create a small naming sheet (source, medium, campaign list) before a campaign goes live. Build each link here, paste the parameter table into your campaign doc, and keep the base URL unchanged so A/B tests differ only in the intended fields. Re-check a sample link in the destination’s own analytics preview if available.
A worked example
https://example.com/?lang=en plus newsletter / email / autumn
https://example.com/?lang=en&utm_source=newsletter&utm_medium=email&utm_campaign=autumn
“Email” and “email” can become different values in downstream reports. Agree on naming rules before creating many campaign links. UTM tags do not guarantee analytics collection or attribution.
Required fields and what the builder preserves
Source, medium and campaign are required; term and content are optional. The builder edits the URL through the browser URL API, so unrelated query parameters keep their place and the fragment is retained. Supplying a field that already exists replaces that UTM value instead of adding a second copy. Values are percent-encoded where needed.
Optional fields left empty do not clear existing values. If a link already carries a campaign, review every field before rebuilding it. The result is a readable URL, not a shortened one, and the parameters remain visible to anyone who receives the link.
Naming discipline matters more than the tool
Analytics systems treat Email and email as different values. Agree on lowercase source and medium names, a consistent campaign pattern and a limited vocabulary before creating many links. Inconsistent names fragment reports even when every URL is technically valid.
Do not put personal data, email addresses or secrets in UTM fields; they appear in shared links, logs and referrer data. When cleaning an existing link, use URL Tracking Parameter Cleaner. The tracking guide covers naming and encoding together.
Processing and privacy
UTM Builder assembles the campaign link in page memory; the base URL and campaign values are not uploaded. Input stays in browser memory until you reset or leave the page. Copy and download run only when you choose them. No tool input is sent to a processing service. Website pages and scripts still make ordinary hosting requests; the privacy policy separates those from tool processing.
Frequently asked questions
Will this shorten a link?
No. It builds readable campaign parameters and does not use a remote shortener or tracking service.
What if the URL already has UTM fields?
A supplied field replaces the existing field of the same name. Empty optional fields leave existing values unchanged.
Do UTM tags guarantee analytics collection?
No. They are labels. Collection and attribution depend on the analytics configuration of the destination.
Can I put personal data in these fields?
Avoid it. Campaign fields are often exported into shared reports. Use campaign names, not customer identifiers.
How do I remove old campaign tags later?
Use URL Cleaner and select the UTM parameter names you want stripped while keeping content parameters.
Will the builder remove unrelated query parameters?
No. Non-UTM parameters and the fragment are preserved; only same-name UTM fields are replaced.
Does it create a short link?
No. It returns the full campaign URL with visible parameters and does not contact a shortener.
How this tool was checked
UTM Builder was checked with existing query parameters, a fragment, missing optional fields, values needing percent-encoding and replacement of existing UTM fields. See the testing method or report a failure.