Google Analytics 4 vs Universal Analytics: Differences and Migration

Google Analytics 4 vs Universal Analytics: What Changed and Why It Matters

Universal Analytics is gone. Not deprecated — gone. On July 1, 2023 it stopped collecting new data. On July 1, 2024, Google deleted all historical UA data from the interface. If you didn't migrate or export before that date, your old data is unrecoverable.

That's the headline. The longer story is that Google Analytics 4 isn't just a rebranded UA. It's a different product built on a different data model, with renamed metrics, a redesigned interface, and a learning curve most marketers underestimated. The reports you knew don't exist in the same place. Bounce rate works differently. Sessions count differently. Pageviews aren't called pageviews anymore — they're "views," tracked as one event type among dozens.

Google didn't force this switch arbitrarily. UA was built in 2012 around a session-and-pageview model that made sense for desktop websites and predictable user journeys. By 2020 most users moved between mobile apps, web, multiple devices, and privacy-restricted browsers — UA couldn't model that cleanly. GA4's event-based architecture handles cross-platform tracking, integrates machine learning for predictive metrics, and complies with stricter consent rules out of the box.

That's why this guide exists. If you've already migrated, you need to understand why your GA4 numbers don't match your UA numbers (different counting methods — see below). If you haven't migrated, you need to know what's salvageable and what to do next. The full picture starts with a clear-eyed look at what is google analytics 4 as a product separate from its predecessor — same name, very different tool. For the practical day-to-day, our how to use google analytics walkthrough covers the GA4 reporting interface from setup to first reports.

Short answer for the impatient: GA4 is more powerful, harder to learn, and your old data is probably gone. Keep reading for the eight differences that matter most.

UA Sunset Timeline — What Happened and When

Google announced the UA deprecation in March 2022, gave users 16 months to migrate, then stopped data collection on the original July 1, 2023 deadline. Most properties got auto-migrated to a basic GA4 setup by Google's automated tool — but "basic" meant tracking ID only. Custom events, conversion goals, audiences, and ad-account linking didn't carry over. If you didn't do the manual migration work, your GA4 property is missing the configuration that made your UA reports useful.

The 8 Differences That Actually Matter

Google's official documentation lists dozens of changes. Most are cosmetic. These eight are the ones that change how you do your job.

1. Data Model — Sessions and Pageviews vs Events

UA tracked sessions and pageviews as the core unit. A user visited, viewed pages, those pageviews aggregated into a session, sessions rolled into users. Simple, predictable, somewhat limited.

GA4 tracks events. Everything is an event — a page load fires a page_view event, a scroll fires scroll, a file download fires file_download, a video play fires video_start. GA4 automatically collects around 90 events without any configuration. Custom events you define get the same treatment. This is more flexible but completely changes how you query data.

2. Metrics Renamed — Bounce Rate, Sessions, Users

The metric you trusted in UA either disappeared or means something different in GA4. Bounce rate in UA = sessions with a single pageview. GA4 originally killed bounce rate, replaced it with engagement rate (sessions lasting 10+ seconds, OR with a conversion event, OR with 2+ pageviews). After backlash, Google added bounce rate back as the inverse of engagement rate — but the calculation is different from UA's, so the numbers don't match.

Sessions count differently too. UA started a new session whenever a campaign source changed mid-visit (utm_source parameter rewrite). GA4 doesn't do that. One visit, one session. Users went from a 30-day window in UA to 28-day active users in GA4. Pageviews became simply "views" — the same metric, renamed and tracked as a page_view event count.

3. Reports — From 50 Prebuilt to 25 Plus Explore

UA's sidebar had Audience, Acquisition, Behavior, Conversions, Real-Time — roughly 50 prebuilt reports across those sections. GA4 has User, Acquisition, Engagement, Monetization, Retention — about 20-25 prebuilt reports. The rest moved to the Explore module, where you build custom analyses using Free-Form, Funnel, Path, Segment Overlap, and Cohort templates. Explore is more powerful than UA's custom reports but takes longer to learn.

4. Setup IDs — UA-XXXXX vs G-XXXXX

