How this naming generator works
Each field is normalized to a lowercase hyphenated token, then assembled into source, medium, and campaign values your team can reuse. Channel becomes utm_source after normalization. Medium is inferred from the raw channel string before normalization: lowercase substring email maps to email, lowercase substring paid maps to paid-social, and everything else defaults to referral. Campaign joins brand, audience, offer, and date with underscores after each piece is normalized.
Because the medium keyword check is case-sensitive today, type paid social or customer email in lowercase when you want the paid-social or email medium shortcut. Otherwise edit the suggested medium before you build live URLs. The generator is a starting convention, not a forced taxonomy.
Worked example: UTM Tools × Paid Social × Marketers
Using the default form values—brand UTM Tools, channel Paid Social, audience Marketers, offer Bulk Builder, date 2026 Q3—the generator returns:
| Field | Token | Why |
|---|---|---|
utm_source | paid-social | Channel label normalized to a hyphenated token |
utm_medium | referral | Raw channel has capital P, so the lowercase paid shortcut does not match |
utm_campaign | utm-tools_marketers_bulk-builder_2026-q3 | Brand, audience, offer, and window joined after normalization |
Change the channel to lowercase paid social and medium becomes paid-social while source and campaign stay the same shape. For email, use lowercase customer email to get medium email and source customer-email. Refine source to the real platform (for example linkedin) when you build the live URL.
Recommended convention checklist
- Lowercase every token; prefer hyphens inside a piece and avoid spaces.
- Reuse one campaign token across email, paid social, and partner placements for the same launch.
- Publish an allowed medium list so teams do not invent
paidsocialalongsidepaid-social. - Keep creative variants out of the campaign name—use content, term, or id later.
- Generate sample URLs and run them through the UTM Checker before links ship.
Continue the campaign workflow
Define consistent names, build one GA4 campaign URL, scale it in bulk, then check the final link before publishing.
Build a GA4 campaign URL · Define campaign names · Scale in bulk · Check the result
FAQ
What does the UTM naming convention generator output?
It returns three normalized tokens: utm_source from the normalized channel label, utm_medium inferred from lowercase email/paid substrings in the raw channel (otherwise referral), and utm_campaign built from brand, audience, offer, and date joined with underscores.
Why are campaign tokens joined with underscores while values are hyphenated?
Each input is lowercased and hyphenated first (spaces become hyphens). The generator then joins those pieces with underscores so the campaign still reads as brand_audience_offer_window while each piece stays GA4-friendly.
Why did medium become referral for Paid Social?
Medium inference looks for the lowercase substrings email or paid in the raw channel field. Title Case Paid Social does not contain lowercase paid, so medium defaults to referral. Type paid social in lowercase or edit the suggested medium before publishing.
Should I regenerate names for every creative variant?
No. Keep source, medium, and campaign stable for the initiative. Put creative, placement, or audience variants in utm_content, utm_term, or utm_id when you build the final URL.
Can I use these tokens in the bulk builder and GA URL builder?
Yes. Copy the suggested source, medium, and campaign into the Google Analytics URL Builder for one link, or reuse the same tokens across rows in the Bulk UTM Builder so every placement shares one naming system.
Does the generator store brand or campaign inputs?
No. Tokens are generated in the browser. Avoid putting private customer, employee, or deal names into any UTM field.
Last reviewed September 7, 2026. See Methodology and campaign naming conventions.