UTM Builder & Validator

How this tool computes its result

Two independent flows share one output panel. "Generate" builds a UTM-tagged URL from a destination URL plus required source/medium/campaign and optional term/content fields, blocking with an inline error if the destination is missing, a required field is empty, or the URL fails to parse. "Validate" instead accepts a pasted campaign URL (or falls back to whatever URL was just generated) and checks it for missing required parameters, duplicate parameters (the same key appearing more than once in the query string), and "extra" UTM parameters (utm_-prefixed keys outside the five standard ones). Generating a URL immediately re-runs it through this same validator, so a freshly generated link always shows its own validation summary.

Worked example

Generating a URL with destination "https://example.com/landing-page", source "newsletter", medium "email", campaign "spring-launch" (term and content left blank) produces the tagged URL plus a validation summary reading "Missing required: None," "Duplicate params: None," "Extra UTM params: None" -- term and content being empty triggers no warning since they are not in the required list.

When not to use this tool

This validates parameter presence and duplication only -- it has no knowledge of your analytics platform's actual campaign taxonomy, so a misspelled or inconsistent utm_source value (e.g. "news_letter" vs "newsletter") that would fragment your reporting passes validation cleanly since the URL is technically well-formed.

Common mistakes

• - Pasting a URL with a repeated query parameter and expecting a hard error -- it is reported as a warning under "Duplicate params," not blocked from generating a validation report.
• - Using a custom, non-standard tracking parameter (e.g. utm_referrer) and expecting it recognized as one of the standard five -- anything outside source/medium/campaign/term/content is flagged under "Extra UTM params" even when it is a deliberate custom parameter.
• - Clicking Validate with both the campaign-URL field and any prior generated URL empty -- this produces an inline error rather than a blank or default report.

Related tools