What session source measures
Session source is the origin attached to one visit. When a session begins, analytics looks for a referring address or campaign parameters on the link, records what it finds, and keeps that value for the whole of that visit. Come back a week later from somewhere else and a new session begins with a new source; the old one is not overwritten, because it belongs to a different visit.
That is what separates it from first user source, which records only how a person reached you the very first time and never changes afterwards. Both describe the same visitor and both are correct. Session source answers what brought them back today; first user source answers who found them originally. Reports that mix the two produce numbers that will not reconcile.
An important detail: an existing session does not change source mid-visit in the way people expect. If someone is already browsing and then clicks one of your ads, most setups will start a fresh session rather than rewrite the current one, so the ad gets its own row.
Why session source matters
It is the metric that answers day-to-day questions honestly. If you want to know which campaign produced this week’s enquiries, you want session source, because it credits the visit in which the enquiry actually happened rather than a channel that introduced the person months earlier.
It also exposes how people really behave. Very few enquiries come from a single visit, and session source shows the repeat pattern plainly: an advertisement bringing someone in, then a search for the brand name, then a direct return to decide. Reading only the last of those would credit the wrong channel with the whole result.
Common mistakes with session source
The first is comparing it against acquisition reports built on first user source and treating the difference as an error. It is not an error; the two are answering different questions, and channels that create demand always look larger in first-touch reporting than in session-based reporting.
The second is forgetting that a session ends after a period of inactivity or at the end of the day. A visitor who leaves a tab open and returns hours later can generate a second session from direct traffic, which quietly moves credit away from the campaign that started the journey.
The third is reading it in isolation for anything with a long decision. A single-visit view suits fast purchases and misrepresents services where people take weeks to choose.
How to act on it
Pick the dimension deliberately for each question rather than accepting whatever the default report shows. Use session source for campaign performance and weekly reporting, and first user source when you are asking which channel finds new people. Say which one a report uses on the report itself, so nobody reconciles two figures that were never meant to match.
Make sure the underlying values are trustworthy before drawing conclusions, since a session source is only as good as the tagging behind it and the referral exclusions protecting it. If the property has never been configured properly, a proper GA4 implementation comes before any of this reporting is worth acting on.