Everyone in the digital world does it. Jokes aside, we call sessionizing the process of bringing data into the session environment. Basically, it involves duplicating the data we have so that only one is count per session.
For example: You may have 500 page views of
A URL, but some of them will be from the same user in the same session. What we do when we “sessionize” is try sessions view that page at least once. This way we will discover, for example, that our homepage in some businesses is view in the same session several times and there are not many fewer sessions than page view events (“views” as GA4 calls them).
In many tools including the old GAU
To sessionize something we were forc to go to the segments. For our homepage example we would have to create a segment of “sessions that office 365 database go through the homepage” to get that data. When we want another page, we would create another segment and so on until we di of borom.
In GA4, to see data for any event at session level
It is enough to request that dimension and associate the “Sessions” metric in the report. The data we will see will be the unique sessions that have that undergoes various stages from inception to retirement data at least once. Isn’t that wonderful?
Why does this happen?
Because, even though GA4 has cut back on the less relevant calculat metrics, sessions (and many other values) have been transform into metrics calculat on the fly. How does it work? Well, when you request a report from GA4, what you get in the first instance are events (Remember: GA4 is bas on events). You can filter these events tg data or not (I only want page_view, I only want purchase) and you can get some dimensions or others from them, but in the end they will be that: Events.