UA used tracking IDs formatted UA-XXXXXXX-X. GA4 uses Measurement IDs formatted G-XXXXXXXX. If your site still has only a UA tag in the header, it's collecting nothing. Check your tag manager or site source. For most marketers, the smoothest path involves working with google analytics consultant or a contractor who's done this migration before — the configuration translation is mechanical but easy to mess up.

5. Cross-Platform Tracking — Web + App in One Property

UA was web-only. If you had a mobile app, you used Firebase. GA4 unifies web and app tracking under one property — multiple data streams (web, iOS, Android) flow into the same reports. For businesses with apps, this is a major upgrade. For web-only businesses, it doesn't matter.

6. Conversion Goals — Goals Are Now "Conversions"

In UA you defined goals (destination URL, duration, pages per session, event). GA4 doesn't have goals. You mark an event as a "conversion" in admin settings. Up to 30 events can be marked as conversions per property. The migration tool didn't carry these over — you had to re-create them manually in GA4.

7. Audiences and Predictive Segments

UA audiences were rule-based — visited page X, spent more than Y seconds, came from source Z. GA4 audiences add machine learning predictions: "likely to purchase in the next 7 days," "likely to churn," "predicted revenue." These predictive audiences require enough conversion data to train the model (Google requires 1,000+ returning users with conversion events in the previous 28 days).

8. BigQuery Export — Free for Everyone Now

This is the change nobody saw coming. In UA, BigQuery export was a GA360 enterprise-only feature costing $150K+/year. In GA4, BigQuery export is free for all properties — up to 1 million events per day on the free tier, with a 1GB daily streaming limit. If you've avoided GA's interface limitations, BigQuery gives you raw event data you can query with SQL. Pair this with your existing google analytics for seo tracking and you can do attribution analysis UA couldn't.

Where Your UA Reports Moved in GA4

If you've been hunting for reports that used to be right there in UA's sidebar, here's the rough translation. UA's Audience Overview = GA4's User → User Acquisition. UA's Behavior Flow visualization is gone entirely — closest replacement is GA4's Explore module with the Funnel exploration or Path exploration templates, both of which need manual setup. UA Real-Time is still called Real-Time. UA's E-commerce reports moved to Monetization. UA's Site Search became a custom event you have to configure yourself.

What You Lost, What You Gained

Migration always means trade-offs. Here's the honest accounting of where GA4 is worse than UA, and where it's substantially better.

What You Lost

Historical data, primarily. Unless you exported to BigQuery (GA 360 only) or downloaded CSV reports before July 2024, your UA data is gone. Year-over-year comparisons reset to zero in GA4.

Behavior Flow visualization is gone. The squiggly path diagram showing where users moved between pages? Doesn't exist in GA4. The closest equivalent is Path exploration, which is more cumbersome to set up and harder to read.

View filters — gone. UA let you create multiple Views of the same property with different filters applied (internal traffic excluded, specific countries only, test versus production). GA4 has Data Filters at the property level only, with limited options (Internal Traffic, Developer Traffic, no IP-based exclusion the way UA had).

Custom Reports as you knew them — gone. Build them in Explore now. Functional but different. Most analysts need a few hours to rebuild reports they used daily in UA.

Real-Time depth — reduced. UA's Real-Time reports showed users, pages, events, conversions, and locations across multiple tabs. GA4's Real-Time is a single dashboard with less drill-down.

What You Gained

Event-level data. Every interaction is captured as an event with parameters. UA forced you to track everything through custom events with limited parameters (event category, action, label, value). GA4 lets you define up to 25 parameters per event. For complex analytics, this is transformative.

Free BigQuery export. The biggest gift Google gave non-enterprise users. You can pipe every event into BigQuery, query with SQL, build dashboards in Looker Studio or any BI tool. UA charged $150K+/year for this through GA 360.

Predictive analytics. Purchase probability, churn probability, predicted revenue — Google's ML estimates these for individual users based on conversion data. UA had nothing comparable.

App + web unification. If you have a mobile app, GA4 tracks it alongside your website in one property. Cross-platform user journeys are visible without the gymnastics UA required.

Cleaner privacy story. Consent Mode v2 is built in. Cookie-less measurement using modeled data fills gaps from users who decline consent. UA was a constant scramble with cookie banners and consent plugins.

