Practical guide
UTM Naming Convention Guide for GA4
A campaign URL is easy to create and surprisingly easy to make inconsistent. This guide explains the five UTM parameters, why value casing matters in GA4, and how to write a naming convention that a marketing team can apply across paid search, social, email and partnerships.
Google does not mandate lowercase values or a single company-wide taxonomy. A naming convention is an internal reporting decision. This guide describes a practical default, not a GA4 platform requirement.
What UTM parameters actually do
UTM parameters are query-string keys appended to a destination URL. When a visitor arrives from a tagged link, analytics tools can read those values and group the session under a source, medium and campaign. The parameters do not change the page itself, and they are not a guarantee that a particular analytics property will attribute the visit the way you expect.
In GA4, campaign dimensions are populated from the URL when the page loads. That makes the link text part of your reporting contract. A typo in utm_source does not stop the page from working, but it can create a new report row that nobody planned for.
| Parameter | Answers | Example | Required here? |
|---|---|---|---|
| utm_source | Where the traffic comes from | Yes, by default | |
| utm_medium | The channel or vehicle | cpc | Yes, by default |
| utm_campaign | The initiative or promotion | 2026_11_black_friday | Yes, by default |
| utm_content | The creative or link variant | hero_cta | Optional |
| utm_term | A paid keyword, where used | running_shoes | Optional |
Why casing and consistency matter
GA4 generally treats campaign parameter values as case-sensitive. If one spreadsheet sends utm_source=google and another sends utm_source=Google, the reports can show separate source values. The same issue applies to title case in campaign names, trailing spaces, and aliases such as fb versus facebook.
Lowercase is popular because it removes one class of accidental variation, not because Google requires it. Pick a rule, document it, and apply it before a campaign launches. A tool can flag a mixed-case value, but it cannot decide whether facebook and meta are the same source for your business. That is a team decision.
Fragmented
utm_source=Google utm_source=google utm_source=GOOGLE
Three spellings that may become three source values.
Consistent
utm_source=google utm_source=google utm_source=google
One documented value that maps cleanly across channels.
A practical naming convention
A convention works when it is short enough to remember and specific enough to resolve disagreements. Start with these six decisions.
- Use lowercase ASCII. Prefer
paid_socialoverPaid Social. Spaces become encoding differences and are easy to mistype. - Choose one separator style. Underscores are common for medium and campaign values. Whichever you choose, use it everywhere.
- Keep a closed list of sources and mediums. A short approved list prevents a new team member from inventing
facebook_adson launch day. - Put dates first in campaign names. A pattern such as
2026_11_black_fridaysorts predictably and makes the reporting period obvious. - Use aliases explicitly. If your team prefers
facebook, mapfb=facebookin the audit rules rather than relying on people to remember. - Document the exceptions. Affiliate IDs, ad-platform macros and regional values deserve a written note. Do not hide personal data or account tokens in a UTM value.
Example team policy
| Parameter | Rule | Examples |
|---|---|---|
| utm_source | Lowercase platform identifier from the approved list | google, meta, linkedin, newsletter |
| utm_medium | Lowercase channel from a closed list | cpc, paid_social, email, organic_social |
| utm_campaign | Year, month, theme in a lowercase slug | 2026_11_black_friday |
| utm_content | Optional creative or placement label | hero_cta, carousel_2 |
| utm_term | Optional; usually paid search only | running_shoes |
A complete example URL looks like this:
https://example.com/landing-page ?utm_source=google &utm_medium=cpc &utm_campaign=2026_11_black_friday &utm_content=hero_cta
The line breaks above are for readability. In a real link, keep the query string on one line or let your builder encode it correctly.
Common mistakes to check before launch
Duplicate parameters
A URL such as ?utm_source=google&utm_source=bing contains two values for the same key. Different systems may choose different values. Fix the link by hand; an audit should not silently delete one of them.
Wrong parameter name casing
UTM_Source is not the lowercase key utm_source. Some platforms normalize it, some do not. Rename it manually rather than adding a duplicate lowercase key.
Tags in the fragment
A fragment begins with #. Tags placed after it, such as /#utm_source=google, are not part of the query string. Move them before the fragment and verify the final URL in the ad platform.
Unverified dynamic macros
Values such as {campaign_name} or {{campaign.name}} may be replaced by an ad platform at click time. A local audit should preserve them rather than lowercasing or trimming text that a platform will interpret. Confirm the macro syntax in the platform that will serve the ad.
Treating UTM rules as attribution proof
A clean URL is necessary but not sufficient. Consent, redirects, app interstitials, analytics configuration and attribution settings can all affect what GA4 records. UTM Audit Studio checks URL text against your policy; it does not claim that tracking itself is verified.
A rollout checklist for marketing teams
- Write down the approved source and medium lists in the same document as the campaign template.
- Decide on casing, separators and the campaign date format before the next launch.
- Add aliases for legacy values, but keep the canonical list small.
- Audit the full batch after the final URLs are built, not the draft spreadsheet.
- Review every suggested fix instead of approving everything by reflex.
- Keep the exported audit CSV with the launch record so changes are traceable.
- After launch, spot-check a few live URLs in GA4 rather than assuming the report is correct.
Apply the convention
Audit a batch against these rules
Paste up to 500 URLs, configure required tags, lowercase enforcement, source and medium lists, aliases and campaign style, then export a reviewable CSV. The tool runs in your browser and never opens an audited link.
This guide describes a practical team convention, not an official Google specification. Platform behavior can change; verify current documentation before making a reporting-critical decision.