The short version: Google Analytics is now called GA4 because it is the fourth generation of the platform, built around a completely different measurement model than the one before it. The old version, Universal Analytics, stopped processing data on 1 July 2023, and Google replaced session-based tracking with event-based tracking to cope with a world that has fewer cookies, more app traffic, and stricter privacy rules. It is not a rebrand or a fresh coat of paint, it is a different tool wearing a familiar name, and knowing that changes how you should treat the numbers it gives you.
A quick timeline, because the dates explain everything
Google bought a company called Urchin in 2005 and turned it into Google Analytics. That first version got a major overhaul in 2012 called Universal Analytics, which most marketers just called “GA” for the next decade. In 2019, Google quietly launched a beta property type called “App + Web,” designed to track a single business across a mobile app and a website in one dataset. In October 2020, Google renamed that beta and released it publicly as Google Analytics 4, or GA4. The 4 refers to it being the fourth major version of the tool, not the year, not a subscription tier.
Then came the deadline that forced everyone’s hand: in March 2022, Google announced that standard Universal Analytics properties would stop collecting new data on 1 July 2023, with the larger Analytics 360 accounts getting a slightly later cut off of 1 July 2024. After those dates, the old reports still existed to view for a limited window, but no new visits, clicks, or conversions were recorded. If you didn’t set up a GA4 property before that date, you have a gap in your data that nobody can fill retroactively.
Why the name is a version number, not a marketing decision
Most software companies would call this an upgrade and leave the name alone, the way Microsoft Word didn’t become “Word 2.” Google chose to put the version number front and centre because the internal architecture is different, not just the interface. Universal Analytics organised everything around sessions, a session was a visit to your site with a start and an end, and every pageview, click, or purchase sat inside that session container. GA4 throws that container away. Everything, a pageview, a scroll, a video play, a form submission, a purchase, is logged as an individual event with its own parameters, and sessions become just one more thing that gets calculated from those events rather than the frame everything else sits inside.
That is a bigger deal than it sounds. It means bounce rate is calculated differently (GA4 originally removed it, then brought back an “engaged sessions” version because businesses complained). It means a single user browsing your site on their phone, then again on your app, then completing a purchase on desktop, can be stitched into one user journey instead of three disconnected visits. If you want the fuller picture of what the tool tracks and why that matters for your marketing decisions, it’s worth reading a plain explanation of what Google Analytics does and why it matters before you try to rebuild your reports.
What moving to events changed day to day
In Universal Analytics, you had to manually configure “goals” to track most meaningful actions, like a newsletter signup or a demo request. GA4 automatically captures a set of events the moment you install the tracking code, including page_view, click, scroll (fired once someone reaches 90 percent of a page), file_download, and video_start. On top of those, a standard GA4 property lets you register up to 500 distinct event names, each carrying up to 25 custom parameters, which is a genuine expansion on what most small businesses ever configured under the old system.
The catch is that this flexibility means almost nothing gets tracked usefully out of the box for ecommerce or lead generation businesses. You still need to set up conversion events, name them consistently, and check they’re firing correctly, which is exactly the kind of unglamorous setup work that gets skipped. If you’ve never gone through this, it’s worth reading through what Google Analytics events are and why you should track them, because the whole GA4 model only pays off once your events are named and structured well.
A migration I watched go wrong, and what fixed it
In spring 2023, I was brought in by a small ecommerce client, a home fragrance brand doing around £40,000 a month in online sales, who had left their Universal Analytics property untouched because “it still worked fine.” It did still work fine, right up until 1 July, when it simply stopped. They were three weeks from a funding conversation and needed year-on-year traffic and conversion numbers for their pitch deck. They had none, because their GA4 property had only been created six weeks earlier, so there was no comparable data to sit alongside the previous year’s Universal Analytics figures.
What we did was pull the last full year of Universal Analytics data out as a static export before the viewing window closed, rebuild their key conversion events fresh in GA4 (purchase, add_to_cart, and a custom “email_capture” event they’d never bothered configuring in the old tool), and cross-check the new numbers against their Google Ads account to make sure conversions were being attributed correctly across both platforms, following the same steps I’d give any client trying to link Google Ads with Google Analytics correctly. It took roughly nine hours of setup and QA work, spread over four days, to get a property that a funder could look at with confidence. The lesson wasn’t about GA4 being hard, it was that the deadline was public for over a year and they still left it to the last month.
The part of this that doesn’t get said plainly enough
Here is the bit most explainers gloss over: GA4 was not built primarily to give small business owners cleaner reports. It was built because Google’s advertising business needed a way to keep predicting conversions and building audiences once two things happened, browsers started blocking third-party cookies and Apple’s App Tracking Transparency rules cut off a huge chunk of iOS measurement data. GA4’s “signals” and modelled conversion features exist to fill the gaps left behind, using statistical estimation to fill in cross-device and cross-platform behaviour that can no longer be directly observed. Google documents this openly, but it rarely gets mentioned in beginner-friendly explainers: a portion of what you’re looking at in GA4 conversion reports, particularly cross-device ones, is modelled, not measured.
That doesn’t make GA4 a bad tool, but it does mean the honest framing is that this transition served Google’s own advertising ecosystem and privacy compliance needs first, and small business reporting benefits second. Thousands of business owners spent twenty, thirty, forty hours relearning a reporting tool over the past few years for a change they had no say in and, for most day-to-day reporting needs, limited practical upside. That’s a fair thing to feel annoyed about, and I don’t think enough people running Analytics trainings say it out loud.
What the name change means for your reporting right now
If you’re still catching up, here is what matters at this stage, not the history, but the checklist:
- Confirm your property is a genuine GA4 property under Admin, not a leftover Universal Analytics view that’s simply stopped updating quietly in the background.
- Check your core conversion events are marked as conversions in GA4’s Admin settings, they don’t carry over automatically from old UA goals.
- Review your cookie consent banner and privacy policy wording, because GA4’s default behaviour around cookies and consent mode differs from the old setup, and it’s worth reading through how Google Analytics uses cookies and what it means for your privacy policy before an update catches you out.
- Get familiar with which parts of the GA4 toolset you’ll use day to day, since the interface bundles in features like Explorations and predictive audiences that most small businesses never touch, and it helps to know which Google Analytics tools are worth learning and which to ignore.
- If you or someone on your team is managing this for clients rather than one business, it’s worth checking which Google Analytics certification is worth the time before signing up for one that covers a version of the tool nobody uses anymore.
None of that takes more than a few hours if you sit down and do it one afternoon, which is roughly a tenth of the time most people waste dreading it.
Frequently asked questions
Is GA4 completely different from the old Google Analytics?
Yes, in the parts that matter most: it tracks individual events instead of sessions, requires you to manually mark conversions rather than inheriting old goals, and calculates metrics like bounce rate differently, so historical comparisons between the two systems are approximate at best.
When did Google Analytics officially become GA4?
Google launched GA4 publicly in October 2020 as a successor to a 2019 beta called App + Web, then forced full adoption by shutting down data collection in the old Universal Analytics on 1 July 2023 for standard accounts and 1 July 2024 for Analytics 360 enterprise accounts.
Can I still see my old Universal Analytics data?
Google kept Universal Analytics interfaces viewable for a period after the shutdown so businesses could export historical reports, but that window has closed for most accounts, which is why exporting your data as static files or spreadsheets before any Google deadline is worth doing on principle going forward.
Do I need to hire someone to set up GA4 ?
Not necessarily, the free setup guides Google provides cover the basics fine for a straightforward website, but if you run ecommerce, multiple conversion paths, or need Google Ads data to line up correctly with your analytics, a few hours with someone who has done the migration before will save you from months of quietly broken reporting.
