How session start works
GA4 collects session_start automatically. When activity arrives and no session is currently open for that visitor, GA4 opens one, issues it an identifier and records the event. Everything that follows in the visit — page views, clicks, form submissions, purchases — is filed under that same session until it closes.
A session closes after a stretch of inactivity, thirty minutes by default, and you can change the threshold in the property’s data settings. When the person comes back after that, activity opens a fresh session with a fresh identifier. On a visitor GA4 has never seen before, a first-visit event is recorded alongside the session start.
The event does more than count. It is the moment GA4 reads how the visit began — the referring site, the campaign tags on the URL, the click identifier from an ad — and fixes those values as the session-scoped source and medium for everything that comes after.
Why session start matters
Almost every traffic report you read is built on it. Sessions, sessions by channel, engaged sessions, entrances, landing pages: they all trace back to the moment a session was opened and the source that was captured there. If the event fires late, or the tag has not loaded when someone arrives, the visit can be credited to the wrong place or start on the wrong page.
It also shapes how you compare periods. Because a session is a window rather than a person, campaigns that bring the same audience back repeatedly generate more sessions than campaigns that bring new people once. Neither pattern is better; they just answer different questions.
Common mistakes with session start
The first is treating a session as a person. Somebody researching a school, a clinic or a property over a week is one user and many sessions, so reading session counts as demand overstates it.
The second is expecting a mid-visit campaign click to open a new session. In GA4 it usually does not; the arrival is folded into the visit already running, and the original source stays. Anyone carrying habits over from Universal Analytics finds this surprising.
The third is losing the source at a third-party page. When a visitor leaves for a payment gateway or an external booking system and comes back, the return can look like a new arrival referred by that domain, which starts a session credited to the gateway rather than to the campaign that paid for the visit.
How to act on it
Load the Google tag as early as you can on every page, including landing pages built by other teams, so no arrival is missed. Add every payment, booking and login domain to the referral exclusion list so a return trip does not open a session and take the credit with it.
Then check the basics on a real visit: open the debug view, arrive from a tagged link, and confirm that one session start is recorded with the source you expect. If sessions look inflated on a single-page site or app-like interface, the usual cause is a page-view configuration issue rather than genuine traffic, and it is worth a proper tracking review before any campaign decisions are made on those numbers.
