Why is Google Analytics 4 Data Different from UA?

If you've logged into Google Analytics 4 and thought, “Wait, this doesn't match my old Universal Analytics numbers at all,” you’re not alone. The shift from Universal Analytics (UA) to GA4 wasn't just a simple update, it was a complete reconstruction of how data is collected and processed. This article will walk you through exactly why your data looks so different and what it means for your reporting.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

It All Starts with a New Measurement Model: Events vs. Sessions

The single biggest reason for data discrepancies between UA and GA4 is the change in the fundamental data model. Trying to compare them directly is like comparing kilograms to pounds - they are both measures of weight, but their scales are completely different.

Universal Analytics: The Session-Based Model

For years, marketers lived in a world defined by sessions and pageviews. The UA model was built around the concept of a "session," which is essentially a container for all the actions a user took on your site within a specific timeframe.

• Hits: Within each session, users generated "hits." Common hit types included pageviews, events (like a button click or video play), and transaction hits.
• Focus: This model was website-centric. It was excellent at telling you what happened during a single visit but struggled to stitch together a user's complete journey across multiple sessions, devices, or platforms (like a website and a mobile app).

Google Analytics 4: The Event-Based Model

GA4 threw out the session-based model entirely. In its place is a much more flexible and user-centric model where everything is an event.

• A pageview is an event, now called page_view.
• A button click is an event.
• A scroll down the page is an event, like scroll.
• A purchase is an event, often called purchase.

This approach shifts the focus from "visits" to "users" and their actions. Instead of asking "How many sessions included a blog post view?", GA4 is better equipped to answer, "What sequence of actions does a user take from their first visit to making their first purchase?" This atomic, event-level data provides a richer, more complete picture of the user journey, which is why Google made the change.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

How Key Metric Definitions Have Changed

Because the underlying models are different, the definitions for some of your most-used metrics have also changed. This is where most of the confusion arises.

Users: Total vs. Active

This is one of the first differences people notice. In UA, the primary user metric was Total Users. In GA4, the main user metric you see in most standard reports is Active Users.

• Total Users (UA): This represented the total number of unique users who initiated at least one session during the date range. Simple and straightforward.
• Active Users: This is the number of distinct users who had an engaged session or when Analytics collected a first_visit event or engagement_time_msec parameter. Essentially, it counts users who were actively engaged with your site or app.

Because "Active Users" has stricter criteria than "Total Users," your user count in GA4 will often appear lower than what you were used to in UA for the same period. GA4 does still track "Total Users," but it's not the default metric you'll see in most reports.

Sessions: A Whole New Way of Counting

The way sessions are calculated has been significantly simplified in GA4, which naturally leads to different counts.

How a UA Session Worked

A session in UA was a sensitive thing. It would end and a new one would start if any of these conditions were met:

• 30 minutes of inactivity: This is the most common one. If a user was idle for half an hour, their next action started a new session.
• The clock strikes midnight: If a user was active on your site at 11:59 PM and was still there at 12:01 AM, UA would count two separate sessions.
• A change in campaign source: If a user arrived via a Google Ad, browsed around, and then came back within 30 minutes through an organic search link, UA would chalk that up as two sessions.

How a GA4 Session Works

GA4 does away with all those rules. A session starts with the automatically collected session_start event. It ends only after 30 minutes of inactivity (this duration can be adjusted). That's it.

Crossing midnight or changing traffic sources during a single period of activity does not start a new session in GA4. As a result, you will almost always see a lower session count in GA4 compared to UA. The users and their behavior are the same, but the ruler used to measure their sessions is different.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Goodbye Bounce Rate, Hello Engagement Rate

This change reflects the philosophical shift from punishing inaction to rewarding interaction.

• Bounce Rate (UA): This measured single-page sessions - where a user landed on a page and left without triggering any other requests. A high bounce rate was generally seen as a bad thing, but it was often misleading. Did a user "bounce" from a blog post because it was bad, or because they found the exact answer they needed and left satisfied?
• Engaged Sessions: GA4 provides the much more useful metric of "Engaged Sessions." An engaged session is one that lasts longer than 10 seconds (adjustable), includes a conversion event, or has at least two pageviews.
• Engagement Rate: This is simply the percentage of sessions that were engaged sessions. Instead of focusing on the negative (bounces), you now focus on the positive (engagement).

While GA4 recently added "Bounce Rate" back into the platform, it's defined differently. In GA4, Bounce Rate is simply the inverse of Engagement Rate. An 80% Engagement Rate means you have a 20% Bounce Rate.

Conversions: All Events Are Potential Conversions

Configuring goals in Universal Analytics could be a bit restrictive. You had a limit of 20 goals per view, and they were based on a specific set of criteria (Destination, Duration, Pages/Session, or Events).

GA4 makes this much more flexible. Any event you collect can be marked as a conversion. Did a user scroll 90% in a blog post? You can make the scroll event a conversion. Did they watch a product demo video? You can make video_complete a conversion.

This new system also changes how conversions are counted:

• UA Goals: were recorded once per session. If a user completed a "Contact Us" form three times in one session, UA would only count one conversion.
• GA4 Conversions: are recorded every time the event occurs by default. If a user submits that form three times in one session, GA4 will count three conversions. This can be adjusted in your settings, but the default behavior is a key reason your conversion numbers might look higher in GA4.

How to Navigate the GA4 Landscape

Seeing all these differences can be overwhelming, but getting hung up on perfect 1-to-1 comparisons is counterproductive. The key is to understand the new logic and adapt your reporting strategy.

1. Avoid Direct, Apples-to-Oranges Comparisons

Stop trying to make your UA session count perfectly match your GA4 session count. It never will, because they are defined differently. The same goes for users, bounce rate, and conversions. The historical UA data is useful as an archive, but it's not a direct benchmark for your new GA4 performance.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

2. Focus on Trends, Not Absolutes

Your absolute numbers have changed, but trends are what matter. Is your user engagement rate going up or down over the last three months within GA4? Is your session count from organic search growing month-over-month within GA4? Use your new GA4 data to establish a new baseline and measure your forward progress from there.

3. Embrace the New Opportunities

The event-based model is more powerful. Use it to your advantage. Track more meaningful, granular interactions that matter to your business. Create custom Funnel Exploration reports to see exactly where users drop off in the conversion path, from viewing a product page to completing a purchase. This level of user-journey analysis was much harder to accomplish in UA.

Final Thoughts

The data discrepancies between Universal Analytics and Google Analytics 4 aren't a bug, they're a feature of a fundamentally different - and more powerful - measurement model. By understanding that GA4 prioritizes users and events over sessions and pageviews, you can move past worrying about mismatched historical data and begin to unlock deeper insights into how people truly interact with your business.

We know that wrapping your head around a whole new analytics platform - while also trying to stitch that data together with your dozen other marketing and sales tools - can feel like a full-time reporting job. That’s why we built Graphed. Our approach is to connect all your data sources like GA4, Google Ads, Shopify, and HubSpot in one place, so you can just ask questions in plain English - like "Which campaigns are driving engaged users and sales last month?" - and get instant, real-time dashboards without the steep learning curve.