Your analytics shows an average session duration of 45 seconds. You assume most people are barely skimming. Then you realize: half of them probably opened your page in a background tab while checking email, left the tab open for an hour, and never looked back. That hour does not count as session duration. Only the active engagement time does.
This shift from session duration to engagement time changed how we measure whether people actually interact with your content. This article explains the difference, what changed in GA4, and what the numbers really mean.
What is session duration?
Session duration is the total amount of time someone spent on your site during one browsing session. They land, browse, and when they leave or go inactive for 30 minutes, that session ends. The time from start to finish is the session duration.
Simple enough. Except it has a major flaw that Google finally fixed.
The old way counted total time, even when your page was sitting in a background tab. Someone opens your article in a tab, switches to Facebook, comes back two hours later and closes the tab. The old analytics counted all two hours as session duration. Obviously wrong. That person was not on your site. They were elsewhere.
Why Google switched to average engagement time
GA4 introduced "average engagement time per session" to fix this. It only counts the time a user was actively engaged with your page. Your site has focus, the user is not switching tabs or windows, they are actually reading or interacting.
This is more accurate. Someone who reads your article for eight minutes straight matters more than someone whose page sat open for an hour while they were doing something else.
The shift means lower numbers than before. Your average session duration might drop from 3 minutes to 2 minutes when you switch to GA4. That does not mean your content got worse. It means your metrics became more honest.
How to understand what engagement time actually means
Average engagement time is the average length of sessions where people were actually focused on your page. If your average engagement time is two minutes, that means on average people actively spend two minutes on your site per session.
That is much more useful than "session duration" which might include idle time. Two minutes of actual engagement is serious. That person read, clicked, maybe scrolled. They paid attention.
Compare engagement time to number of pages per session to get the full picture. If engagement time is high but pages per session is low, people are spending a long time on fewer pages. If engagement time is low but pages per session is high, people are moving through pages quickly. Neither is inherently bad, but they tell different stories.
What counts as engagement in GA4
In GA4, a session is considered engaged if any of these happen:
The user stays for more than 10 seconds. They view more than one page. They generate a conversion event (form submission, purchase, video play, anything you define as valuable).
The 10-second threshold is important. Stay on a page for 11 seconds and it counts as engaged, even if you do not click anything. This is different from older analytics that required an action.
Session duration benchmarks for your industry
A good average engagement time varies by industry and content type. A news article might have 90 seconds. A product page might have three minutes. A checkout page might have five minutes.
The important benchmark is your own site over time. Is engagement time climbing or falling? Are you keeping people longer than last quarter? That tells you whether your content quality is improving.
Comparing your engagement time to a competitor's is less useful because you do not know their actual traffic quality, their content type mix, or whether their numbers come from GA4 or old analytics.
Frequently asked questions
Does leaving a page open in a background tab count toward session duration?
No, not in GA4. GA4 only counts active engagement time. If your site is open but you are focused on a different tab, the clock is not running. This is why GA4 numbers are often lower than Universal Analytics numbers for the same traffic. With WEMASY's website builder, you can set this up directly on your website.
What is a good average engagement time for a blog?
Aim for 90 seconds to three minutes depending on article length. A 500-word article should have lower engagement time than a 2,000-word guide. Do not compare across different content types.
Why is my engagement time so low if people are scrolling?
Scrolling alone does not extend engagement time much. People can scroll quickly through a page in 30 seconds. Engagement time counts minutes of active attention. Scrolling counts, but fast scrolling does not add much time.
Does GA4 count time differently than Universal Analytics?
Yes, significantly. Universal Analytics counted all time a page was open. GA4 only counts time the site is in focus. GA4 numbers will be 20 to 40 percent lower for the same traffic. This is not a problem with your data, it is a more accurate measurement.
Can I set a custom engagement time threshold in GA4?
Yes. The default is 10 seconds, but you can customize it. However, changing it makes it hard to compare to industry benchmarks and previous years. Keep the default unless you have a specific reason to change it.
How do I improve average engagement time?
Improve content quality and formatting. Longer engagement time comes from pages that are worth reading and easy to scan. Use headers, short paragraphs, visuals, and clear next steps. Fast-loading pages also help because slow loading frustrates people and makes them leave.