Are UTM parameters case sensitive in GA4? Yes, and here is what it breaks

GA4 treats UTM values as case sensitive: Facebook and facebook become two sources. What it breaks, what it doesn't, how to find it and what you can still fix.

Yes, GA4 treats UTM values as case sensitive

Google says it plainly in its guide to custom campaign URLs: parameter values are case sensitive, and utm_source=google is different from utm_source=Google. The same page recommends using lowercase as a standard practice and keeping one strict naming convention for source, medium and campaign.

In practice that means a link tagged utm_source=Facebook and another tagged utm_source=facebook become two different sources in your reports. Same audience, same platform, two rows, each holding part of the traffic. Add a utm_campaign=Spring_Sale next to a spring_sale and the campaign splits the same way.

Where it hurts, and where GA4 quietly saves you

Here is the part most posts on this topic miss. The default channel group (Organic Social, Email, Paid Search and so on) is not affected by casing. Google’s channel definitions page states that channel definitions are not case sensitive. So Facebook / social and facebook / social both land in Organic Social, and Email or E-mail as a medium still counts as Email.

That gives you a quick way to reason about the damage:

  • Channel totals are fine. If you only ever look at the channel report, casing will not change those numbers.
  • Source, medium and campaign are split. Anything broken down by Session source, Session medium, Session source / medium or Session campaign shows each spelling as its own row. That is where you compare one newsletter to another, or one launch to the last one.
  • Campaigns have no safety net. There is no channel-style rule that merges campaign names, so Black-Friday and black-friday stay apart.

Casing is also only the most visible version of the problem. fb versus facebook, a trailing space, or newsletter versus news-letter split your rows just as well, and no rule in GA4 fixes those for you.

How to find duplicates in your GA4 property

  1. Open Reports, then Acquisition, then Traffic acquisition. The default dimension is the channel group, which hides the problem.
  2. Change the primary dimension to Session source / medium and widen the date range to a few months. Sort by the dimension and scan for neighbors that differ only in a capital letter, a space or a hyphen.
  3. Repeat with Session campaign. That is usually where the worst duplicates live.
  4. For a cleaner view, build a free form report in Explore with Session source, Session medium and Session campaign as rows and Sessions as the value. Seeing the three side by side makes it obvious which links were tagged by hand.

Can you fix data that is already split?

Not inside GA4, at least not the way you would hope. There is no setting that renames a source or campaign value in data that was already collected. What you have are workarounds, and it helps to know which ones do not work before you spend an afternoon on them.

  • Data filters will not do it. GA4’s data filters exclude internal, developer or unwanted hostname traffic. They work only from the moment you create them, and what they exclude is gone for good. They remove data; they do not rewrite it.
  • Custom channel groups help at the channel level. According to Google’s help page, they can be applied to your reports retroactively, so you can build a channel such as “Partner newsletter” whose conditions list every spelling you have used. It groups the traffic; the source and campaign rows underneath still keep their original spellings.
  • Merge them in the reporting layer. In Looker Studio, a calculated field with the LOWER function applied to the source or campaign field folds the spellings into one row for every chart that uses it. If you export GA4 to BigQuery, the same idea works with LOWER() in SQL.
  • Annotate and move on. Sometimes the honest fix is a note in the report (“before March, add the two rows together”) and a clean convention from today.

The convention that prevents it

Whatever you choose, write it down once and make everyone use the same list:

  • All lowercase, in every parameter, always.
  • No spaces. Use hyphens: spring-sale-2026, not Spring Sale 2026.
  • A fixed list of sources and mediums. Decide that it is facebook and email, never fb or e-mail, and stick to the mediums the default channel rules expect (social, email, cpc, referral) so traffic lands in the right channel instead of Unassigned.
  • Build links with a tool, not by hand. Typing UTMs at 11pm is how a capital letter sneaks in.

That last point is why we built the UTM Builder widget for Webstarted Toolbox (disclosure: it is ours, and free). It lowercases every value and turns spaces into hyphens as you type, offers one tap presets for common channels (LinkedIn, newsletter, Google Ads, Instagram), remembers the values you have already used, and reads an existing tagged link back into its fields so you can edit it instead of starting over. You can try it in the browser on its page, or install it from the catalog inside Toolbox, on Mac and Windows.

Get Webstarted Toolbox

UTM Builder is a free widget for Toolbox. The app is free, needs no account, and runs on macOS 12 and later and Windows 10 and later.

Free beta · macOS · Windows (x64) · Signed & notarized · No account required