Better integration with the broader Google stack. Google Ads, Google Tag Manager, Search Console, BigQuery, Looker Studio — everything connects more cleanly in GA4. For SEO work specifically, our google analytics website traffic guide covers the reports SEO teams use most. To go deeper, google analytics course reviews catch you up on the GA4-specific training that didn't exist in UA's curriculum.

Migration — What to Do Now

If you're reading this and haven't migrated, the situation depends on what's on your site right now. Most properties got auto-migrated by Google's setup assistant in late 2022 — your GA4 property exists with basic tag tracking. The work that remains is configuration: conversions, audiences, custom dimensions, e-commerce events.

Step 1 — Confirm Your GA4 Property Exists

Log into analytics.google.com. Look at the property selector. You should see two properties: your old UA property (data viewable until July 2024, empty after) and a new GA4 property. If you only see UA, Google's auto-migration didn't run — you need to create a GA4 property manually via Admin → Create Property.

Step 2 — Check the GA4 Tag Is Firing

Open Realtime → Overview. Visit your site in another tab. You should see your visit appear within 10 seconds. If nothing shows up, the GA4 tag isn't installed. Check Tag Manager or your site's <head> for the G-XXXXXX measurement ID.

Step 3 — Recreate Conversions

Admin → Events → mark important events as conversions. Common ones: purchase (auto-tracked for e-commerce), generate_lead, sign_up, contact. You can have up to 30 conversion events.

Step 4 — Set Up Custom Events for What Auto-Tracking Misses

GA4 auto-tracks scrolls, file downloads, outbound clicks, video engagement, site search — but it might miss things specific to your site. Custom events go through Google Tag Manager or direct gtag.js calls.

Step 5 — Connect Google Ads

Admin → Product Links → Google Ads → connect your account. Conversions sync automatically. Audiences become available for remarketing campaigns. Get the right google analytics account permissions before this step — you need Editor or Administrator role on the GA4 property and the Ads account.

Step 6 — Enable BigQuery Export

Admin → BigQuery Linking → link a GCP project. Free up to 1M events/day. This single step is the biggest reason to migrate — you get raw data access UA never gave non-enterprise users. To use the data for SEO analysis, including not-provided keyword workarounds, our guide on google analytics not provided keywords shows the BigQuery queries that surface what Search Console hides.

If You Didn't Migrate Before the Sunset

Real talk: your UA data is gone. Google deleted it. No amount of escalating with Google support will recover it. The only path forward is to set up GA4 fresh and start building new data.

The good news — that 12-18 months of fresh GA4 data will eventually replace what you lost, with better granularity than UA ever provided. The bad news — your year-over-year analysis is broken until at least mid-2025.

What to check before assuming everything is lost: third-party tools you used alongside UA may have your traffic data archived independently. Marketing dashboards built on BI tools often have UA data snapshots in their data warehouses. Old screenshot reports, monthly emails sent to stakeholders, and shared Google Slides decks may have traffic numbers you can rebuild metrics from. None of this replaces clean data, but it can fill historical gaps.

Why Your GA4 Numbers Don't Match Your UA Numbers

This trips up almost everyone. Your GA4 sessions show 50% fewer than UA reported for the same period. Your conversion count is half. Bounce rate looks dramatically different. Stakeholders accuse the new data of being wrong.

It isn't wrong. The math is different.

UA counted sessions when a user arrived AND the campaign source changed mid-visit (utm_source parameter rewrite started a new session). GA4 doesn't do that — one visit equals one session regardless of mid-visit URL parameter changes. This alone makes GA4 sessions appear lower than UA sessions for sites running paid ads.

UA's bounce rate was strict — single pageview, period. GA4's bounce rate inverts engagement rate. A user who scrolls past 90% of a page and stays 30 seconds but views only one page counts as engaged in GA4 (not a bounce). In UA, that was a bounce. Same user, opposite metric value.

Users count differently too. UA used a 30-day window for unique users. GA4 uses 28-day active users. Tiny difference, but compounded over months it adds up.

Conversions — GA4 counts every conversion event, not just the first per session. If a user submits a form twice in one session, GA4 logs 2 conversions; UA logged 1. For lead-gen sites this inflates conversion counts dramatically.

Bottom line: stop comparing GA4 numbers to UA numbers. The math is different by design. Use GA4 as your new baseline. Year-over-year comparisons start fresh from your GA4 launch date.