Unlike traditional UA, the basic concept of GA4 is to measure on an event-by-event basis. This means that events are collected when a user actually does something, as opposed to the traditional method of sending information when a page has finished loading. With traditional UA, events could be collected by embedding tracking code directly into the web page. However, GA4 recommends the use of a tag manager, which requires setting up a tag manager, tags, variables, and triggers. You will need to set it up to track when certain actions occur, such as button clicks, page scrolling, form submissions, etc. Tag managers require more complex configuration than traditional UA because they generate code to automatically track events. Event-by-event tracking allows for more detailed analysis, but may be a bit esoteric for those setting up GA for the first time. events are central to GA4 and allow for more detailed data to be collected, but if events are not designed correctly, it will be impossible to collect important data with GA4 We recommend that you consult with an expert who has a proper understanding of how tag managers and GA4 work and function.

Unlike UA, GA4 recommends setting a user ID. By setting a user ID, the behavior of a logged-in user can be tracked, and even if the same user accesses the site on multiple devices, the user can be determined as a single user. However, setting user IDs is a bit more complicated than traditional UA and requires proper configuration.

Unlike traditional UA, GA4 recommends setting up specific custom events. Setting up custom events allows for analysis related to specific actions or objectives of the website. In a traditional UA, three fields could be used to track events: “Category”, “Action”, and “Label”. However, in GA4, three additional fields have been added: “Value,” “Non-interactive,” and “Conversion. This allows for more granular settings for tracking events and more information to be captured. However, it also means that the settings are more complex.