Is this the same as a UTM builder?
Yes. This page uses the same underlying browser-only tool but frames it around the broader “trackable URL” job.
Can I use it without optional UTM fields?
Yes. The core workflow only needs destination URL, source, medium, and campaign values.
Does it keep the final URL readable?
Yes. The builder is designed to keep dynamic placeholders readable and static values normalized.
What makes a URL trackable?
Query parameters that your analytics tool recognises. In practice that means utm_source, utm_medium and utm_campaign, which are what GA4 and most other tools read to attribute a session to a campaign.
Will the parameters my landing page already uses survive?
Yes. Non-UTM query parameters are preserved as they are, and the hash fragment is kept. Only existing utm_ parameters get replaced with the values you set, and the tool warns you before doing so.
Why does my ampersand turn into the word and?
Because an ampersand is the separator between query parameters. A raw one inside a value would end the parameter early and break the rest of the URL. Turning it into and keeps the value readable and the URL valid.
Can I use a trackable URL in a QR code or a print ad?
Yes, and offline is where it pays off most, since there is no referrer to fall back on. Use utm_medium values like qr, print or flyer, and be consistent, because these will not map into GA4's default channel groups and you will need a custom group to see them.
Should I shorten a UTM link before sharing it?
You can, and a shortener hides an ugly query string, but the parameters must survive the redirect. Test the short link and confirm the UTM values land on the final page before you print anything.