UTM parameters are query keys you append to a landing URL so analytics can attribute the visit. Google Analytics 4 still reads the classic five: utm_source, utm_medium, utm_campaign, plus optional utm_term and utm_content. The free UTM Campaign URL Builder builds and parses those tags in your browser - nothing is uploaded. This guide explains each parameter, lowercase hygiene, parse-back, and the mistakes that quietly wreck Source / Medium reports.
Quick answer
Always set source, medium, and campaign. Keep every value lowercase and hyphenated. Use utm_content to tell two links on the same campaign apart; use utm_term for paid keywords. Put UTMs in the query string before any #hash. Parse live links back into fields before you ship a fix. The tool page owns transactional builder searches; this article covers what the parameters mean.
utm_source, utm_medium, and utm_campaign
utm_source names where the traffic came from - google, newsletter, linkedin, partner-site. utm_medium names the channel mechanism - cpc, email, social, referral, affiliate. utm_campaign names the initiative - spring-sale, q1-launch, webinar-replay. GA4 Default Channel Group rules lean heavily on source and medium pairs (google + cpc → Paid Search; newsletter + email → Email). Missing source or medium is how sessions fall into Direct or (not set).
- utm_source = platform or publisher (google, facebook, newsletter)
- utm_medium = mechanism (cpc, email, social, referral)
- utm_campaign = the named push you want to report on
- All three should be present on every paid or owned outbound link you care about
utm_content and utm_term
utm_content differentiates two creatives or placements that share the same source, medium, and campaign - hero-cta vs footer-link, or creative-a vs creative-b. Session manual ad content in GA4 Explorations is where that split shows up. utm_term is for paid search keywords when you are not relying solely on auto-tagged click IDs. Skip term on organic social and most email; skip content when there is only one link to the destination.
Lowercase hygiene - GA4 is case-sensitive
GA4 stores utm_source, utm_medium, and utm_campaign as exact strings. google and Google become two rows in Acquisition reports, and you cannot rename historical values later. Default Channel Group regexes are mostly case-insensitive, so CPC may still group as Paid Search while Source / Medium tables split. Lowercase every value at link creation - including optional term and content - unless you have a documented exception. Prefer hyphens over spaces; spaces become %20 and look messy in reports.
Parse-back - audit before you fix
A tagged URL is only useful if the five fields round-trip cleanly. Parse-back means pasting a live or drafted link and reading source, medium, campaign, term, and content as separate fields. That catches mixed case, missing campaign, duplicate old UTM keys, and tags stuck after a hash. Build and parse should be inverses: a link you generate should re-parse to the same values. Pair hygiene checks with the URL Encoder / Decoder when you need to inspect a messy query string outside the UTM fields.
Common UTM mistakes
- Putting UTMs after # - GA4 never sees fragment query tags; move them before the hash
- Mixed case (Facebook vs facebook) that splits Source / Medium forever
- Using medium values that look like sources (facebook as medium instead of social)
- Blank source or medium so sessions land in Direct / (not set)
- Spaces and Title Case in campaign names instead of hyphenated lowercase
- Replacing an entire query string and wiping ref, gclid, or utm_id you still need
A practical naming workflow
- Agree a short source / medium vocabulary before the campaign launches
- Name campaigns with hyphens and a date or quarter when useful (q1-launch)
- Reserve utm_content for A/B placements; reserve utm_term for paid keywords
- Lowercase on by default when building; parse suspect links before rewriting ads
- Keep non-UTM query keys and put the hash after the query
- Build privately in the browser - unpublished landings and internal names stay local
Build or parse a real campaign URL
SERP snippets explain the parameter names; they cannot safely hold your unpublished landing URLs. Build or parse a real link locally, then copy it into ads, email, or social.
- UTM Campaign URL Builder - Build, parse, lowercase, and predict GA4 channel groups - nothing uploaded.
- URL Encoder / Decoder - percent-encode values or parse a full query string when debugging links.
- Open Graph Tags Complete Guide - social preview tags for the same landing you are tagging with UTMs.
Frequently asked questions
Which UTM parameters are required?
Always set utm_source, utm_medium, and utm_campaign. utm_term and utm_content are optional. Missing source or medium is the usual path into Direct or (not set).
Why lowercase UTM values?
GA4 treats values as case-sensitive exact strings. google and Google never merge. Lowercase at creation so reports stay one row per channel.
What is parse-back for UTM links?
Parse-back splits a tagged URL into the five builder fields so you can audit mixed case, missing keys, or UTMs stuck after # before you rewrite the link.
Is my campaign URL uploaded?
Not on ToolsMinify. Building, parsing, encoding, and channel prediction run in the browser, so unpublished landings and internal names stay on your device.
Build UTM links without uploading
Open the free UTM Campaign URL Builder, paste a landing URL, fill source / medium / campaign, keep lowercase on, and copy the tagged link - or parse a live URL to fix one field.