UTM Link Builder

utm_source, utm_medium, and utm_campaign are required, and each is marked with a red asterisk. utm_term and utm_content are optional and are dropped from the link when you leave them blank.

Source is where the click comes from (newsletter, google, twitter), medium is the channel type (email, cpc, social), and campaign is the initiative name (spring_sale, launch). Keeping these consistent is what makes analytics reports readable.

Yes. If your destination already contains a question mark and a real parameter, the UTM values are appended with an ampersand so the existing query stays intact. A bare trailing question mark is handled too.

Yes. Spaces and special characters are URL-encoded, so a campaign like spring sale becomes spring%20sale. That keeps the link valid and prevents analytics tools from splitting a value in the wrong place.

A trailing fragment like #comments is detached, the UTM parameters are inserted before it, and the fragment is reattached at the very end. This matters because anything after the # is not sent to the server and would otherwise swallow your parameters.

utm_term is traditionally for paid-search keywords, and utm_content is for distinguishing two links to the same page, such as a text link versus a button in an A/B test. Both are optional and only appear in the URL when filled in.

It is a good habit. Most analytics platforms treat Email and email as two separate mediums, which fragments your reports, so pick one casing convention and stick to it across every link you build.

Yes. This tool exposes a JSON endpoint that takes baseUrl, source, medium, and campaign (plus optional term and content) and returns the finished url, so you can generate tagged links in bulk from a script.

Yes when built here in the browser. The link is assembled locally with no upload, so your destination URLs and campaign names never leave your device.