Back to the tool

Are UTM Parameters Case Sensitive? Yes, and It Quietly Splits Your Reports

Are UTM parameters case sensitive? Yes. utm_source=Facebook, utm_source=facebook, and utm_source=FACEBOOK show up as three separate rows in your analytics reports. A healthy channel can look like it is declining for a quarter when half the team tags links in title case and the other half uses lowercase. Four spellings of the same channel produce four rows, each showing a quarter of the real volume.

The confusion is understandable. Most of the web is case-insensitive about things like this. Domain names do not care about case. But UTM values are just strings that your analytics tool stores exactly as received, and GA4 does not normalize them. Whatever casing you put in the URL is what lands in the report.

Where the split actually hurts

It hurts in two places. The first is reporting. GA4's default channel grouping runs rules against your source and medium values, and the medium does most of the routing: medium=email goes to Email, medium=cpc goes to paid. If your medium is Email in one campaign and email in another, you get two rows where you expected one, and neither shows the true total. The same fragmentation hits source, campaign, term, and content.

The second is comparison. A split channel makes trends unreadable. You cannot tell whether the newsletter grew this quarter if its traffic is scattered across newsletter, Newsletter, and NEWSLETTER. Every question you ask of the data, which channel drove conversions, which campaign earned its budget, requires you to mentally merge rows first. Nobody does that consistently, so decisions get made on partial numbers.

The naming checklist I enforce

The fix is boring, which is why it works. One convention, applied at creation, beats any amount of cleanup later:

Always lowercase, no exceptions. Pick lowercase for every value you create and never deviate. This is the entire fix for the case problem. It costs nothing and it is the first thing every UTM guide recommends.

No spaces, ever. Raw spaces break URLs, so use hyphens for word separation: summer-sale, not summer sale. Some tools accept plus signs or %20 encoding, but hyphens read cleanly in reports and never cause encoding surprises.

Keep a shared value list. A spreadsheet with your approved sources, mediums, and campaign names, one row each, that the whole team tags from. facebook with medium social for organic posts, facebook with medium cpc for paid ads, newsletter with medium email for the weekly send. When someone needs a new value, it goes on the list first.

Tag only external links. UTMs belong on links pointing to your site from elsewhere: email, social, ads, partner sites, QR codes. Never tag internal links between your own pages. An internally tagged link overwrites the visitor's original source for the session, which corrupts attribution far worse than a casing inconsistency.

The keys matter too. Use the standard lowercase keys, utm_source, utm_medium, utm_campaign, utm_term, utm_content. Some platforms accept variants, but the standard keys are what GA4 reads automatically.

Cleaning up an existing mess

If the damage is already done, you have two options. GA4 lets you build custom channel groupings and exploration reports that merge the variant spellings, which fixes the view going forward without touching history. The historical data stays split. Analytics tools do not rewrite past rows. So fix the view, then fix the source: update your link builder or templates so every new tag comes out lowercase. Build the tags with consistent casing here and the problem stops compounding from today.

One honest limit applies here. No tool can retroactively merge the old rows. The split quarters stay split. What you buy with the convention is that next quarter's numbers are trustworthy, which is the only quarter you can still affect.

Frequently asked questions

Are UTM parameter values case sensitive?

Yes. Analytics tools store UTM values exactly as they appear in the URL. utm_source=Facebook and utm_source=facebook create two separate rows in GA4 and other platforms. Always use lowercase to keep each channel on one row.

Should UTM parameters ever use uppercase?

No. There is no reporting benefit to uppercase, and it guarantees fragmentation the moment anyone else on the team uses lowercase. Lowercase everywhere is the convention every major guide recommends.

Can I use spaces in UTM values?

Not raw spaces; they break URLs. Use hyphens for word separation, like summer-sale, or percent-encoding like summer%20sale. Hyphens are the cleanest choice because they read well in reports and never cause encoding issues.

Do the UTM keys themselves need to be lowercase?

Use the standard lowercase keys: utm_source, utm_medium, utm_campaign, utm_term, utm_content. These are the keys GA4 reads automatically. Non-standard casing or naming on the keys risks the parameters being ignored entirely.

Why is my campaign split into multiple rows in GA4?

Almost always inconsistent tagging: different casing, different spellings, or spaces encoded differently across links. Check the raw values in the report, pick one canonical spelling, update your link builder, and consider a custom channel grouping to merge the variants in your views.

Related reading: UTM Naming Conventions: The System That Keeps Reports Clean · utm_source vs utm_medium: Which Is Which · UTM Parameters on Internal Links: The Mistake That Rewrites Your Attribution · UTM Parameters Not Showing in GA4? The Usual Suspects

Try the tool

Build clean campaign links with saved presets, and keep them on external links where they belong. Build UTM links with the preset system.

Get new free tools by email

Want the next guide in your inbox? I publish one practical guide per new tool. Subscribe to the free newsletter on Substack. No spam, unsubscribe anytime.