Why Do GA4 Acquisition Reports Show Different Numbers?

GA4 acquisition reports can show different numbers because they may describe different traffic-source scopes and use different attribution rules. If you are comparing User acquisition, Traffic acquisition, or an event-scoped attribution report, matching dates and metric names alone does not make the figures comparable. First identify the question each report answers; then check its event, filters, and attribution settings before changing UTMs or drawing conclusions about channel performance.

What each acquisition view is answering

First user source is user-scoped: it describes the source associated with acquiring the user. Session source is session-scoped: it describes the source associated with a particular session. Google identifies User acquisition with user-scoped dimensions such as First user source and Traffic acquisition with session-scoped dimensions such as Session source. Because their scopes differ, Google cautions that metric values across those reports should not be compared as if they measure the same thing. See Google Analytics Help: User acquisition report vs. Traffic acquisition report and Google Analytics Help: Scopes of traffic-source dimensions.

Event-scoped traffic-source dimensions answer a different question: they attribute key-event activity according to the reporting attribution model selected for the property. For user- and session-scoped traffic dimensions, GA4 uses paid and organic channels last click; changing the reporting attribution model does not change those dimensions. Event-scoped dimensions use the selected model. That distinction matters when an acquisition report and an attribution report appear to disagree.

Audit the two reports before interpreting the gap

Open each report or exploration and record the settings that determine what its figure means. Do not rely on a report name or a familiar channel label; note the exact dimension shown. Then classify that dimension as user-scoped, session-scoped, or event-scoped.

Record the date range and metric. Note whether the figure is users, sessions, key events, revenue, or another metric. Similar labels do not guarantee that the metric measures the same thing in every view.
Record the exact traffic-source dimension. For example, is it First user source, Session source, or an event-scoped traffic dimension? A First user dimension and a Session dimension describe different scopes.
Confirm the key event. Check which event is being counted rather than assuming each report reflects the same conversion action. GA4 allows any collected event to be marked as a key event, so confirm that the event matches the business question. See Google Analytics Help: About events.
Compare filters and report configuration. Record applied filters and other report-specific settings that could change which data appears. Scope and attribution are documented reasons for different figures, but they do not establish the cause of every discrepancy.
Check the attribution model when the dimension is event-scoped. Note the selected reporting attribution model. Google says a model change affects historical as well as future data, and affects key-event reports and explorations using event-scoped traffic dimensions. It does not change user- or session-scoped traffic dimensions. See Google Analytics Help: Change the reporting attribution model for key events.

When data-driven attribution is selected, GA4 may assign fractional credit across contributing interactions. That can make event-scoped Key events or related revenue figures appear as decimals; fractional credit is not an extra key event. Treat the figure as model-assigned credit, not proof that a channel alone caused the purchase.

Hypothetical journey: organic search, email, then a purchase

Suppose a prospective customer first visits a store from organic search, returns in a later session through an email link, and then purchases during that email session. First user source can continue to describe the acquisition source as organic search, while Session source for the return session can describe email. An event-scoped view of the purchase can assign credit according to the selected attribution model; with data-driven attribution, credit may be distributed across contributing interactions. These views can therefore classify or credit the journey differently without establishing that campaign tagging is wrong.

Allow for recent attributed key-event updates

For attributed key-event data by channel, GA4 says figures can continue updating for up to 12 days after a key event is recorded. Google recommends using a date range beyond or prior to the previous week for increased accuracy. If you are comparing recent channel attribution, repeat the comparison after that window before treating a difference as settled. This timing caveat applies to attributed key-event data by channel, not every GA4 metric or report. See Google Analytics Help: About modeled key events.

Verification checklist: is this a like-for-like comparison?

Both figures cover the same date range and use the same metric.
You have recorded each exact traffic-source dimension and identified its scope. For a direct comparison, the dimensions must have the same scope; different scopes can answer different questions.
The same intended key event is being counted, and filters and relevant report settings match.
If the comparison uses event-scoped traffic dimensions, you have checked the selected reporting attribution model.
If the comparison concerns recent attributed key-event data by channel, you have repeated it after the documented update window.
You have noted what changed and what remained different, rather than assuming a discrepancy proves a tagging or tracking error.

If the dimensions have different scopes, explain that the reports answer different questions instead of forcing their figures to match. If the comparison is like-for-like and a gap remains, investigate the specific property’s filters, report configuration, event setup, and data quality before revising UTMs or judging channel performance. Splinternet’s conversion-tracking service can help review event definitions and reporting comparisons, implement measurement changes, and keep results under review. Brian Bateman’s managed service draws on 30 years of experience and DOYJO’s process, with technology supporting ongoing data-driven improvement; it is $421 per month per business, month to month, and can be canceled at any time.

Sources

Google Analytics Help: User acquisition report vs. Traffic acquisition report

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.