In UA, page views referr to web pages visit by users. Screen views appli to mobile app screens. In addition, views includ a number of attributes (page_title; page_location, etc.) and although GA4 also retains these concepts as parameters of these events, the truth is that.
In GA4, it is possible to
Combine views as “view events.” This means that you can track both web pages and app screens under one umbrella. For example, measuring pageview and app screen opening in a single event.
That is to say, what is interesting here is the
Possibility (not the obligation) of cross-referencing this information, especially if we take into account that for many businesses the online experience cash app database of their users is multi-device.
Sessions.UA GA4
UA us the traditional session concept, where a session start when a user arriv at the site and end after a period of inactivity (30 minutes), when the browser was clos, or at midnight. In addition, if the campaign chang, the session also expir. Sessions includ page views, events, and other user interactions. Now, sessions in GA4 are calculat bas how to find a supplier for your online store on the difference between an event automatically trigger in the first interaction (session_start) and the last event that the user carries out. In this case, GA4 also generates a User ID that will be associat with each event of said session, which, on the other hand, does not expire even if the campaign changes.
User.UA GA4
With Universal Analytics, the information we knew about the user came from cookies. GA4 adds the User ID that we discuss in the Sessions, in addition to Google Signals (with which there began to be problems with the Threshold, one of the limits of GA4 but which has now been resolv).
6. Origin of traffic.
UA GA4
In Universal Analytics we could see the usa data origin of visits through dimensions such as campaign, source or mium. In GA4 this information can be seen in 3 different areas, that is, through.