Skip to main content

Blog

Google Analytics 4

Mark Rochefort14 October 20202 min read

The new future version of Google Analytics has been announced - now branded as Google Analytics 4. Building on the "App + Web" property that was released last year, this sets the direction for Google Analytics going forwards. It is now the default experiences for all new properties and is where all product developments will be focussed.

Google Analytics 3, commonly known as Universal Analytics, was released in October 2012. This next product iteration for Google Analytics is a major step on from that - and has re-built the entire approach to implementation, reporting and analysis.

Bringing together insights across platforms and devices, at its heart are powerful machine-learning models, enabling predictions for things like churn rates and revenue. Such modelling will also be used to fill the gaps in data, caused by opt-outs and cookie blocks for example, in specific sets of data. Indeed, features such as "consent-mode" and "data deletion" directly address the need to provide a customer with greater control of their analytics data collection and management.

While Google Analytics 4 is a new version, the underlying paradigm has actually been around a while - and it is something we are very familiar with. Both in the App + Web property released last year and, since before that, when it was powering the analytics within Firebase (Google's mobile application framework). So, if you have seen Firebase or App + Web, you are likely to recognise the direction this is headed.

This is where Google are investing any future product improvements. Game changing features such as BigQuery export (something that was previously a Google Analytics 360 - i.e. enterprise - feature only), e-commerce reporting, Data Studio connectors and much more are rolling out as we speak! Google Analytics 3 will not be developed much further - to gain from any of these new features you should be looking to make the switch to Google Analytics 4. At the moment, we suggest this is done in parallel to your existing setup so you can reasonably compare and contrast between the versions.

Speak to one of our experts to find out more about how we can help you with this transition.

Need to connect your data?

Join marketing, customer and product data with tested models and documentation your team can use. Start with the sources needed for your question.

Have a question or project in mind?

Bring data to connect, a question to investigate or something to fix or build. We can agree a focused scope directly.

Suggested content

Blog

How to make an AI agent accurate in BigQuery

A year ago, I wrote about getting a BigQuery warehouse ready for AI ( Easy ways to prepare your BigQuery warehouse for AI) , but didn't look properly into Knowledge Catalog (known as Dataplex at the time). We decided to go back and look through Google's Knowledge Catalog properly: what's actually in there, how it works and what it relates to. What Knowledge Catalog is Knowledge Catalog is Google's metadata layer for BigQuery data (and a few other sources). It sits alongside your tables rather

Katie Kaczmarek15 Sept 2026

Blog

What's actually in Google's Knowledge Catalog

Google's Knowledge Catalog has been renamed four times. Data Catalog, then Dataplex Catalog, then BigQuery universal catalog, then Dataplex Universal Catalog, and now Knowledge Catalog, as of 10 April 2026. The API, gcloud and IAM roles still all say "dataplex". If you land on a page that mentions Dataplex and wonder whether you're reading something out of date, you're probably not. That's just the product's fifth name in four years. I spent some time looking through the different sections of K

Katie Kaczmarek15 Sept 2026

Blog

BigQuery Tips: When your query is technically correct but BigQuery won't run it

There is a particular kind of frustration that comes from staring at a query you know is correct and watching it fail. No syntax error. No logic problem. Just a wall. We hit two of them on the same project. What we were building The job was to migrate ga4_daily_snapshot for a large enterprise client from a BigQuery scheduled query into a proper Dataform pipeline. The scheduled query had been added to over time until it was too large to maintain with any confidence. Moving it to Dataform w

Katie Kaczmarek17 Aug 2026