


Universal Analytics: built-in filter (tick box at view-level) for bot traffic.Google Analytics 4: only built-in (automatic filter) for bot traffic.Universal Analytics: a session spans across two days -> GA creates a new session.Google Analytics 4: a session spans across two days -> GA doesn’t create a new session.Universal Analytics: campaign source change mid session -> GA creates a new session.Google Analytics 4: campaign source change mid session -> GA doesn’t create a new session.Let’s look into several reasons why sessions in GA4 and UA usually don’t match. Something is wrong (in most cases): session difference between GA4 and UA is greater than 20%.Further investigation needed: session difference between GA4 and UA is between 8 and 20%.Good: session difference between GA4 and UA is smaller than 8%.Here are some thresholds that I usually apply: In general, sessions will never fully match. Im my experience, sessions in Google Analytics 4 are often lower compared to Universal Analytics. This might make sense to you would you define a user engaged if she stays 10 seconds on your website and immediately leaves after? Why Sessions in GA4 Don’t Match with UA You can extend the 10 seconds to 60 seconds max. There is also a timer for “engaged sessions”.Įngaged sessions: The number of sessions that lasted 10 seconds or longer, or had 1 or more conversion events or 2 or more page or screen views. The minimum value of “session timeout” is 5 minutes and you can extend it to 7 hours and 55 minutes. Step 5: set the session timeout in hours and minutes. Step 3: click on More Tagging Settings at the bottom of the screen. Step 2: click on Data Streams and select the Data Stream of which you want to modify the session timeout.

It just takes a few clicks to adjust session timeout in Google Analytics 4. You can adjust the session timeout in the GA4 UI. For proper attribution and session statistics it can be helpful to lengthen the session time window. For example, an Ecommerce site where customers leave the screen for an hour or two (keep browser open) and return to finish the purchase. I have dealt with situations where you want to lengthen the session threshold time. Keep in mind though that changing this threshold will impact session numbers in Google Analytics 4 and quite a few related metrics and dimensions. This 30 minutes is a threshold that is not modified by many, but in GA4 you can easily do so (which I will show in a minute). In other words, in the last 30 minutes no new “event” was triggered. In Google Analytics 4 a user can initiate a session by either 1) opening your app in the foreground or 2) viewing a page (web) or screen (app) without having an active session.īy default, a session ends after 30 minutes of user inactivity. Let’s dive into sessions in Google Analytics 4 together! How GA4 Calculates Sessions Why Sessions in GA4 Don’t Match with UA.You will notice that your session count in GA4 doesn’t match the same number in Universal Analytics and this is normal. One type of question marketers or analysts ask me often, relates to differences in metrics between GA4 and Universal Analytics. The number of questions about GA4 are steadily growing with more companies migrating to Google Analytics 4. In this post we will explore this in all detail. Sessions in Google Analytics 4 (GA4) are calculated in a different way if compared to sessions in Universal Analytics.
