If you spend time in Google Analytics you’ve probably visualized Google’s supportive little elicits exhorting you to upgrade to Google Analytics 4. Likewise, if you’ve set up a new asset recently, you might notice that Google seems to have removed Universal Analytics( don’t be alarmed, it’s only hidden away–here’s how to set it up ). You might be thinking,’ it’s an ameliorate so why wouldn’t I miss the latest and greatest? ’. Well, read on to learn how the programmes are different and what those gaps may mean for you.
What is Google Analytics 4( GA4 )?
The internet has changed significantly since 2005 when the first Google Analytics was launched. Back then, the iPhone was just a twinkle in Steve Jobs’ eye and websites looked like this. GA4 is Google’s response to cross-device usage and the impending death of cookies . It’s been redesigned from the ground up to better collect and predict data in a life with stricter privacy regulations. It too uses a new assessment pattern that can collect and integrate data from both your website and your app in one data stream.
Despite what the Google Analytics UI tells you, GA4 is not exactly an ameliorate from UA. It’s actually a new scaffold that runs alongside UA. Well … kind of. It used to be called’ App+ Web’ but beings weren’t squandering it, conceiving it didn’t apply to them unless they coped an app( guilty as charged ).
How does this help with a cookie-less future?
GA4 is built to use AI and data modelling to help fill the gaps in data caused by privacy regulations, which is becoming more and more important as major players like Apple limit the amount of data we’ll receive.
GA4 is also able to stitch data together across variou manoeuvres to better track consumers across telephones, tablets, TVs, and whatever else they use. This signifies customers are less likely to be double-counted, which will be supported more accurate data on which to base predictions.
How is GA4 different from Universal Analytics( GA3 )?
Here’s the quick and unclean lowdown 😛 TAGEND
Updated UI. It’s a bit more modern while grouping items differently. It’s designed to work even without cookies. Affair moving is a core part of the stage. Basic episodes are built-in. No more purposes. Instead, you celebrate contests as conversions. No more deems( for now ). No more return proportions. They’ve been replaced by’ engaged sessions’( discussions that lasted longer than 10 seconds, or had a conversion event, or had 2 or more screen or sheet beliefs) and involvement charge. Reporting is less of a focus. Google wants us to use GA for analysis and Data Studio for reporting. Data retention is 14 months( pro-tip: it’s set to 2 months by default. Change it to 14 months by going to Data Settings> Data Retention in the Admin tab ).
Event tracking is the foundation of GA4
If I had a dollar for every time I logged into a new GA account and received no event tracking set up, I would be sitting on a beach in Hawaii sipping a Pina Colada right now. If sizable transactions with plenty of available resources aren’t making all the benefits of Google Analytics, then what hope do tiny or midsized ventures have?
With this in mind, GA4 applies contests as the basis for data collection, with numerous set up by default. Now, everything is an event. A pageview? That’s an contest. A brand-new seminar? Event. GA4 transgresses occurrences down into four lists 😛 TAGEND Automatically accumulated
GA4 comes out of the box automatically rallying basic occurrences such as page_view, session_start, and move. If your GA4 is set up, you accumulate these events–no coding required.
Enhanced Measurement contests are also automatically obtained( if you don’t disable them) and may also collect specific parameters out of the box. One lesson is the file_download event which will likewise accumulate the file_extension, file_name, link_classes, link_domain, link_id, link_text, and link_url parameters.
These are events that are not automatically rallied but that are common across different industries and use specimen. Google has provided standardized refer and implementation. Some instances would be login, share, and purchase.
If none of the above happens work for your abuse contingency, you’ll want to set up a habit happen. Customers should know there’s a limit to the number of occasions you can collect( spoiler alarm: it’s 500 ), so choose wisely!
Google Analytics 4 will remove the need for things like manually adjusted bounce paces because the platform can better understand user behaviour without setting up anything custom.
Event are more flexible
Gone are the standard event action, list, description, and importance constants you used to add to each event in GA3. Now, phenomena are much more flexible, allowing you to add up to 25 constants to each event and to mention them however you like.
By standardizing episodes and ensuring the basic ones are collected by default, Google is able to better understand user behaviour across scaffolds. I’m speculating now, but I also suspect it helps improve machine learning beyond your belonging by arrange everyone on the same sheet events-wise.
Reporting in GA4
If you already do your reporting in Google Data Studio, this doesn’t affect you. But for those who don’t, you might feel a little bit lost at first-I sure did. Granular reporting in GA4 is not very straightforward. In fact, that’s by design. Google has said that their intent is for GA4 to be used for analysis and Google Data Studio to be the go-to for reporting.
This–combined with data retention for a maximum of 14 months–is one of the most important reason I will continue to use GA3 for reporting and analysis for the time being. When privacy principles start heavily restraint the data we see coming into Analytics, that’s when we’ll look to adopt GA4 and its machine learning sitting completed in the gaps.
So, should be used “upgrade” to GA4?
There’s no question that Google Analytics 4 is the future. It’s where Google will be focusing its efforts and where I expect we’ll exclusively ensure new and innovative aspects from here on out.
That said, it’s going to take a while for integratings to catch up, and for beings( and customs) to learn how to best use the new scaffold. Personally, GA4 still feels like it’s in Beta to me. For now, my recommendation would be to run both in latitude. Continue utilizing GA3 for everything( particularly for preserving historical data ), but start experimenting with GA4. Set it up now so you can start gathering data and configuring incidents, then compare it against GA3. That highway you’ll be ahead of the arc when it’s time to finally say goodbye to GA3.
You might also just wanted to ramp up on Google Data Studio if you haven’t once!
Read more: feedproxy.google.com