UTM Parameters Not Working in GA4?

Before going through all 10 fixes, run this quick test to narrow down where the problem is. It takes two minutes and saves you hours of guessing.

This is the most common cause. Your UTM link looks fine, but between the click and the final page load, something redirects the URL and drops the UTM parameters along the way.

Common culprits:

GA4 only recognizes specific parameter names. If you misspell one, GA4 ignores it completely — no error message, no warning, just silence.

These are the exact parameter names GA4 supports:

Common mistakes that break tracking:

Your UTMs might be working perfectly — but your data looks wrong because GA4 treats uppercase and lowercase as different values.

For example, these three are separate sources in GA4:

Instead of one "facebook" row with 300 visits, you'd see three separate rows — making it look like each source is performing poorly when they're actually the same channel.

Fix: Always use lowercase for every UTM value. No exceptions. If your team has been using mixed case, you can't retroactively fix old data, but you can standardize going forward. Write down your naming rules and share them with everyone who creates links.

Our UTM best practices guide has the full naming convention framework.

This one doesn't look like a problem at first — but it's one of the most damaging mistakes you can make.

If you add UTM parameters to links between pages on your own website (like a banner link from your homepage to your pricing page), GA4 starts a brand new session. The original traffic source gets overwritten.

Here's what happens:

Fix: Remove UTM parameters from every internal link on your website. UTMs are only for links from external sources pointing to your site. If you want to track internal click behavior, use GA4 events instead.

GA4 has multiple acquisition reports, and they show different things. This confuses a lot of people.

Also make sure you're looking at the right GA4 property. If you have multiple properties (test, staging, production), you might be checking the wrong one. It happens more often than you'd think.

GA4 is not real-time (except the Realtime report). Standard reports can take 24-48 hours to process data. If you just launched a campaign and immediately checked the Traffic acquisition report, your data might not be there yet.

Fix: Use the Realtime report for instant verification. If you see your visit there with the correct source/medium, everything is working — just wait a day for it to appear in the standard reports.

If your website uses a cookie consent banner (required in the EU and many other regions), it might be blocking GA4 from firing until the user accepts cookies.

Here's what happens: a visitor clicks your UTM link, lands on your page, sees the cookie banner, but doesn't click "Accept". GA4 never fires. The visit is never recorded. Your UTM data disappears into nothing.

Even if the user eventually accepts cookies on a later page, GA4 may start a new session — and attribute the visit to "Direct" instead of your original UTM source.

Fix: Check your Google Consent Mode settings. If analytics_storage is set to "denied" by default, GA4 won't track until consent is granted. You can enable GA4's "modeling" mode which estimates data for unconsented visits, but this won't give you exact UTM attribution. There's no perfect solution here — it's a trade-off between privacy compliance and data completeness.

This is a frustrating one. Your UTMs are working — you can see the correct source and medium in the source/medium report — but when you look at the default channel grouping, it says "Unassigned".

This happens because GA4 has built-in rules for mapping source/medium combinations to channels like "Paid Search", "Email", "Organic Social", etc. If your utm_medium value doesn't match any of GA4's expected values, it can't categorize the traffic and dumps it into "Unassigned".

For example, if you use utm_medium=paid_social but GA4's default rules don't include "paid_social", the traffic becomes Unassigned.

Fix: Two options.

Ad blockers and privacy extensions (like uBlock Origin, Ghostery, or Brave's built-in shields) can block Google Analytics entirely. When GA4 doesn't load, no UTM data gets recorded — regardless of how perfectly you set up your links.

Some privacy-focused browsers also strip query parameters from URLs, which removes your UTM tags before GA4 even has a chance to read them.

Fix: You can't force users to disable ad blockers. But you should be aware that a portion of your traffic (often 15-30% depending on your audience) will be invisible to GA4 regardless of your UTM setup. For your own testing, disable ad blockers in your browser before checking if UTMs work. If your test fails with ad blockers on but succeeds with them off, the UTMs are fine — it's just ad blocker interference.

For more complete tracking, consider server-side Google Tag Manager, which is harder for ad blockers to detect.

Sounds obvious, but it happens: the page your UTM link points to doesn't have the GA4 tracking code installed. This is common with:

Fix: Open your landing page in a browser. Right-click → View Page Source. Search for your GA4 measurement ID (starts with "G-"). If it's not there, the page isn't tracking anything. Install the GA4 tag on that page, or use Google Tag Manager to deploy it site-wide.