Quick answer: recommended campaign convention
Use lowercase hyphenated tokens that name the initiative, not the channel. Example: q3-product-launch, webinar-followup, or partner-summer-offer.
| Rule | Do | Avoid |
|---|---|---|
| Case | q3-product-launch | Q3 Product Launch |
| Separators | Hyphens only | Mixing spaces, underscores, and hyphens |
| Scope | Name the initiative | Encoding LinkedIn, CPC, or creative into the campaign |
| Reuse | Same token across channels | One-off spellings per team or placement |
1. Start with the business initiative
Campaign should answer “which launch, promotion, or program does this click support?” If LinkedIn ads and a newsletter both support the same launch, they should share the same utm_campaign.
2. Normalize before publishing
Lowercase everything, replace spaces with hyphens, and strip punctuation that creates lookalike values. Q3 Launch, q3_launch, and q3-launch should not coexist.
3. Keep optional detail in content or id
Creative, placement, and audience variants belong in utm_content, utm_term, or utm_id. Do not force every detail into the campaign name.
Worked naming examples
| Initiative | utm_campaign | Optional content | Notes |
|---|---|---|---|
| Product launch | q3-product-launch | hero-button | Shared across email and paid social |
| Webinar follow-up | webinar-followup | reminder-1 | Sequence variants stay in content |
| Partner offer | partner-summer-offer | partner-acme | Partner identity can also live in source |
| Evergreen demo | demo-request | sidebar-cta | Stable name for always-on demand gen |
Team checklist before a launch
- Publish the allowed medium list and separator rules in one place.
- Choose the campaign token once; do not invent per-channel spellings.
- Generate sample URLs for every planned placement.
- Run each sample through the UTM Checker before links ship.
- Avoid private customer, employee, or deal data in any UTM value.
Generate names, then build the URLs
Create consistent tokens, build one GA4 URL, scale the batch, and validate before publishing.
Open the naming convention generator · Build a GA4 campaign URL · Scale with the bulk builder
Last reviewed September 6, 2026.
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 is a good UTM campaign naming convention?
Use lowercase tokens, hyphens instead of spaces, and a reusable initiative name such as q3-product-launch. Keep the same campaign token across every channel that supports that initiative.
Should campaign names include the channel?
Usually no. Put the channel in utm_medium and the platform in utm_source. Campaign should name the business initiative so multi-channel traffic groups together in GA4.
How long should a campaign name be?
Short enough to type consistently and long enough to recognize in a report. Prefer q3-product-launch over vague names like campaign1 or overlong strings that encode every targeting detail.
How do I generate consistent campaign tokens?
Use the UTM Naming Convention Generator to produce lowercase tokens, then apply the same campaign name in the Google Analytics URL Builder and Bulk UTM Builder.