What is a New Session in Google Analytics 4 When Source/Medium Changes?

If you have a background in Universal Analytics, you’re probably used to one unbreakable rule: a change in source or medium always starts a new session. But in Google Analytics 4, that core principle no longer applies. This article explains exactly how GA4 handles sessions when a user returns from a different source and what it means for your marketing reports.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

The Big Shift from Universal Analytics to GA4

To understand the change, it helps to quickly recap how things worked in the past versus how they function now. The difference comes down to GA4’s fundamental shift from a session-based data model to an event-based one, which gives us a more accurate and user-centric view of behavior.

How Sessions Worked in Universal Analytics (The Old Way)

In Universal Analytics (UA), a session was a container for all the actions a user took on your site during a single visit. This session would end for one of three reasons:

• Time-based expiration: By default, after 30 minutes of inactivity.
• End of day: When the clock struck midnight in the timezone of your Analytics view.
• Source/Medium change: When the user arrived at your site via a new campaign, source, or medium.

That last one is the most important for this discussion. Imagine this common scenario in UA:

1. A user clicks your Facebook Ad (facebook / cpc) and lands on your product page at 10:00 AM.
2. They browse for five minutes but don't buy anything.
3. At 10:15 AM, they Google your brand name, click an organic search result (google / organic), and land back on your homepage.

Even though only 15 minutes passed, Universal Analytics would have recorded two separate sessions because the source/medium changed from facebook / cpc to google / organic.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

How Sessions Work in Google Analytics 4 (The New Way)

Google Analytics 4 throws out that old rule. GA4 is built around an event-based model, where everything a user does - from viewing a page to clicking a button - is an event. A session is simply a group of these events triggered by the same user within a certain timespan.

In GA4, a session starts with the automatically collected session_start event. From there, the session only ends for two reasons:

• Time-based expiration: The session times out after a period of inactivity (the default is 30 minutes, but this can be adjusted).
• End of day: Like UA, hitting midnight ends the session (though this isn't reported on often).

Critically, a change in source, medium, or campaign during an active session does NOT start a new session in GA4.

Let's revisit the same scenario in GA4:

1. A user clicks your Facebook Ad (facebook / cpc) at 10:00 AM, triggering a session_start event.
2. They leave and return via organic search (google / organic) at 10:15 AM.

Because the 30-minute inactivity window hasn't closed, GA4 registers this entire sequence as one continuous session. This reflects reality more accurately - it was one continuous period of consideration, not two disconnected visits.

How GA4 Assigns Credit When Source/Medium Changes

This raises the obvious follow-up question: if it’s all one session, which source gets the credit for what the user does?

The answer is that GA4 uses an event-scoped traffic source dimension. This means GA4 has the flexibility to give credit to different sources for different events within the same session. It does this using a "last non-direct click" attribution model by default for event-scoped dimensions.

Let's walk through a more detailed example to see how this works in practice.

A Step-by-Step Multi-Touch Session in GA4

Imagine a user’s journey over a 25-minute period:

1. 11:00 AM: Arrival via Facebook Ad. A user clicks an ad and lands on your site.
2. 11:15 AM: Return via Organic Search. The user opens a new tab, searches for a product review, and clicks an organic search result linking back to your site.
3. 11:25 AM: Purchase. Convinced by the reviews on your site, the user completes their purchase.

In this scenario, all these actions happened within one session. The session itself can be tied back to Facebook Ads, but the final conversion is credited to a different channel, Organic Search. This granular, event-level attribution helps you see how different channels contribute to a single conversion path.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Understanding "Session Source / Medium" in GA4

If you're looking for reporting that feels a bit more like Universal Analytics, GA4 provides a specific dimension named "Session source / medium." This dimension behaves differently from the standard Source / medium dimension.

The Session source / medium is attributed only once per session. It latches onto the traffic source that initiated the session_start event and sticks with the session for its entire duration, regardless of any other channels the user arrives from later.

Using our previous example:

• The user first arrived from facebook / cpc.
• The session_start event was attributed to facebook / cpc.
• Therefore, the Session source / medium for this entire session will always be facebook / cpc.

Key Dimensions to Know

This creates an important distinction that solves many reporting headaches in GA4. If you see seemingly mismatched data, it's often because you're comparing event-scoped dimensions with session-scoped dimensions. Here’s a simple cheat sheet:

• Source / medium: This is event-scoped. It can change multiple times within a single session and tells you which channel drove a specific event (like a purchase or a download).
• Session source / medium: This is session-scoped. It is set once, at the beginning of the session, and tells you which channel started the user's visit. It will not change mid-session.
• First user source / medium: This is user-scoped. It tells you which channel acquired the user for the very first time and is tied to the user, not the session.

What This Change Means for Your Marketing Reporting

This new session logic isn't just a technical tweak, it has practical benefits for how you analyze your marketing performance.

Fewer Sessions, More User-Centric Data

The most immediate impact is that you will almost certainly see fewer total sessions in GA4 compared to UA for the same amount of traffic. This isn't cause for alarm. It’s a sign of more accurate measurement. You're no longer artificially inflating session counts when a user is simply comparing options or interacting with multiple campaigns during a single visit.

Focusing on the Entire Customer Journey

GA4's model encourages you to think beyond the limits of a single session. By analyzing event-level data, you can see how different channels work together. A Facebook ad might be great at starting the conversation (driving the session_start event), while your SEO efforts are better at closing the deal (driving the purchase event). You can visualize this in GA4's Path Exploration reports to see the common sequences users take.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Better Cross-Device and Cross-Platform Analysis

Because GA4 is fundamentally user-centric (thanks to the Google Signal data and your own User-ID implementation), this session handling allows for a cleaner view of users bouncing between devices. Instead of tracking fragmented sessions across a phone and a laptop, GA4 can often stitch them together into a single user journey, giving you a holistic view of performance rather than disconnected data points.

Final Thoughts

Ultimately, Google Analytics 4 sessions are more durable and more aligned with actual user behavior than they were in Universal Analytics. A change in the source/medium no longer fragments a single visit into multiple sessions, which gives you a clearer and more accurate picture of a user's complete journey within one continuous period of engagement.

Of course, digging into GA4 explorations to compare event-scoped attribution versus session-scoped dimensions isn't always quick. At Graphed, we've designed our platform to abstract away a lot of this complexity. Instead of jumping between reports, you can connect your Google Analytics account and simply ask questions in plain English - like "Show me a table of users who had a session source from google / cpc but had a purchase event driven by another channel." We pull this all together for you, creating live dashboards that monitor marketing performance in real-time. It's about getting the answers you need without having to become a full-time analytics expert. Feel free to give Graphed a try and see how simple reporting can be.