Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Google recently announced that the current Google Analytics 3 (Universal Analytics) will come to an end in July 2023 (now extended until October 2023) and they’ve encouraged all current users to start using the new GA4. Google Analytics 4 is the new version of the current GA reporting portal that current users have used to analyse the performance of their sites.
When will Google Analytics 3 stop working?
When the launch of GA4 was made public in October 2020, Google gave all current users enough time to migrate their current use of GA3 to the newer and better GA4 until July 2023 which is plenty of time for both small and large corporations to switch.
The question is now, however, should you switch Universal Analytics off and switch immediately to GA4 or should you wait? The best thing to do is to use both simultaneously first to make sure the new Google Analytics has all the relevant reports in place otherwise you will miss out on this data. Although there are many new features on the new Google Analytics 4 version it might need some time for you to have all your reports set up.
Do I need to use Google Analytics 4?
The short answer would be yes! If you want to get the most out of Google Analytics and use the same reports as you have been using, you must update to GA4. If you don’t, by the time GA3 stops working in October 2023, you and your business will be left high and dry without the tracking and reports you need to monitor your website performance. The result? This could cause endless issues for your internal teams that rely on this data for both strategy and sales, which in turn helps to deploy improvements and adjustments to your business.
What’s the difference between GA3 and GA4?
Good question. Firstly, one of the fundamental differences is the UI. When you first see the reporting UI for GA4 you might be very surprised to see it differs greatly from what you’re used to in GA3.
View functionality will also be altered with only one view with GA4 for your reports which differs quite significantly from the 25 offered currently by GA3. The reason for this? For a cleaner, easier viewpoint that shows you everything you need to report on in one place. You can still filter your view however, by “data streams”.
Probably the biggest, and more shocking differences of all, is how GA4 measures activity on your website. For example, GA3 uses timed sessions whilst GA4 doesn’t use time as a measurement for a said session. Surprised yet? Wait until you hear this one…
Forget about the bounce rate. Yep, I said it. Bounce rate is going in GA4 and instead you’ll see “engagement rate”. Unlike bounce rates, engagement rates take into consideration the time taken on the landing page, which could give you an even better understanding of your visitors’ interaction with your website.
These are just the basics. Stay tuned for our comprehensive changes to GA3 and GA4 coming soon!
StatusCake Team
Share this
More from StatusCake
Engineering
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026