You built a tagged link, shared it in a newsletter or a post, watched people click it, and then opened Google Analytics 4 to find nothing. No campaign, or the visits filed under Direct, or a channel called "Unassigned". It is one of the most common analytics complaints, and it is rarely a GA4 bug. It is almost always one of a short list of causes, most of which you can check in a few minutes.

The short answer: make sure you are looking at the right report (Traffic acquisition, session-scoped dimensions) after the processing delay, open your tagged link and confirm the utm_ parameters survive every redirect into the final URL, and check your parameter names and utm_medium value against GA4's channel rules.

1. You are looking at the wrong report

GA4 has two acquisition reports and they answer different questions. User acquisition shows how each user first found you. Traffic acquisition shows where each session came from. If someone who first arrived from Google comes back through your newsletter link, the newsletter appears in Traffic acquisition but not in User acquisition. For campaign checks, use Traffic acquisition and the "Session source / medium" or "Session campaign" dimensions.

2. You are looking too soon

Standard GA4 reports can take a day or more to process. Realtime shows activity within seconds but only a limited set of dimensions, so it is useful to confirm hits are arriving, not to judge campaign attribution. If you tagged a link this morning, check tomorrow before concluding it failed.

3. A redirect is stripping the tags

This is the cause I find most often in audits, and the one people least expect. The link you shared goes through one or more redirects before it reaches the page with your GA4 tag: http to https, the bare domain to www, a trailing-slash rule, a link shortener, a language redirect. If any of those drops the query string, the UTM parameters are gone before GA4 ever loads.

Testing it is simple. Paste the full tagged link into a browser, let it load, and look at the address bar. If the ?utm_source=… part is missing from the final URL, a redirect removed it. Fix the redirect rule to preserve the query string, or link directly to the final URL so no redirect is needed.

4. The parameter names or values are wrong

  • Typos and the wrong separator. GA4 reads utm_source, not utm-source, utmsource or utm_souce.
  • Tags after a #. Anything after the fragment marker is not sent to the server and is not read as a campaign parameter by default. The tags must come before any #.
  • Inconsistent capitalisation. GA4 treats values as case-sensitive, so Facebook and facebook become two separate sources. Pick lowercase and stick to it.
  • A missing utm_source. Source is the parameter GA4 relies on most. Medium and campaign without a source give you incomplete or confusing data.

Building links with a UTM generator removes most of these mistakes, because it writes the parameter names for you and encodes the values correctly.

5. Your medium does not match any channel

If your campaign shows up but its channel is "Unassigned", the tags worked. GA4 just could not file them under a default channel. Default channels are assigned by rules that look mostly at utm_source and utm_medium. A newsletter tagged utm_medium=newsletter is a common example: GA4's Email channel expects a medium of email, so the visit lands in Unassigned.

Use the conventional mediums where they exist: email for email, social for unpaid social posts, cpc for paid search, paid_social or similar for paid social, affiliate for affiliates and referral for referral links. Put the detail you care about, like the newsletter name, in utm_campaign or utm_content instead. Our guide to creating UTM links for GA4 includes a naming system that avoids this from the start.

6. Something is overriding the campaign

  • Payment and login redirects. If visitors leave your site for a payment provider or a sign-in service and come back, the return visit can be credited to that service as a referral. Add those domains to GA4's list of unwanted referrals in your data stream settings.
  • Google Ads auto-tagging. For Google Ads traffic, the gclid parameter is the main source of campaign data, and it generally takes precedence over manual UTM tags.

7. GA4 never saw the visit

Some visits are invisible to GA4 regardless of tagging. Visitors who decline analytics cookies may not be measured, or may only be modelled, depending on your consent setup. Ad and tracking blockers stop the GA4 script entirely, and among technical audiences that can be a large share of visitors.

One more possibility to rule out early: pages where the GA4 tag is simply missing. Templates that build their own page head, such as a blog post layout separate from the rest of the site, are a classic place for the tag to be forgotten. If your campaign numbers look low rather than missing, compare them against a source that does not depend on the browser, such as server logs, your email platform's click counts or the shortener's statistics. The gap tells you how much GA4 cannot see.

A worked example: the newsletter that "disappeared"

A typical case. A shop sends its monthly newsletter with links tagged utm_source=Newsletter&utm_medium=newsletter&utm_campaign=november. The email platform reports 300 clicks. GA4 shows a few dozen sessions from the campaign, most of them in a channel called Unassigned, and a spike in Direct traffic on the same day.

Three of the causes above are at work at once. The medium newsletter does not match GA4's Email channel rule, so tagged sessions land in Unassigned rather than Email. The links point to http://shop.example.com, and the redirect to https://www.shop.example.com drops the query string for some paths, so those clicks arrive untagged and are counted as Direct. And the capitalised Newsletter source does not match the lowercase newsletter used in last month's links, splitting the campaign across two rows.

The fix took ten minutes: tag future links with utm_source=newsletter&utm_medium=email&utm_campaign=2026-11-monthly, link straight to the final https://www URLs, and fix the redirect rule to keep query strings. The remaining difference between the email platform's clicks and GA4's sessions was then down to consent and blockers, which is a gap you can measure and explain rather than a mystery.

A quick test before every campaign

  1. Build the link with a UTM generator using lowercase, conventional values.
  2. Open it in a private window and confirm the parameters are still in the final URL after any redirects.
  3. Check Realtime to confirm the visit arrives.
  4. Next day, confirm the campaign in Traffic acquisition under Session campaign and the channel you expect.

Frequently asked questions

Why does my campaign show as "(not set)"?

Usually because the visit had a source and medium but no utm_campaign, or the session started without campaign data. Add utm_campaign to every tagged link.

Should I put UTM tags on links between pages of my own site?

No. Tagging internal links overwrites the visitor's original source with your internal campaign and breaks attribution. Use UTM parameters only on links that bring people to your site from elsewhere.

Do UTM parameters affect SEO?

Not if your pages have a canonical tag pointing at the clean URL, which is standard practice. Google then treats tagged URLs as duplicates of the canonical one.

Short version

Check the Traffic acquisition report after a day, open your tagged link and make sure the parameters survive redirects, use correct lowercase names with conventional mediums, and remember that consent choices and blockers hide some visits from GA4 no matter what. Most "missing" campaigns are one of those four.