How does scope affect the way data is stored? Listen. Truly promised, now comes the most important part of the post so pay attention and, if you need it, rest a little first. As I told you, Google Analytics collects raw data and then processes and synthesizes it . This raw data is made up of hits, events and pageviews that we send from our website. From those events or hits. Analytics has to build sessions. But you also have to synthesize and clean the data.Eiminate duplicates or non-relevant information, etc.
The cleaning
The cleaning and synthesis process is, broadly speaking, as follows . Google Analytics assigns a Client Id industry email list to each hit to identify unique users. Each hit is associated with the Client Id (through its cookie) that generates it. Some hits such as duplicates or hits that. Do not meet filters defined by the view configuration are discarded. All remaining hits are collected and ordered chronologically. Grouped by Client Id (per user). Analytics can then “understand” the sessions, based on the date and time of the hits (and other attributes such as the source).
The importan
The important thing about this is to understand that each hit comes with an associated user ID but not with a session ID, so the session itself is not part of the hits information but is deduced later. This means that the analytics scope works CL Lists unidirectionally . Users have sessions but sessions do not have users. Sessions have hits but hits do not have sessions associated with them. Hits can have products associated with them but products are not associated with hits. A detail that may seem very technical and not very relevant to you but, in the end, it is the reason for all the headaches.
