Analytics & Attribution

The Same Campaign Wins in User Acquisition and Loses in Traffic Acquisition. Both Reports Can Be Right.

A GA4 user journey showing one first-user source across multiple sessions while each session receives its own traffic source.

Updated: November 20, 2026

Dimensions prefixed with First user describe how the person was originally acquired. That value remains attached when the same person returns through other channels. Use User acquisition to evaluate the channels that first introduced new users. Label the question and scope in every dashboard tile.

First-user source answers an acquisition question

Dimensions prefixed with First user describe how the person was originally acquired. That value remains attached when the same person returns through other channels.

Use User acquisition to evaluate the channels that first introduced new users. Label the question and scope in every dashboard tile.

Session source answers a visit question

Session-scoped dimensions describe how each new session began. A returning user can therefore contribute sessions to several sources while retaining one first-user source.

Use Traffic acquisition to evaluate the visits generated during the reporting period. Do not describe its rows as original customer acquisition.

Operating control table

Control Evidence Failure prevented
Owner Named reviewer and decision Unclaimed change
Configuration Saved source state Cannot reproduce
Validation End-to-end fixture Partial success accepted
Threshold Success and rollback rule Result reinterpreted
Evidence Public or reporting read-back Configured mistaken for delivered

The same metric changes meaning with scope

Engagement rate or revenue can appear beside either first-user or session dimensions. The metric name stays familiar while the population represented by each row changes.

Read the dimension prefix before interpreting the metric. Store the full dimension name in exports and chart labels instead of shortening both to Source or Campaign.

Direct return visits expose the difference

A customer may first arrive from paid search and later return directly. First-user reporting can continue crediting that person to paid search, while session reporting evaluates the later visits according to session attribution rules.

Build a simple two-session test journey and document the expected row in each report. Use it to train reviewers before investigating supposed discrepancies.

API fields must preserve the prefix

The Data API exposes separate fields such as firstUserSourceMedium and sessionSourceMedium. Choosing the convenient field without confirming scope bakes the wrong business question into automation.

Define scope in the data contract, validate compatible dimensions and metrics, and reject generic aliases that hide whether a field is user-, session- or event-scoped.

Reconcile reports without forcing them to match

User and Traffic acquisition reports are not duplicate views. Trying to make their totals align row by row removes the very distinction they were designed to show.

Reconcile total users, sessions and revenue only at compatible levels. Explain differences with a journey example, reporting identity and attribution settings rather than editing source labels after the fact.

Connect the control to the wider system

Use this process alongside the GA4 item-scope and ecommerce reporting audit. The platform setting, creative promise, measurement rule and downstream experience should describe the same decision.

Pre-launch checklist

  1. Write the decision and owner in plain language.
  2. Capture the source configuration and evidence.
  3. Test one realistic customer or reporting path end to end.
  4. Verify mobile presentation, links and accessibility.
  5. Record the success threshold and rollback trigger.
  6. Schedule the next review before material spend accumulates.

Run a cross-functional release review

Ask the channel owner, creative lead, analyst and conversion owner to inspect the same case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation.

Repeat the test on mobile and with one adverse condition. Resolve differences in the campaign brief and measurement plan before launch.

Set the review cadence before launch

Assign a monitoring owner, review frequency and evidence threshold before the change is released. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.

At the first review, reconcile the source platform, public experience and one downstream business system. Close the change only when all three support the same conclusion, and record any limitation that future analysts must preserve.

Frequently asked questions

Should this be automated?

Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.

What evidence should be preserved?

Keep the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.

When should the team roll back?

Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.

Sources

Published by Marketing That Clicks
Last reviewed November 20, 2026.