How to Use This Tool
Normalize explicit source, medium and campaign labels into one reproducible convention. Generate a UTM-tagged URL and normalized naming key from user-entered source, medium and campaign values without contacting analytics.
The exact task
Campaign reports fragment when the same source appears with spaces, hyphens, capitalization and ad-hoc abbreviations across different links. This page transforms only base url, utm_source, utm_medium, utm_campaign. It does not fetch a remote resource, inspect an account, guess an omitted schema or claim that syntactically tidy output is operationally safe.
Transformation rule
Normalize each label to lowercase underscore tokens, preserve the supplied base URL, then append the three standard UTM query parameters in fixed order. The default fixture is executable, so a future change that alters punctuation, ordering, escaping or validation will fail before publication. Try a small representative sample first and compare every generated token with the source.
How to interpret the output
Adopt the displayed normalization only if it matches the organization's analytics governance; consistency matters more than this particular separator. The supporting outputs—normalized naming key, generated parameter count—make the transformation auditable rather than presenting one opaque block to copy.
Assumptions
- The base URL is already approved and uses HTTP or HTTPS.
- Lowercase underscore labels match the user's chosen convention.
- Exactly source, medium and campaign are generated.
Keep the original text unchanged until the result has been tested in the destination system. Browser processing protects against an upload by this calculator, but it does not make sensitive material appropriate to paste into an untrusted device or extension.
Limitations and safety boundary
It does not shorten links, fetch pages, validate an analytics property, preserve duplicate UTM parameters or decide a universal campaign taxonomy. This is a preparation and review tool, not a standards-complete parser, security assessment, legal determination or production deployment system.
Source and verification
The transformation rule was checked against IANA — Uniform Resource Identifier Schemes on 2026-08-26. Recheck the destination specification when its grammar can change. All processing here runs in the current browser tab; ecech receives no input through a calculation API.
Sources & assumptions
Tool Spec v2 · verified 2026-08-26. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- IANA — Uniform Resource Identifier Schemes (checked 2026-08-26)
Model assumptions
- The base URL is already approved and uses HTTP or HTTPS.
- Lowercase underscore labels match the user's chosen convention.
- Exactly source, medium and campaign are generated.
- It does not shorten links, fetch pages, validate an analytics property, preserve duplicate UTM parameters or decide a universal campaign taxonomy.
