GA4 campaign reports disagree: check the scope before fixing the tags

A campaign appears in GA4’s Traffic acquisition report but contributes much less in another acquisition view. The immediate suspicion is often a broken UTM tag. Sometimes the reports are simply answering different questions.

Acquisition data can describe how a user was first acquired, what brought someone into a session, or how credit for an event is assigned. A shared word such as “source” does not make those dimensions interchangeable.

Read the full dimension name

Google’s traffic-source scope documentation separates user, session, and event scopes. “First user” describes the source associated with initial acquisition. “Session” describes the acquisition context for a session. Event-scoped attribution addresses credit for events.

Use that distinction to define the question before exporting a report:

Business question	Starting point
Where did these users first arrive from?	First-user acquisition dimensions
Which campaigns brought sessions?	Session acquisition dimensions
Which channels receive credit for key events?	The relevant attribution report and its settings

A key event is an event marked as important to the business, such as a completed enquiry. It is still necessary to check exactly what triggers it.

Walk through a returning visitor

Imagine someone first discovers a site through organic search. Several days later, they return through a tagged newsletter and submit a form.

Their first acquisition remains associated with the original discovery. The later session can be associated with the newsletter. Credit assigned to the form event depends on the applicable attribution setup and available evidence.

A first-user report and a session report can therefore describe this journey differently without either being broken. Do not rename a campaign or reinstall a tag solely to make those totals match.

This example is simplified. Consent, identity, implementation, and reporting settings can affect the recorded journey.

Make the comparison like for like

Keep the date range, property, filters, metric, and dimension scope consistent. Note the reporting time zone and the selected attribution settings where relevant.

Also separate campaign names from channel groups. A campaign label identifies an initiative. A channel classification groups traffic according to its rules. A campaign can contain more than one source or medium if that is how its links were built.

Google’s overview of traffic-source dimensions provides the terminology behind these fields. Use the actual exported column names in your reporting notes; shortening every acquisition field to “source” removes useful meaning.

Then test the tagging

If a session acquisition comparison still looks wrong, inspect a controlled visit using an approved test link and the consent state appropriate to the test. Confirm the final landing URL, parameter values, and whether redirects preserve them.

Look for duplicate parameters, inconsistent capitalization, an unexpected destination, or a campaign value overwritten by a template. The bulk UTM builder and checker can help find naming and parameter problems before launch. It cannot establish how a completed visit was attributed inside GA4.

Keep personal details out of campaign URLs and use an identifier that can be understood without exposing a customer record.

Write the reporting definition once

A useful dashboard note is specific: “Sessions by session campaign, excluding internal traffic, using the property time zone.” “Campaign performance from GA4” is too broad for someone else to reproduce.

When the question changes from acquisition to business outcomes, change the report deliberately and explain the new basis. For comparisons with ad-platform delivery, use the separate guide to advertising report differences; clicks and sessions introduce another distinction beyond acquisition scope.