Skip to content
Lizely

UTM Link Builder

Build clean campaign URLs with the five traditional UTM parameters, entirely in your browser.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Paste the complete http or https destination URL.
  2. 2.Enter campaign source, medium, and name; add term or content only when needed.
  3. 3.Build the URL, review the preserved parameters and fragment, then copy the result.

About UTM Link Builder

A UTM link builder helps marketers, publishers, and small teams create a campaign URL without hand-editing a long query string. Paste a complete destination URL, enter a campaign source, medium, and name, then generate a link with the traditional utm_source, utm_medium, and utm_campaign fields. You can also add utm_term and utm_content when they are useful for your reporting convention. The finished URL is shown immediately and can be copied for an ad, newsletter, social post, partner placement, QR code, or other campaign destination. Everything happens in the browser. The tool does not send the destination URL or your campaign labels to a server.

The builder is intentionally narrow. It manages only the five traditional UTM keys: utm_source, utm_medium, utm_campaign, utm_term, and utm_content. Campaign source, medium, and name are required so a generated link is not missing the core manual-campaign fields described in Google Analytics guidance. Term and content are optional. When an optional field is blank, the tool leaves that parameter out instead of adding an empty value. This makes a short campaign link easier to inspect and reduces accidental variations in reporting labels.

You can safely start from a URL that already has parameters. For example, a landing page may include ref=homepage, gclid, language settings, or another application-specific value. The builder keeps those unrelated query parameters, the URL path, and any #fragment. It removes any old copies of only the five UTM keys it owns, then adds the values from the form. That prevents duplicate utm_source values and lets you refresh a link without rebuilding the destination address by hand. The output uses ordinary URL query encoding, so spaces in a campaign term become a valid URL representation.

Use a full http or https URL, such as https://example.com/pricing. Relative paths, email links, file-transfer links, and other non-web protocols are rejected because this tool is scoped to web campaign destinations. The result is a constructed URL, not a test of your analytics installation. It does not check whether a Google Analytics property exists, whether auto-tagging is active, whether a redirect keeps the parameters, whether a destination page loads, or whether future traffic will be attributed to a particular report. Test an important campaign link in your own browser and reporting setup before publishing it.

Keep campaign values understandable and consistent. A team might use google as a source, cpc as a medium, and spring-launch as a campaign name; another team may have a documented naming policy. This tool preserves the text you supply after trimming accidental outer spaces, rather than inventing a taxonomy or changing its case. Avoid putting names, email addresses, phone numbers, account numbers, or other personal information in any UTM field. Query parameters can appear in browser history, referral logs, analytics systems, and shared links, so campaign labels should describe the marketing placement instead of a person.

For a repeatable workflow, begin with the final destination page, choose labels your reporting team recognizes, build the URL, copy it, and retain a simple campaign record outside the link itself. If you need to update a campaign, paste the existing link and replace the five managed values; unrelated parameters will remain in place. For a short public-facing URL, use a trusted redirect or short-link service only after you have verified that it preserves the query string. This local builder keeps the construction step quick, private, and explicit without claiming to validate your tracking or measure campaign performance.

Methodology & sources

The tool parses the supplied URL with the browser URL API and accepts only absolute HTTP or HTTPS destinations without username or password credentials. It deletes only utm_source, utm_medium, utm_campaign, utm_term, and utm_content, retains unrelated parameters and the fragment while normalizing URL query encoding, then appends trimmed source, medium, and campaign values plus optional non-empty term and content values. It must not be used with signed or pre-signed URLs. It makes no network request and does not validate analytics, redirects, attribution, or campaign performance.

Frequently asked questions

Which UTM parameters does this builder manage?
It manages the five traditional fields: utm_source, utm_medium, utm_campaign, utm_term, and utm_content. It does not add other GA4 campaign parameters.
Will existing query parameters remain in my URL?
Yes. Parameters such as ref or gclid, plus the URL path and fragment, are retained. Only existing copies of the five managed UTM keys are replaced.
Does this confirm that analytics tracking will work?
No. It constructs a URL only. It does not inspect your analytics property, redirects, consent setup, or reporting configuration.
Can I use a relative URL or an email link?
No. Enter a complete http or https web URL so the result is a usable campaign destination.
Can I use a signed or pre-signed URL?
No. The browser URL API can normalize query encoding, which can invalidate a signature. Start from an ordinary destination URL instead.
Should I put a person's name or email address in a UTM value?
No. Use campaign labels rather than personal information because query parameters can be stored or shared in logs, history, and analytics systems.

Related tools

SEO & Webmaster guides

View all