How session-scoped dimensions work
A session is one continuous visit to your site or app. A session-scoped dimension describes that visit as a whole, so GA4 stamps the same value on every event inside it and stops at the boundary. The next visit gets its own value, even if it is the same person on the same phone an hour later.
The best known examples are the traffic ones: session source, session medium, session campaign and session default channel group. GA4 works these out from how the visit began — the link that was clicked, the referring site, the campaign tags on the URL — and then holds them steady for the rest of the visit. You can add your own session-scoped values too, though it is a narrower need than user or event scope.
Why session scope matters
It is the scope that answers “what brought this visit in”. If you want to know which channel produced enquiries this week, session scope is what you group by, because it ties the outcome to the way that particular visit started rather than to how the person first found you a year ago.
It also explains why two dimensions with almost the same name disagree. Session source describes this visit; the first user source describes how the person originally found you and never changes. Both can appear in the same report and both can be right, which is why picking the user-scoped or session-scoped version deliberately matters more than it looks.
Common mistakes with session scope
The most frequent problem is mixing scopes in one table. Put a session-scoped dimension next to an event-scoped one and GA4 has to spread the session value across events that never carried it, which produces rows that look precise and are not. Reports behave far better when everything in them shares a scope.
The second is assuming a new campaign restarts the session. In GA4 it does not. If someone is already browsing and then clicks a tagged link from an email or an ad, that arrival is usually folded into the visit already in progress, and the session keeps the source it started with. Sessions end on inactivity, so a return the next morning is a fresh visit with a fresh source.
The third is losing the source at a payment gateway or booking system. When traffic bounces out to another domain and comes back, the return leg can register as a brand-new session referred by that gateway, and the original campaign disappears from the report.
How to act on it
Decide the scope before you build the report, not after the numbers look odd. Ask whether the question is about a person, a visit or a single action, and pick the matching dimension family. Tag your own campaign links properly so the session source has something reliable to read, and add every payment or booking domain to your referral exclusions so a checkout does not steal the credit. If the channel figures still do not reconcile with your ad platforms, that is a job for a proper analytics and tracking review rather than a dashboard tweak.
