How to implement the new Google Analytics 4?
Posted: Wed Jan 29, 2025 10:06 am
The future of GA3
AJ: You've already partially answered this question, but I'd like to make it clear. If I've already implemented GA 4 (I've managed to agree on all the departments and everything you've mentioned), should I disable the old version, suspend it, or do anything else with it?
MM: No, I don't think so. At this point, it's recommended to track both versions. First, because not all of the Universal Analytics stuff is available in GA 4 yet, even something as simple as conversion rate , which is dividing the number of events by the number of users. So even something as simple as that isn't there yet. Plus the whole GA 4 setup.
AJ: What does it take to implement Google Analytics 4 if it's more than just uploading code cambodia rcs data and measuring a few events?
MM: Yes, that's the first thing we need to do. And then we need to go through the whole configuration process. First, custom events, meaning sending all the events, all the parameters. Because we also have one option - a new but well-known word that's in Google Analytics - conversion. Because up until now we had goals, but we didn't really have conversions in Google Analytics, in a word that's very well-known, for example from Google Ads.
At this point, from all the events, we can choose conversion, or the main event – what is our main goal on the page. In most cases, this will be a purchase and we should mark this event as the main goal of the page.
Then we should do all the configuration. A bit of technical stuff, for example excluding referring domains that we had in the old version – all payment gateways, email addresses – so that they don’t disturb our analysis of the actual source of entry, so that it doesn’t turn out that it’s best to invest in advertising on PayU and Przelewy 24.
AJ: You've already partially answered this question, but I'd like to make it clear. If I've already implemented GA 4 (I've managed to agree on all the departments and everything you've mentioned), should I disable the old version, suspend it, or do anything else with it?
MM: No, I don't think so. At this point, it's recommended to track both versions. First, because not all of the Universal Analytics stuff is available in GA 4 yet, even something as simple as conversion rate , which is dividing the number of events by the number of users. So even something as simple as that isn't there yet. Plus the whole GA 4 setup.
AJ: What does it take to implement Google Analytics 4 if it's more than just uploading code cambodia rcs data and measuring a few events?
MM: Yes, that's the first thing we need to do. And then we need to go through the whole configuration process. First, custom events, meaning sending all the events, all the parameters. Because we also have one option - a new but well-known word that's in Google Analytics - conversion. Because up until now we had goals, but we didn't really have conversions in Google Analytics, in a word that's very well-known, for example from Google Ads.
At this point, from all the events, we can choose conversion, or the main event – what is our main goal on the page. In most cases, this will be a purchase and we should mark this event as the main goal of the page.
Then we should do all the configuration. A bit of technical stuff, for example excluding referring domains that we had in the old version – all payment gateways, email addresses – so that they don’t disturb our analysis of the actual source of entry, so that it doesn’t turn out that it’s best to invest in advertising on PayU and Przelewy 24.