Bas on these events, GA4 will calculate the sessions in each report that you request. How does it do this? Each event has its associat user ID and session ID, and the only thing GA4 will do is count how many different session IDs it has in those events that appear in your data row.
Let’s go back to our example:
We want to see users who go through the homepage. You don’t ne a segment anymore. All you ne to do is go to the pageviews report and look at the sessions metric. Each row of data will have calculat how many unique sessions there are for each value. Isn’t that wonderful?
You can check what I’m telling you in a simple way:
Just go into GA4, look for any event or pageview report and add up the sessions you see in these reports. You will discover that, adding up all the skype database rows, there are many more sessions than the total number of sessions you have.
Why? Because for each row
The sessions have been calculat independently and that means that each session can be in different rows at the same time (for example, for a user who it accessibility in content creation ensures that has seen 3 URLs in less than 30 minutes, their session will be seen in the 3 different URLs. 3 sessions that add up to one).
And this effect of calculating sessions for each row doesn’t just happen for URLs
It happens for any GA4 event. All of them without exception and regardless of whether you request them in standard reports, explorations, API or Looker Studio. It means that you can sessionalize your purchases ( purchase event + session metric), internal searches ( search event + session metric) or your content groupings (the latter is great, as it allows tg data you to see at a macro level what is being queri).