Practical framework / 5 MIN READ
Choose the acquisition scope that answers the question
Read first-user, session and event-source dimensions as different views of a journey.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
Two acquisition reports can disagree because they classify different parts of customer activity. Choosing a scope deliberately is more useful than forcing all reports into one apparently consistent channel ranking.
What you will leave with: Write a scope-aware acquisition readout with compatible dimensions, metrics and interpretation.
Use this when
- User acquisition and traffic acquisition show different channel leaders.
- A custom report combines similarly named source dimensions without explanation.
This lesson explains report semantics, not which attribution model proves a channel’s incremental value.
State the journey question
Write whether the analysis asks where people were initially acquired, what brought sessions, or how a selected model assigns credit to key events. These questions support different operational decisions. An onboarding team and a repeat-visit team may need different views of the same people.
Name the population and period before selecting a report. New users, all users, sessions and key events are not interchangeable counts. Check report filters and identity limitations rather than assuming the same date range guarantees the same population across every screen.
Read the prefix and its definition
Google Analytics distinguishes First user dimensions, Session dimensions and event-scoped traffic dimensions. Its documentation also explains that their attribution behavior differs. Preserve those prefixes in exported data and chart labels instead of shortening all three to source.
Check supported dimension-metric combinations in the selected report or API. A technically available combination still needs a coherent reading. Ask a colleague to explain one row in a full sentence: these events occurred among people classified by this first-user source, for example, rather than implying every event was directly caused by that source.
Walk through a small journey
Use a non-sensitive hypothetical journey with an initial visit, a later return and a key event. Predict which dimensions describe each part before inspecting the real report. This exercise catches conceptual mistakes that a grand-total reconciliation can miss.
Keep identity and collection limits visible. A platform’s user identity may depend on available identifiers, consent and configuration. Do not promise that a single person will always remain one observed user across browsers or devices. The purpose is to understand the report’s classification, not to reconstruct an individual beyond authorized measurement.
Present complementary views without double counting
Use separate panels for distinct acquisition questions when both matter. Explain why the channel ordering differs and which decision each view informs. Never add first-user and session-level revenue views as though they represent separate sales. They can classify overlapping underlying activity.
Record scope changes alongside definition changes. A sudden improvement after replacing a session dimension with a first-user dimension is a reporting change until evidence shows otherwise. Keep previous definitions available and avoid using whichever scope flatters the channel under discussion.
Make the reasoning concrete.
A hypothetical visitor first arrives through organic search, then returns through an email link and purchases. A first-user view classifies the user by the initial acquisition; a session view describes the later visit separately. Event-credit reporting follows its configured rules.
Force one channel label
Opening: Call one report wrong because the channels differ.
Hypothesis: The same purchase appears in the analysis.
Risk: The reports answer different classification questions.
Explain the scope
Opening: Show initial acquisition and return-session context in separate views.
Hypothesis: The team can decide whether it is improving discovery or return visits.
Risk: Neither classification alone establishes the sale’s incremental cause.
Keep the full dimension names and explain the journey question each answers. Count the underlying purchase once in an overall commercial total.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Question
Is this about initial acquisition, sessions or key-event credit?
Dimension
Which exact scoped field is selected?
Population
What people or events are included?
Compatibility
Can one row be explained coherently?
Overlap
Are multiple views classifying the same commercial outcomes?
Watch for the wrong conclusion.
- Removing scope prefixes from exported labels.
- Adding overlapping scoped revenue views.
- Treating different rankings as automatic tracking failure.
- Selecting whichever scope makes a channel look best.
Your next action
Rewrite one acquisition chart title and footnote to state its exact scope, population and supported decision.
Sources & scope
Frameworks, worksheets and hypothetical examples are original editorial synthesis. Linked primary sources support only the stated concepts. Source checking is not an independent audit of effectiveness. No named human author or reviewer is claimed.
- Google Analytics: Scopes of traffic-source dimensions →Primary technical documentation · Supports: Distinguishes first-user, session and event-scoped acquisition dimensions and their attribution behavior. The lesson does not interpret these as causal channel contribution.