Acquisition reports in GA4
GA4's acquisition collection has two reports: User acquisition attributes by the channel that first brought a user, and Traffic acquisition attributes by the channel of each session. They answer different questions and rarely sum the same way, because one is keyed to first touch and the other to per-session source.
What this means
Acquisition answers 'where did this traffic come from'. GA4 splits it: User acquisition uses each user's first-user source/medium/channel; Traffic acquisition uses the session source. Both roll up into default channel groupings (Organic Search, Direct, Referral, and so on).
First-user vs session attribution
Because User acquisition is keyed to first touch, a returning user who arrives via Organic still counts under whatever first recruited them. Traffic acquisition credits the current session's source. So the same period's Organic count differs between the two reports by design. Decide which question you're asking — recruitment vs current sessions — before reading either, and don't average them.
- User acquisition: first-user channel, counted once per user
- Traffic acquisition: per-session channel
- Both roll into default channel groupings
How it appears in analytics and logs
A difference between user and traffic acquisition for the 'same' channel is expected: first-user attribution counts a channel once per user, session attribution counts it per qualifying session.
Diagnostic use case
Use Traffic acquisition to see where sessions come from now, and User acquisition to understand which channels originally recruited your users — and never expect them to reconcile.
What WebmasterID can help detect
WebmasterID classifies first-party referral and campaign sources so you can read acquisition without third-party cookies or cross-site identity.
Common mistakes
- Expecting user and traffic acquisition channels to match.
- Reading Direct as a real source rather than unattributed traffic.
- Ignoring channel-grouping rule changes when comparing over time.
Privacy and accuracy notes
Acquisition reports aggregate by channel and apply thresholds. They do not require third-party cookies to group sessions by source.
Related pages
- Engagement reports in GA4
The Engagement collection reports on what users do: events, key events (conversions), pages and screens, and landing pages. Its metrics rest on GA4's engagement model — engaged sessions and engagement time — which replaced the old bounce-centric view, so reading them means understanding what 'engaged' counts.
- The realtime report
The Realtime report surfaces events and users from approximately the last 30 minutes, refreshing continuously. It is built for spot-checking that tracking fires after a deploy or campaign launch — not for analysis. Its short window and live nature mean its totals will never reconcile with processed historical reports.
- Channel grouping rule changes
Default channel groupings are sets of rules that map sources and mediums to channels like Organic, Paid, and Referral. When a platform revises those rules — adding a channel, retiring one, or changing how a source is classified — traffic moves between channels and historical trends appear to jump. This page explains how channel-rule changes reshape reports and how to read a channel trend across a definition change.
- Attribution analytics
First-party source attribution without third-party cookies.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.