|
|
Engaged means “active or interacting with” — users that had some interaction with your site not limited to navigation. There’s a level deeper as well. You could have a user land on a site and immediately leave and a user that lands and just sits there. You can’t distinguish the two in UA even though it’s very different behavior. In GA4 you can. It’s the difference between a Session and an Engaged Session. we can measure when your site is in focus even if unengaged — so we do. So that’s really what makes recreating reports from UA hard.
In UA you have familiar constructs DB to Data may not be answering the questions you think they are. In GA4 you have new terms that mean what they say, but that are different from UA. If you are asking the same questions you did in UA, but GA4 has a better answer to give you, it will. Are there similarities/overlaps between UA and GA4 I can use to do this? RK: Yes, absolutely. GA4 can measure a lot more than UA could and can do it at scale – apps for example. But for the web, technologies may have evolved but we expect our customers to still have the same set of fundamental questions. That’s why we made sure to bring over all of the core reporting use cases from UA to GA4.
Ga4 Usecases 1 800x341 You can find more use cases here. GA4 takes many of the existing use cases and features Universal Analytics offered and either adds to them or distills them down to be simpler and more intuitive or customizable. Are there specific things in GA4 I should focus on to do this? RK: Yes! When you search GA4 for report names from UA, you’ll get pointers to the updated equivalents. Then, when you’re on a given report, but you get a different set of metrics or dimensions than you expected, look to customization – the pencil icon.
|
|
發表於 19:00:24