UTM Builder

How it works

Enter the page you want to send people to, then fill in the source, medium and campaign name. The finished link appears as you type and the copy button takes it to your clipboard. Nothing is uploaded: the link is assembled in your browser, never opened, and never shortened or tracked.

The tool adds up to six parameters, always in this order: utm_source, utm_medium, utm_campaign, then utm_id, utm_term and utm_content if you filled them in. Per Google Analytics Help, utm_source names the referrer (for example google or newsletter4), utm_medium the channel type (cpc, email), utm_campaign the product, slogan or promo code, utm_term a paid keyword, utm_content what tells two creatives apart, such as two links in one email, and utm_id a campaign ID.

What happens to your URL

• Scheme. Only http:// and https:// are accepted. If you type example.com/shop, https:// is added. Anything else, such as javascript:, data:, ftp: or mailto:, is rejected.
• Host. A scheme-less entry must look like a host, meaning it contains a dot, or is localhost or an IPv6 address. A single word like hello is rejected. The host is lowercased and an internationalized domain becomes punycode, so münchen.de is written xn--mnchen-3ya.de. Path case and existing query values are left as typed.
• Existing query. Parameters already in the URL keep their order and the UTM parameters are appended after them.
• Fragment. The #fragment stays at the end and the UTM parameters go before it.
• Encoding. Each value is percent-encoded as UTF-8. &, =, #, ?, + and % inside a value would break the URL, so they are encoded too. Letters outside ASCII are encoded byte by byte, which is why ş becomes %C5%9F.

Two options

Convert values to lowercase runs toLowerCase() on the UTM values only, never on the path or on other parameters. It is locale-independent: a capital I becomes i, and a Turkish İ becomes i followed by a combining dot above (U+0307), which is non-ASCII and is encoded as %CC%87.

Spaces in values is %20 by default, or you can replace each run of whitespace with _ or -.

Examples

Things to watch for

• Pick one naming convention and keep it. Google's documentation says values are case sensitive and recommends a strict naming convention; Newsletter and newsletter become two rows. A short written list of allowed sources and mediums for your team prevents most reporting clutter.
• This tool does not know your analytics setup. It writes the parameters you ask for. How a given medium or source value is grouped or labelled depends on your analytics property and its settings, and that is not checked here.
• UTM parameters are visible. Anyone can read them in the address bar. Do not put names, e-mail addresses or anything private into a value.
• Do not put credentials in a link. A URL of the form https://user:password@example.com is accepted without a warning, and it would travel with the link. Leave login details out.
• Internal links. This page makes no claim about what your analytics does with UTM links placed on your own site. Check your tool's documentation and test before relying on it.
• Page reports can look different. Google notes that UTM parameters are left out of the Landing page + query string and Page path + query string dimensions and appear in Page location. Do not look for them in the first two.
• Length. Inputs up to 2,048 characters are accepted (500 per UTM field). A finished URL longer than 2,000 characters triggers a warning, a cautious limit rather than a specification one, because some browsers, servers and link shorteners may cut longer ones.
• Shortening is a separate step. If you shorten the link afterwards, test that the short link lands on the page with the parameters intact.
• The result is text. It is deliberately not a clickable link. Copy it and test it in a new tab before sending a campaign.