Someone visits your product page, scrolls through all the details, watches a demo video, then leaves without buying. Your pageview metrics show one page viewed. Your events per session shows six interactions: scroll, video play, and four clicks on different features. The first metric misses what actually happened. The second tells the real story.
Events per session is how GA4 measures engagement beyond just clicking to the next page. This article explains what it tracks, why it matters, and how to use it to understand visitor behavior.
What is an event in GA4?
An event is any user interaction tracked on your site. Pageviews, clicks, form submissions, video plays, downloads, scrolls, purchases. GA4 treats all of these as events.
Events per session is the average number of events fired during one browsing session. If your average is 5.2 events per session, visitors trigger about five interactions per visit.
This is different from pages per session which only counts page loads. Events per session captures everything a person does, not just what pages they view.
What types of events GA4 automatically tracks
GA4 automatically collects certain events without extra setup:
Page view. Every time a page loads, that is an event.
Session start. When a session begins, GA4 fires a session_start event.
Scroll. When someone reaches 90% down a page, scroll event fires.
User engagement. If a session lasts more than 10 seconds or has a page_view or conversion event, it is marked as engaged.
Click events. If Enhanced Measurement is enabled, clicks on links and buttons fire events.
What you can track as custom events
Beyond the automatically collected events, you can define any interaction as an event:
Button clicks specific to your site. Download button, comparison tool, calculator, etc.
Video engagement. Play, pause, completion of specific videos.
Form interactions. Form starts, field fills, form submissions.
Feature usage. Any in-page interaction that matters to your business.
The more you define as events, the more complete your picture of engagement becomes.
When high events per session is good
An e-commerce product page with 8 events per session is strong. Visitors are clicking features, reading specs, watching videos, comparing products. High event count means high engagement.
A calculator tool with 10 events per session is excellent. People are interacting deeply with the tool. That is exactly what you want.
A blog with 4 events per session is good if those events include scrolling and clicking to related articles. More events means more engagement.
When high events per session can be deceiving
A page with 15 events per session but 80% bounce rate means something is broken. People are clicking repeatedly trying to find something, or the page is buggy and firing duplicate events.
A form with 20 events per session but low completion rate means people are struggling. They are clicking multiple times, possibly deleting entries, starting over. That is frustration, not engagement.
High event counts can sometimes indicate confusion or problems, not engagement. Always pair event counts with conversion metrics and bounce rate.
How to use events per session to improve your site
Track which events are most common. If people click a help button frequently, your interface might be unclear. Add better instructions or improve the UI.
Track which pages have highest events per session. Those pages are engaging people. Understand why and apply the same principles to lower-engagement pages.
Compare events per session across traffic sources. Organic search might have 4 events per session while paid traffic has 2. That tells you paid traffic needs better message-match or landing page experience.
Define custom events for your business goals. If you own a SaaS tool, track feature usage. If you run a blog, track link clicks and time reading. Events per session becomes a proxy for whether people are getting value.
Frequently asked questions
What is a good events per session metric?
It depends on your site type. A blog should aim for 3 to 6 (page view, scroll, clicks). E-commerce should be 5 to 10 (browsing, comparisons, adding to cart). SaaS should be 8 or higher (feature usage). Calculate your own baseline and track trends over time. With WEMASY's website builder, you can set this up directly on your website.
Why is my events per session so low?
You might not have custom events defined. GA4 only automatically tracks a few events. Define custom events for interactions that matter to your business. Also, low events can mean people are not engaging. Check bounce rate and time on page. If those are low too, content or UX is the problem.
Can events per session be gamed?
Yes. If you trigger events on page load or for every scroll pixel, artificially high numbers result. Only track events that represent meaningful user choices or actions. Track events you actually care about, not just quantity.
Does GA4 count every click as an event?
Not by default. GA4 tracks page_view, session_start, and scroll with Enhanced Measurement on. For clicks, you need to enable Click events in Enhanced Measurement. Even then, it only tracks clicks on links and buttons, not every possible click.
How do I set up custom events for my site?
You can enable Enhanced Measurement for common interactions like clicks, scrolls, file downloads, video plays. For unique interactions specific to your business, use Google Tag Manager to create custom events. GTM lets you track any interaction you define.
Should I track every interaction as an event?
No. Track interactions that matter to your business goals. If a certain button matters, track it. If a 1% of people use a feature, you do not need to track every click. Be selective so your data stays meaningful and actionable.