What is the difference between the two GA4 acquisition reports?

User acquisition is user-scoped: it groups behavior by the source, medium, or campaign that first acquired a new user. Traffic acquisition is session-scoped: it groups behavior by the source, medium, or campaign that began each session, whether the visitor is new or returning.

Choose by question: use User acquisition for “Where did we first find new users?” Use Traffic acquisition for “Which visits brought people back and produced activity?” Neither report alone proves which marketing Source belongs to a specific Lead or whether that Lead was delivered.

Google describes both as prebuilt behavioral reports, but says their scopes are different. Its current User acquisition versus Traffic acquisition comparison names the first report's focus as new users and the second report's focus as new sessions. That scope difference is the reason two apparently similar rows can show different values.

User acquisition vs Traffic acquisition at a glance

This table uses Google's current report names and dimension prefixes, verified August 6, 2026. The final column is the operational boundary a lead team should keep outside GA4.

Field User acquisition Traffic acquisition First-party Lead record
Scope User Session One Lead and its evidence
Focus How new users first arrived How new sessions began Which Source is supported for the inquiry
Dimension prefix First user Session Source plus evidence method
Example dimension First user source / medium Session source / medium Explicit intake or exact matched source
Value lifecycle Assigned from the user's first acquisition Assigned for each session Preserved with the Lead and not guessed
Best use New-user acquisition and cohort quality Visit, re-engagement, and session performance Qualification, routing, and Delivery reporting by Source

Google's traffic-source scope documentation says user-scoped dimensions keep the First user prefix and remain the same when a user returns. Session-scoped dimensions use the Session prefix and can receive new values on later visits. Keep those prefixes visible in exports and dashboard labels. Removing them creates a generic “Source” column that no longer tells the reader what the row means.

Exact names matter: First user source is not a verbose synonym for Session source. The prefix declares the scope. A report titled only “Leads by source” is incomplete until it names which source field it uses.

A deterministic three-session lead example

Consider this synthetic journey. It contains no personal data and uses tagged sources only, so the scope difference is visible without relying on an ambiguous direct visit.

Step Visit User acquisition row Traffic acquisition row Lead evidence
Session 1 First visit from Google organic search google / organic google / organic No Lead yet
Session 2 Return from a tagged email newsletter Still google / organic newsletter / email No Lead yet
Session 3 Return from a tagged paid-search campaign; form submitted Still google / organic google / cpc Lead Source supported by its intake or exact match

User acquisition answers how this user was first acquired: organic search. Traffic acquisition shows the source for each session: organic, email, then paid search. The actual Lead needs a separate Source decision based on evidence captured with that inquiry. It should not inherit the first-user row merely because it is the oldest, or the latest GA4 row merely because it is recent.

Why do the same metrics differ across the reports?

Both reports can display metrics such as engagement rate and key events, but the left-hand dimension groups those metrics differently. Google explicitly advises against comparing metric values across the two reports as if they shared one scope. In User acquisition, behavior is grouped under the dimensions that first acquired the user. In Traffic acquisition, behavior is grouped under the dimensions associated with sessions.

Start every analysis with a complete sentence: “Engaged sessions grouped by First user default channel group” or “Key events grouped by Session source / medium.” That naming habit prevents a chart from turning two valid but different questions into an apparent data-quality problem.

How should direct traffic be interpreted?

Google defines (direct) / (none) as traffic without a clear referral source. A typed URL or bookmark can be direct, but missing campaign or referrer evidence can also produce the label. Do not translate direct into “the visitor already knew us” or use it as proof that marketing played no role.

Direct is a reporting value, not a Lead Source verdict: Google's report comparison notes that session acquisition follows non-direct last-click rules and that lookback settings can affect how later direct sessions appear. Preserve raw UTM, click, landing-page, referrer, and exact-match evidence for the Lead instead of rewriting it from a GA4 row.

For reliable campaign dimensions, Google recommends cross-channel fields such as Source, Session source, and First user source and documents both manual UTM tagging and supported auto-tagging in its traffic-source collection guide. Missing UTM fields can produce (not set), so a QA process should test the final landing URL and not only the ad-platform setup screen.

Which report should a lead team use?

Choose the report that matches the decision. Add a first-party Lead source when the question moves from audience or session behavior to one operational inquiry.

Question Use Reason
Which channels first acquired new users? User acquisition The question is user-scoped and begins with first acquisition.
Which campaigns started sessions that contained lead events? Traffic acquisition The question is about visit-level traffic context.
Which Source is supported for this submitted inquiry? First-party Lead record The answer needs evidence matched to the actual Lead.
Was the Lead qualified and routed successfully? Validation and Delivery facts GA4 traffic dimensions do not prove operational outcomes.

For channel-credit questions beyond first-user and session scope, use the GA4 attribution models guide. The acquisition reports and event-scoped attribution are related, but they should not be collapsed into one generic source field.

How should GA4 context connect to a Lead Source?

In Lucidity, a Source is the marketing origin of a Lead. It is separate from the Intake that received the Lead and from the GA4 dimensions used to analyze users or sessions. Explicit attribution supplied with the intake payload takes precedence. When those fields are absent, exact first-party Tracking Pixel evidence can fill missing fields. Ambiguous nearby activity is not silently guessed.

Record What it can support What it cannot prove alone
First user dimensions How a new user was initially acquired The Source of every later Lead from that user
Session dimensions How a new or returning session began That one session caused or owns a specific Lead
Lead Source evidence Explicit or exactly matched marketing origin for one Lead Credit across every marketing touchpoint
Delivery record A forwarding attempt and its outcome for one Destination The marketing channel's causal contribution
System boundary: GA4 supplies user- and session-scoped traffic context. Lucidity keeps the first-party Lead, supported Source, Validation Outcome, Destination, and Delivery attempts. Related records should be reconciled, not treated as interchangeable facts.

The Lead Source attribution guide documents this evidence precedence in detail. For campaign capture and naming, use the UTM attribution guide for Leads.

A seven-step acquisition-report QA checklist

  1. Write the question first. Decide whether it asks about a user's first arrival, a session, an attributed key event, or an actual Lead.
  2. Name the complete dimension. Keep First user, Session, or event scope in the chart title and export header.
  3. Confirm the report unit. Do not place new users, sessions, Leads, and Delivery attempts into one unlabeled total.
  4. Check campaign tagging. Verify the final landing URL retains the intended UTM or auto-tagging evidence and investigate (not set) values.
  5. Flag direct traffic carefully. Treat it as missing clear referral context, not as proof of an unassisted visit.
  6. Reconcile without forcing equality. GA4 and first-party systems collect different records under different scopes and processing rules.
  7. Preserve Lead evidence. Keep the Source method and exact match with the Lead before reporting qualification or Delivery results by Source.

How does Lucidity preserve the reporting boundary?

Lucidity connects GA4 traffic context to a Business while preserving first-party Lead and Delivery facts. Each Lead can retain an auditable Source supported by explicit intake data or exact first-party evidence. Qualification and Delivery reporting then stays attached to the operational records that actually produced those outcomes.

This lets a team use User acquisition for first-touch audience analysis, Traffic acquisition for session analysis, and Lucidity for the Source, validation, routing, and Delivery history of the actual Lead.

Keep an auditable Source with every Lead

See how Lucidity preserves first-party Source evidence while keeping GA4 user and session context in its proper reporting scope.

Request a Lucidity attribution demo