Google Analytics 4 destination
Google introduced the new version of Google Analytics, called Google Analytics 4 (GA4), in October 2020. GA4 has some distinct differences from Universal Analytics (UA), which are important to understand before considering migration and the data schema changes that might require.
Segment’s GA4 destination is in beta, with an expectation to release to general availability in early 2021. If you are interested in being a beta tester, please complete this short questionnaire and someone will be in touch with next steps.
We’ll update this page to share the latest on our GA4 destination.
Event-based data model vs pageview-based data model
GA4 has an event-based data model, like Segment. It is replacing Universal Analytics (UA), which has a pageview-centric data model. For more details, see Google’s help center article: Universal Analytics versus Google Analytics 4 data.
Because the data models are different, data cannot be migrated from Universal Analytics to GA4. Google recommends you rethink your data collection in terms of the new model, rather than port everything over from UA. If you’re using UA for ecommerce, see Google’s best practices guide for setting up ecommerce tracking in GA4: Migrate ecommerce data collection from Universal Analytics; note this is not a simple migration.
Support for web and mobile data streams
UA’s pageview-based data model made it great for websites, but not wonderful for mobile apps, which might load content dynamically, without having “pages” the way UA defined them. GA4 has an event-based data model which improves upon this, and can serve as a single reporting destination for both your web and mobile sources. This means you can compare data across devices.
If you decide to use GA4 so you can compare the data, you should spend some time thinking about how to set it up. To compare data across devices, you must use the same parameters across all data streams when you create your custom events.
GA4’s out-of-the-box reports are different from UA’s. GA4’s reporting is much more configurable, and supports new reporting metrics like churn probability and predictive revenue estimates.
You might not be able to perfectly recreate your UA reports in GA4. One approach is to send your data to both UA and G4A while you build out your new reports in G4A, and improve those reports over time. Once you are satisfied that your G4A reports meet your needs, you can gradually migrate away from using the original reporting in UA.
Client-based or server-based
GA4 is only available using a device-mode (client-based) SDK such as
gtag.js, Firebase, and Google Tag Manager. The Measurement Protocol that enables server-to-server data syncing for GA4 properties is currently in alpha.
Segment plans to support Device Mode and Cloud Mode for GA4. Availability will depend on the Google Analytics roadmap and our assessment of the stability of these APIs.
Switching to GA4
Universal Analytics replaced Google Analytics in 2012; there is precedent for Google slowly replacing the previous generation of Google Analytics with something new. You do not need to switch to GA4 right now. Ultimately, when and how you migrate to GA4 is up to you and your team.
While Google indicates that GA4 is the future (it’s the new default property type when you create a new Google Analytics account), Universal Analytics doesn’t appear to be going anywhere. You can still choose to create a new Universal Analytics property when you create your new GA4 property.
This page was last modified: 13 Jan 2021
Questions? Problems? Need more info? Contact us, and we can help!