There will be no more categories or actions. So the old implementation nes to undergo a major overhaul. It is therefore worth reviewing the lists of available parameters and considering your own nes to plan the network of information sent to the new service. For eample, tracking video on a wsite with UA requires implementing events via GTM . GA in its advanc tracking options has a built-in video module by default. Another eample is tracking the correct completion of forms on the wsite – in the case of UA, we had options with classic forms with a separate thank you for subpage, we set the goal of visiting this subpage.

An The Company’s Attorneys in Fact

The matter was complicat if our thanks appear in the form of a pop-up. In this case, it was necessary to act in GTM and, bas on changes in the Morocco Mobile Number List DOM, set the appropriate rule that sent the event to Google Analytics. In GA , it is enough to add the generatelead event to which we simply assign the appropriate value. Session counting differs slightly between the two services. In the case of UA, a new campaign automatically starts a new session, which is not present in GA . This means that the number of report sessions in the new service will be smaller.

The Specific Interest Of The Group Of Companies

In addition, where UA has a -hour window for counting sessions, GA analyzes them for hours. All for a more accurate attribution. The user’s active time in GA is count on a regular basis between successive events. This means that the new service will USB Directory report more active users and the bounce rate will be lower than in the case of Universal Analytics. To sum up, the correct implementation of the event network is etremely important for the proper functioning of Google Analytics . Therefore, Google recommends that the migration process assumes the creation of both simultaneous services.