GA4 validation layer

Where UTMs show in GA4

Check the right GA4 view, match the right scope to the right question, and confirm that the tagged visit arrived cleanly before you diagnose a deeper tracking problem.

See where to look first Start with the validation problem
Session first

Validate the click that just happened with session-level reports before you look at acquisition history or channel summaries.

Scope before blame

Most “GA4 is wrong” reactions come from mixing session values, first-user values, and channel grouping as if they were one answer.

Fix upstream

If GA4 looks messy, check the tagged URL, redirect path, and launch proof before treating it as a reporting failure.

Where to look first in GA4

Start with the report and scope that match the validation question you are actually asking.

Start here first

Did this tagged visit arrive correctly?

Use Traffic acquisition with session-level source, medium, and campaign dimensions when you need to confirm the click that just happened.

How was this user first acquired?

Use User acquisition only when the question is about the user’s first-touch history, not the current click path.

What bucket did GA4 classify the traffic into?

Use Default channel grouping after the raw values already look correct. It is classification, not proof that the original tagging was clean.

Match each UTM to the GA4 field that matters

Manual tags do not live in one GA4 column. Check the field that actually answers the validation question.

UTM fieldCheck firstUse it for
utm_sourceSession sourceWho sent the visit that just landed
utm_mediumSession mediumHow the traffic arrived
utm_campaignSession campaignWhich campaign generated the click
utm_contentExplore or custom reportingCreative / placement detail when you need finer validation
utm_termExplore or custom reportingKeyword detail when it is part of the tagging model
Session dimensions

Best for launch-day verification and current click validation.

First-user dimensions

Best for acquisition history, not for confirming the click that just happened.

Channel grouping

Best for classification once the raw source, medium, and campaign values are already clean.

Start with the validation problem

The tagged URL still needs structural validationUse the machine check before blaming the report. The click lands, but parameters may be disappearingCheck the redirect path and prove the signal survives. The question is about manual campaign reporting viewsUse the dedicated manual reporting page. The visit is showing up as Direct or UnassignedUse the source-loss diagnosis page. The disagreement is really about interpretationUse the attribution boundary page before changing the tagging.

Go deeper in validation and release

UTM QA CheckerValidate the tagged URL structure before you interpret the report. Redirect CheckerConfirm that the live click path preserves the parameters and lands at the right destination. GA4 Manual Campaign ReportingUse the manual reporting page when the question is about report setup and campaign support fields. GA4 Direct / UnassignedDiagnose source loss when traffic arrives without the session values you expected. UTMs and Attribution ExplainedSeparate validation from interpretation before you escalate a disagreement between systems.