New in the kilnstl → gcodemp3 → midipsd → pngpdf → csva/b significance
UTM Link Builder
Build campaign URLs with utm_source, utm_medium, and utm_campaign parameters, correctly encoded, in your browser. No spreadsheet templates, no uploads.
Private by construction. The conversion happens in this page's JavaScript. Nothing you paste here leaves your machine, and the tool keeps working with the network unplugged.
First line is the destination URL; the lines below it are your campaign parameters as key: value pairs. The builder produces a link with proper utm_source, utm_medium, and utm_campaign parameters, percent-encoding values with spaces or special characters correctly — the part hand-typed UTM links most often get wrong — and preserving any query parameters the URL already carries. Consistency is the whole game with UTMs: analytics splits Email, email, and e-mail into three different channels, so pick lowercase conventions once and let a builder enforce the spelling.
Questions this tool gets asked
Which parameters do I actually need?
utm_source (where the click comes from: newsletter, google, linkedin) and utm_medium (the channel type: email, cpc, social) cover most reporting. utm_campaign names the push; term and content are for paid-keyword and creative-level detail.
Why did my values get percent-encoded?
Spaces and special characters are not legal in URLs; encoding them (spring%20sale) is what makes the link work everywhere. Analytics tools decode them back for reports. If you dislike the look, use hyphens: spring-sale.
Do UTM parameters affect SEO or change the page?
The page loads identically - UTMs are inert freight read only by analytics. For SEO, keep tagged URLs out of your own site's internal links and sitemaps (they create duplicate URLs); they belong on external campaigns.
Uppercase or lowercase?
Lowercase everything, always. UTM values are case-sensitive in every major analytics tool, and mixed case silently splits one campaign into several rows of reporting.