# UTM Naming Convention: A Template That Keeps GA4 Reports Clean (2026) > A copy-paste UTM naming convention with rules, a values table for every parameter, common mistakes, and a governance workflow that stops the messy-tag problem before it starts. URL: https://u2l.ai/blog/utm-naming-convention Published: 2026-10-02T23:19:19+05:30 Updated: 2026-10-02T23:19:19+05:30 Author: Team U2L Category: marketing Tags: utm-parameters, campaign-tracking, google-analytics, governance, marketing-analytics --- A UTM naming convention is a written rulebook that says how every campaign tag is spelled. The core rules: lowercase everything, use hyphens instead of spaces or underscores, keep utm_medium locked to Google Analytics 4's default channel groupings, use a controlled vocabulary for utm_source, and follow one consistent pattern for utm_campaign so every report groups the same clicks together instead of splitting them across misspellings. A **UTM naming convention** is a written standard for how a team spells and structures the values inside utm_source, utm_medium, utm_campaign, utm_term, and utm_content. It typically covers case (lowercase), word separators (hyphens), an allowed-values list for each parameter, a repeatable pattern for the campaign field, and rules for who reviews new values before they are used. ## Table of Contents - [Why Naming Conventions Matter (More Than the Tags Themselves)](#why-naming-conventions-matter-more-than-the-tags-themselves) - [The Copy-Paste Template](#the-copy-paste-template) - [Rule 1: Lowercase, Always](#rule-1-lowercase-always) - [Rule 2: Hyphens, Not Underscores or Spaces](#rule-2-hyphens-not-underscores-or-spaces) - [Rule 3: utm_medium Follows GA4 Channel Groupings](#rule-3-utm_medium-follows-ga4-channel-groupings) - [Rule 4: utm_source Uses a Controlled Vocabulary](#rule-4-utm_source-uses-a-controlled-vocabulary) - [Rule 5: utm_campaign Follows a Repeatable Pattern](#rule-5-utm_campaign-follows-a-repeatable-pattern) - [Rule 6: utm_content and utm_term Are for Variants, Not Everything](#rule-6-utm_content-and-utm_term-are-for-variants-not-everything) - [Common Mistakes That Break Reports](#common-mistakes-that-break-reports) - [Governance: How to Enforce the Convention](#governance-how-to-enforce-the-convention) - [Auditing an Existing Mess](#auditing-an-existing-mess) - [Frequently Asked Questions](#frequently-asked-questions) Every messy GA4 account has the same story. Somebody launched a campaign with `utm_source=Facebook`. A month later, a different teammate tagged their post with `utm_source=facebook`. Six months in, an agency layered on `utm_source=FB` and `utm_source=fb_paid`. Now the "Facebook" line in the reports is four rows, and no one is sure which is the real total. A UTM naming convention is the fix, and it does not require any new tools. It is a page of rules that everyone tagging a link agrees to follow, plus a small amount of governance to make sure new values get reviewed before they get baked into three quarters of history. Skip the convention and every downstream dashboard, attribution model, and paid-media ROI number quietly rots. Adopt one and the same reports start telling the truth without any additional software spend. This guide is the copy-paste version. Grab the template, adapt the values to your channels, and paste it into whatever wiki your team lives in. ## Why Naming Conventions Matter (More Than the Tags Themselves) GA4 (and every other analytics tool) treats parameter values as case-sensitive strings. There is no automatic normalization. `Newsletter`, `newsletter`, and `NEWSLETTER` are three different sources. `spring-sale`, `spring_sale`, and `Spring Sale` are three different campaigns. The tool has no idea they mean the same thing, so it dutifully creates a separate row for each in every report. That fragmentation shows up in three specific pain points. Campaign-level totals underreport because clicks scatter across misspelled variants. Attribution models pick the "wrong" last-touch source because the biggest driver was actually two variants totaled together. And any pivot that filters by source or medium becomes a hunting exercise across near-duplicate rows. The naming convention prevents fragmentation at the source. Every tag lives in a controlled vocabulary. Every campaign follows the same pattern. When a new value is legitimately needed, it goes through a lightweight review that adds it to the vocabulary so the next person uses the same spelling. None of this replaces the underlying [UTM parameters guide](/blog/utm-parameters-guide) that explains what each tag does. This is the layer on top: the rulebook that makes the tags trustworthy. ## The Copy-Paste Template Here is the whole convention on one card. Every rule below is a longer version of one of these lines. ``` UTM Naming Convention (v1) General: - Values are lowercase. - Words separated by hyphens (never underscores, never spaces). - Only [a-z 0-9 -] characters. No accents, no punctuation. - Values are stable. If you change a name, you split the report. utm_source Purpose: The specific platform, publication, or partner. Format: or Allowed values: See "Sources" tab in the shared sheet. Examples: newsletter, instagram, techcrunch, partner-acme utm_medium Purpose: The channel type (must match GA4 default groupings). Format: One of the approved list. Allowed values: email, social, cpc, display, referral, affiliate, organic, sms, qr, push, video, audio, print Rule: If in doubt, pick the closest GA4 default channel. utm_campaign Purpose: The specific initiative. Format: --[-] Examples: 2026-q3-spring-launch 2026-q4-black-friday-us 2026-q1-brand-awareness-eu Rule: yyyy-qq prefix required. Slug is 2-4 words, kebab-case. utm_content Purpose: Distinguishes creative or placement inside one campaign. Format: Examples: hero-cta, footer-link, story-frame-2, video-15s utm_term Purpose: Paid-search keyword (or leave blank). Format: Examples: url-shortener, qr-code-generator Rule: Only for paid search. Skip for anything else. Governance: - New utm_source or utm_medium values require review (Slack #utm). - Owner: . - Sheet: . - Reviewed quarterly, deprecated values archived. ``` Paste this into your team wiki. Fill in the owner, sheet link, and any extra source or medium values your industry needs. That is version one. ## Rule 1: Lowercase, Always **Rule:** Every character in every value is lowercase. No exceptions. The reason is boring and mechanical: analytics tools do not normalize case. `utm_source=Instagram` and `utm_source=instagram` produce two separate rows in every report. Do it enough times and every "Instagram" row has a shadow twin somewhere in the account. Lowercase is easy to enforce because it is easy to spot. If you see a capital letter in a UTM value, it is wrong. Ship a lint rule if you build tagged URLs in code, ship a form validation if you use a UTM builder, and ship a training slide if you do it manually. The one edge case is proper nouns that people naturally capitalize. `utm_source=TechCrunch` looks right to a human. It is still wrong. Write it `techcrunch` and move on. The report will still be readable. ## Rule 2: Hyphens, Not Underscores or Spaces **Rule:** Multi-word values use hyphens as separators. `spring-launch`, not `spring_launch` and not `spring launch`. Hyphens are the safest choice for three reasons. Browsers do not encode them (a space becomes `%20` or `+`, which breaks the value's spelling downstream). GA4 default channel groupings are matched with hyphenated values. And hyphens read naturally in URLs the way spaces do in prose. Underscores work technically but split the ecosystem. Some tools treat `_` as a word boundary and some do not. Search-friendly URL conventions almost universally use hyphens. Adopting the same rule for UTMs keeps the whole taxonomy consistent, which pays off when a marketer eyeballs a raw URL and can read it without a decoder ring. If your CMS or ESP inserts spaces automatically (some do, into `campaign_name` slots), catch them at the source. A single space in the raw URL corrupts the value all the way through the funnel. ## Rule 3: utm_medium Follows GA4 Channel Groupings **Rule:** utm_medium is one of GA4's default channel grouping values. Nothing custom, unless you also update GA4's grouping config. GA4 groups sessions into channels (Organic Search, Paid Search, Email, Social, and so on) based on regex rules that check utm_medium against a fixed list of allowed values. If you tag with `utm_medium=e-mail` or `utm_medium=mail-newsletter`, GA4 does not recognize it and dumps the session into "Unassigned." That defeats the whole point. The GA4-native list for 2026: `email`, `social` (organic), `paid-social`, `cpc` (paid search), `display`, `referral`, `affiliate`, `organic`, `sms`, `push`, `video`, `audio`. Values like `qr` and `print` are not GA4 channels on their own, so they need a custom channel grouping rule or they land in Unassigned. GA4's channel definitions evolve, so keep the list in sync with [GA4's documented channel groupings](https://support.google.com/analytics/answer/9756891) instead of memorizing it. Adding a custom value is fine, but only if you also add a matching regex rule in GA4 admin so the channel grouping stays clean. Ninety percent of teams should just use the defaults. ## Rule 4: utm_source Uses a Controlled Vocabulary **Rule:** utm_source draws from a maintained sheet of allowed values. Adding a new source is a governance action, not a free-for-all. The failure mode without a vocabulary is dozens of near-duplicate sources across the account. `linkedin`, `linkedin-com`, `linkedinads`, `linkedin_ads`, `li`, `LI`. Every one is the same platform. Every one gets a separate row. The report becomes a Rorschach test. The fix is a two-column sheet: allowed source values on the left, a one-line description on the right. Anyone tagging a link picks from the sheet. Anyone who needs a new source (a partner blog you have not tagged before, a newsletter sponsor you just booked) submits a request, the owner adds the row, and the value goes live. For high-volume operations, put this behind a UTM builder that reads from the sheet. U2L AI's built-in UTM builder is where our own team keeps this consistent: paste a URL, fill in the source, medium, and campaign fields from the sheet, and save the tagged short link in one step. Keeping the sheet open next to the builder is what makes typos rare. Our [link tracking pillar guide](/blog/link-tracking-guide) has the full stack recommendation. ## Rule 5: utm_campaign Follows a Repeatable Pattern **Rule:** Every utm_campaign starts with a date component and ends with a short slug. Optional region on the end. Example: `2026-q3-spring-launch` or `2026-q4-black-friday-us`. The date prefix is the single most valuable convention in a large account. It sorts campaigns chronologically in every list view, disambiguates repeated annual campaigns (Black Friday 2025 vs Black Friday 2026), and answers "when did this run" without opening the campaign brief. The slug component says what the campaign was about. Two to four words, kebab-case, meaningful. `product-launch` is fine. `new-feature-launch-announcement-final-v3` is not. Keep it recognizable at a glance. Optional region suffix handles multi-market campaigns where the same offer runs differently by geography. `2026-q4-black-friday-us` and `2026-q4-black-friday-eu` roll up under "black-friday" in a partial-match query and split apart when regional performance matters. If your business runs on a calendar year, `yyyy-mm` works instead of `yyyy-qq`. Pick one pattern and never mix. Consistency beats theoretical purity. ## Rule 6: utm_content and utm_term Are for Variants, Not Everything **Rule:** utm_content distinguishes creative or placement variants within one campaign. utm_term is only for paid-search keywords. Leave both blank if they do not apply. The trap is treating utm_content as a dumping ground for miscellaneous metadata. A tag like `utm_content=october-newsletter-hero-cta-mobile-v2` shoves five different dimensions into one value. Any pivot on it becomes a string-parsing exercise. Break the dimensions out: put the campaign context in utm_campaign, the placement in utm_content, and let each field mean one thing. Sensible utm_content values are short and describe placement or creative variant only. `hero-cta`, `footer-link`, `story-frame-2`, `banner-336x280`, `subject-line-a`. If you find yourself wanting three things in one value, you probably need to structure your naming or lean on ad platform metadata instead. utm_term is a specialized field. Google Ads populates it automatically with the search keyword when you use `{keyword}` in your tracking template. Manually tagging a random link with utm_term for anything other than paid search creates noise in reports that are wired to expect keyword data. ## Common Mistakes That Break Reports The mistakes we see most often, in rough order of how often they nuke a report: **Case drift.** `Facebook` mixed with `facebook`. A single manual link with the capital letter can silently split months of data. **Space in the middle of a value.** Usually from a copy-paste out of a doc. Becomes `%20` in the URL, becomes a mystery value in GA4. **Underscores where hyphens belong.** Not always broken, but inconsistent with the rest of the taxonomy, so downstream reports do not group cleanly. **Custom utm_medium values.** `utm_medium=insta-story` reads well but GA4 has no idea what to do with it. Session ends up in Unassigned. **Campaign field used as a source field.** `utm_campaign=instagram-october-post` is wrong on two dimensions. Instagram is a source. October is a date. Post is a placement. Splitting them properly makes every downstream slice meaningful. **Missing utm_source or utm_medium.** GA4 requires both for the campaign to appear in channel reports. Missing either drops the visit to Direct. **Tagging internal links.** A UTM on a link between two of your own pages resets the session's attribution. The original source (email, ad, whatever brought them in) gets overwritten by whatever internal UTM they clicked. Never tag internal navigation. **Re-tagging the same campaign with a new value mid-flight.** Splits the historical trend. If a name is wrong, live with it or migrate everything at once. Do not partially renumber. ## Governance: How to Enforce the Convention A convention that is not enforced is just a suggestion, and suggestions lose to speed every time. Three lightweight controls do most of the work. **A UTM builder that reads from the vocabulary.** The single most effective control. If the only way to build a tagged link is through a form that requires picking from dropdowns, the vocabulary self-enforces. Google's [Campaign URL Builder](https://ga-dev-tools.google/campaign-url-builder/) is the free minimum. A shortener with a built-in UTM builder (see [U2L AI's features](/features)) is the version that actually gets used, because the tagging happens in the same step as creating the link. **A quarterly review.** Once a quarter, someone looks at the top 100 utm_source and utm_medium values in GA4, spots any drift or unknown values that snuck in, and either normalizes them (via GA4 channel grouping rules) or adds them to the vocabulary. Twenty minutes of work, huge return. **A single named owner.** One person is accountable for the sheet. New values go through them. When somebody wonders "is this source spelled `techcrunch` or `tech-crunch`," there is a person to ask instead of a group chat that never resolves. Larger teams add a fourth layer: automated auditing that flags out-of-vocabulary values in the daily analytics feed. Overkill for most, but for anyone running hundreds of campaigns a quarter, it pays for itself in a month. ## Auditing an Existing Mess If you are adopting the convention on top of years of unstructured tags, do not try to fix history. Segment history from the going-forward standard. The pragmatic playbook: draw a line in the sand at a specific date (start of quarter is convenient). From that date forward, every new link follows the convention. For historical data, either leave it as-is (accept that the old reports are messy) or spend one focused effort on GA4 channel grouping rules that map the most common misspellings to their canonical forms (`Facebook` → Social, `FB` → Social, `facebook` → Social). Do not try to retro-tag old campaigns. UTM values live in the URLs that were shared, not in the analytics tool. You cannot change what was clicked six months ago. For the tools side of the audit, our [marketing attribution guide](/blog/marketing-attribution-guide) covers how the cleaner tags feed better attribution models, and the [campaign tracking guide](/blog/campaign-tracking-guide) shows how the convention plugs into the wider tracking stack. ## Frequently Asked Questions ### Is there a "correct" UTM naming convention I should copy? No universal standard exists. What matters is that your team has one written down and follows it consistently. The template in this post is a good starting point that plays well with GA4's default channel groupings, but adapt the source and campaign patterns to fit your business. ### Should UTM values be case sensitive? GA4 and most analytics tools treat them as case sensitive strings, so yes, they behave that way whether you want them to or not. The convention response is to write everything lowercase, which sidesteps the problem entirely. ### What is the difference between utm_source and utm_medium? utm_source names the specific place the click came from (`newsletter`, `techcrunch`, `partner-acme`). utm_medium names the type of channel it belongs to (`email`, `referral`, `affiliate`). Source is the "who," medium is the "how." ### Can I use a UTM builder to enforce the convention? Yes, and this is the single most effective way to enforce it. A form with dropdowns backed by your allowed-values list makes it structurally difficult to type a wrong value. Google's Campaign URL Builder is free; shorteners with built-in UTM builders (like U2L AI) tie the values to the link creation flow. ### What happens if I tag internal links with UTMs? The internal click resets the session's campaign attribution, so whatever brought the user in originally gets overwritten. Never tag links between your own pages. Reserve UTMs for external inbound traffic only. ### How often should I audit our UTM naming? Quarterly is enough for most teams. Look at the top 100 values in GA4 for source and medium, spot any drift or unfamiliar values, and either add them to the vocabulary or fix the source of the drift. ### Should I include the date in every utm_campaign value? For recurring campaigns (weekly newsletters, monthly promos, annual holidays), yes. The date prefix disambiguates the 2025 and 2026 versions of the same-named campaign and sorts naturally. For one-off campaigns you can skip it, but the consistency of always including it usually pays for itself. ### Do custom utm_medium values break GA4 channel reports? Yes, if the custom value does not match GA4's default channel grouping regex. The session lands in "Unassigned" instead of the right channel. Either stick to the default list (`email`, `social`, `cpc`, `referral`, and so on) or add a matching custom channel grouping rule in GA4 admin. ## Write It Down Once, Then Enforce It A naming convention is the cheapest fix in analytics: one page of rules, one owner, one allowed-values sheet, and every downstream report starts agreeing with itself. Lowercase, hyphens, GA4-native mediums, a controlled source list, and a dated campaign pattern cover almost every case. Ready to standardize your UTMs across every link your team ships? [Start with a U2L AI free account](https://u2l.ai/app/signup) and use the built-in UTM builder so every tagged short link carries your convention automatically, no wiki tab-flipping required.