UTM Builder and Parser

Features

• Build: append five UTM parameters, spaces encoded as %20
• Parse: list each UTM parameter and its decoded value
• A separate warning when utm_source or utm_medium is missing
• Every non-UTM parameter is kept, in its original order
• Choose overwrite or keep when a parameter already exists
• Recognises non-UTM tracking parameters such as fbclid and gclid
• Parse mode also shows the landing page with tracking removed
• Several URLs at once, grouped line by line

How to use

1. Pick Build or Parse
2. In Build, fill in the five UTM values; in Parse, leave them empty
3. Paste one landing page URL per line
4. Each result is on its own row and can be copied on its own

FAQ

Why did my ?id=42 disappear after building?

It did not. Only `utm_*` parameters are added or replaced; every other parameter on the link (id, color, ref and so on) is kept exactly as it was, order included, because reordering can invalidate signed URLs. If something really is missing, it probably started with `utm_` itself and was treated as part of the same family.

What is the difference between overwrite and keep?

When the link already has `utm_source=old`: Overwrite replaces it with the value you typed, in the same position, keeping only one copy if it appears twice. Keep leaves the original alone and ignores your value, which is reported in the result. Overwrite is more common when tagging a batch of campaign links.

Why are utm_source and utm_medium treated as required?

Analytics splits traffic mainly by source and medium. Without them, filtering by campaign, content or term means much less. That is why parse mode warns separately when either is missing instead of treating them like any other parameter.