GA4 UTM Tracking Troubleshooting Guide: Root Causes, Debugging & Solutions

If a campaign appears under the wrong source or does not appear at all, follow the click from the original link to the final page. Check the tags, redirects and analytics collection in that order. The sections below cover common symptoms and how to investigate them.

The GA4 Attribution Diagnostic Flowchart

When campaign data fails to appear correctly in GA4, follow this symptom triage table:

Issue 1: Traffic Showing as Direct Instead of Paid Campaign

GA4 uses Direct / (none) when there is no clear referral source. Missing campaign information can contribute, but the presence or absence of referrer, campaign, and advertising click information affects processing. If paid clicks appear as Direct, inspect the click URL, redirect chain, landing page, and analytics data before settling on a cause.

# BROKEN REDIRECT (Query string stripped)
GET /signup?utm_source=meta -> 301 Moved Permanently
Location: https://example.com/signup/  <-- UTMs LOST!

# CORRECT REDIRECT (Query string preserved)
Location: https://example.com/signup/?utm_source=meta

Issue 2: Traffic Showing as "Unassigned"

GA4 uses "Unassigned" when the available traffic-source information does not meet an applicable Default Channel Group definition. Check the values collected and compare them with Google's current rules. For example:

• utm_medium=paidsocial vs utm_medium=paid_social (both may match paid-social medium patterns; check the source and other available values against Google's current definitions).
• utm_source=newsletter&utm_medium=email_blast (check whether the custom medium matches a current channel definition; the result depends on the available traffic-source data).

Issue 3: Campaign and Source Showing as "(not set)"

In GA4, (not set) indicates that GA4 collected an event, but the associated dimension has no recorded value. Common causes include:

1. Partial tagging: Include source, medium and campaign together, plus relevant campaign identifiers. Missing values can produce missing dimensions; check the specific field and reporting scope.
2. Measurement Protocol Mismatch: Backend offline conversion events sent via the GA4 Measurement Protocol without an attached client_id or session_id to link to the original campaign session.
3. Session inactivity: GA4 uses a configurable inactivity timeout, typically 30 minutes. Midnight or a new campaign value does not by itself restart a GA4 session. Inspect session continuity before diagnosing campaign loss.

Issue 4: Payment Gateway & Social Webview Referral Hijacking

An external payment journey can introduce an unwanted referral or interrupt measurement. Check whether client and session identifiers survive checkout, whether tags run on the return page, and whether the payment provider appears in your acquisition reports. For a practical test, use the ecommerce tracking audit.

Issue 5: Server 301/302 Redirects Stripping Query Strings

Redirect chains can affect campaign attribution if a redirect drops the incoming query string. Check each redirect response and the final landing URL. In Apache mod_rewrite, the [QSA] flag is an Apache-specific option for appending an incoming query string when a substitution already creates one. Nginx uses different configuration; consult the documentation for the server in use.

Issue 6: Consent Mode v2 Delays and Cookieless Pings

Consent behavior depends on the implementation: basic consent mode blocks Google tags until consent, while advanced mode can send cookieless pings under denied consent. Test the landing page and consent transition separately; do not infer a second session solely from a consent update. Follow Google’s consent-mode concepts and your applicable consent requirements.

Live Testing Protocol: Realtime & DebugView

Never debug campaigns by waiting 24 to 48 hours for standard GA4 acquisition reports. Follow this real-time verification process:

1. Use a complete test link such as ?utm_source=newsletter&utm_medium=email&utm_campaign=qa_audit. Enable debug mode for your own device through Tag Assistant or GTM Preview.
2. Open the URL in an Incognito browser window.
3. In GA4, go to Admin > DebugView. Select your active device stream.
4. Click on the page_view and session_start events.

Keep an evidence trail before changing settings

Record the published campaign link, final destination, consent state, collected page URL and exact report dimension. If the destination loses tags, investigate redirects first. If the destination is correct but no landing event arrives, inspect collection. If events arrive but the report looks different, compare scopes, processing and attribution settings.

Use the worked launch test and downloadable QA record. For additional instruction, Google’s official GA4 Tutorials YouTube series covers setup and integrations. For specific journeys, continue with the checkout audit, delivered email audit or LinkedIn lead audit.