What is engagement rate in Google Analytics 4?
Paul Jarvis ·Engagement rate in Google Analytics 4 is the percentage of sessions that were “engaged”. GA4 counts a session as engaged if it lasts longer than 10 seconds, includes a key event, or has two or more pageviews.
If your site had 100 sessions last week and 62 of them met at least one of those rules, your engagement rate is 62%. GA4’s bounce rate is simply the other 38%.
That sounds tidy, but the 10-second rule does a lot of work, and it’s why engagement rate tends to look much healthier than the bounce rate you remember from Universal Analytics. Here’s how it’s calculated, where to find it, and how to read it without fooling yourself.
What counts as an engaged session in Google Analytics?
Google defines an engaged session as one that meets any one of these:
- It lasts longer than 10 seconds.
- It has at least one key event. Key events are what GA4 used to call conversions, such as a signup or a purchase.
- It has two or more pageviews (or screen views, in an app).
Only one of the three has to be true. Someone who lands on a blog post, reads it for 11 seconds and closes the tab counts as engaged.
The 10 seconds is a default. You can raise it, up to 60 seconds, in your web data stream’s tag settings, under the timer for engaged sessions. If 10 seconds feels generous for your site, that’s the setting to look at.
How Google Analytics calculates engagement rate
The formula is:
Engagement rate = (engaged sessions ÷ total sessions) × 100
And GA4’s bounce rate is the opposite:
Bounce rate = 100% − engagement rate
So if 1,500 of your 2,000 sessions were engaged, your engagement rate is 75% and your bounce rate is 25%. Every session is one or the other.
Engagement rate vs bounce rate
In Universal Analytics, bounce rate was the share of sessions with a single pageview and no other interaction. Someone who read one page for four minutes and left was a bounce.
In GA4, that same person is engaged, because they stayed longer than 10 seconds. GA4 still reports a bounce rate, but it’s just the sessions that weren’t engaged. That’s why a site’s GA4 bounce rate is usually much lower than its old UA bounce rate, even when nothing about the site changed. The two numbers measure different things, so don’t compare them.
We go into this in more detail in our article on what bounce rate is, including how Fathom measures it.
Other GA4 engagement metrics
| Metric | What it means |
|---|---|
| Engaged sessions | The number of sessions that met at least one of the three rules above. |
| Engaged sessions per user | Engaged sessions divided by active users over the date range. |
| Average engagement time | How long your site was the page in focus in the browser, on average. GA4 reports it per active user and per session. |
| Engagement rate | Engaged sessions as a percentage of all sessions. |
You’ll find most of these in the Engagement overview report in GA4.

What affects engagement rate?
Anything that changes whether people stay longer than 10 seconds, view a second page or complete a key event:
- Where the traffic comes from. Visitors from a newsletter you sent usually engage more than visitors from a social post they scrolled past. Compare sources before blaming the page.
- What the page is for. A help article can answer the question in eight seconds. That’s a non-engaged session, and a happy visitor.
- How your key events are set up. Mark more things as key events and more sessions count as engaged. The number goes up without anything real changing.
- Speed and layout. A slow page, or one that’s broken on a phone, loses people inside 10 seconds.
- Tracking problems. If the GA4 tag is missing from some pages, or fires twice, engagement rate is wrong in ways that look like real behaviour.
What is a good engagement rate?
For most websites, a GA4 engagement rate of around 50% to 55% is normal, and anything above 55% is on the strong side. That’s where the three studies we could find that say where their numbers come from all land:
| Study | Sites | Typical engagement rate |
|---|---|---|
| Siege Media, January 2024 to August 2026 | 546 GA4 properties, 16 billion sessions | 51% (median) |
| Databox, September 2024 | Not stated | 56.2% (median) |
| Orbit Media, early results | 65 client websites | 55% (average) |
A few caveats before you hold your site up against those. Most of the sites in these studies belong to an agency’s clients, so they lean towards businesses that pay for marketing. And a single average mixes blogs, shops, SaaS sites and everything in between, which is why none of them makes a good target.
The breakdowns are more useful than the headline number. Here’s how much the same metric moves in Siege Media’s data, depending on where visitors came from and what they were using:
| Where the session came from | Median engagement rate |
|---|---|
| Organic search | 63.4% |
| Paid search | 60.4% |
| Referral | 59.1% |
| 50.9% | |
| Organic social | 49.9% |
| Direct | 45.7% |
| Display ads | 31.9% |
| Paid social | 20.2% |
Desktop sessions came in at 55.3% and mobile at 48.8%. By industry, ecommerce sites had the highest median (54.4%) and SaaS and B2B software the lowest (46.6%). Databox’s industry figures run from about 53% (SaaS, IT and consulting) to about 62% (health and wellness, automotive).
So a blog that lives on Google search should expect well above 60%, and a site that buys a lot of social ads can sit at 35% and be perfectly healthy for its traffic. Compare your number with the row that looks like your traffic, not with the headline average.
When to look closer
Build your own baseline first. Note your engagement rate for each page type and each channel over three to six months. That tells you far more than someone else’s average. Then look closer when:
- Your site-wide rate drops below about 40%. Check the split by source before you touch any pages. Paid social, display ads or bot traffic will drag the number down before your content does.
- It’s above 90%. Real visitors rarely do that. It usually means the tag fires twice, or an event that fires on every page (like a page view or a scroll) is marked as a key event.
- It moves by 15 points or more from one month to the next and you didn’t change anything. Check your tracking and the property’s change history in Admin before you blame the page.
- One channel or device is far below the rest. That’s the traffic or the layout, not necessarily the content.
Ignore pages with fewer than about 100 sessions. A 100% engagement rate on six sessions doesn’t mean much.
How to improve your engagement rate
- Match the page to why people arrived. Look at the search terms or the ad that sends people to the page. If the page answers a different question, they’ll leave inside 10 seconds.
- Answer first, then give a next step. Put the answer at the top, then link to the obvious next page. A second pageview makes the session engaged, and it’s genuinely useful to the reader.
- Fix speed and the mobile layout. Mobile sessions engage less than desktop in Siege Media’s data, and a slow page loses people before GA4 has counted 10 seconds.
- Look at the traffic, not just the page. If paid social sits at 20%, the problem is more likely the audience or the ad than the copy.
- Don’t game it. Marking more events as key events pushes the number up without anything real changing. You’ll get a nicer chart and lose the signal.
Where to find engagement rate in Google Analytics 4
Most GA4 reports don’t show engagement rate by default, so you’ll usually need to add it. You need Editor or Administrator access to the property.
Step 1: Open a detail report
In Google Analytics, go to Reports in the left-hand menu, open the Engagement section and select Pages and screens. You can also use a traffic acquisition report if you want engagement rate by source.

Step 2: Click Customize report
Click the pencil icon (Customize report) in the top right corner of the report.

Step 3: Add the engagement rate metric
Under Report data, select Metrics.

Click Add metric, search for Engagement rate and add it. Add Bounce rate too if you want both. Then click Apply.

Step 4: Save the report
Click Save, then choose Save changes to current report or Save as a new report, and go back to the report.

Step 5: Read engagement rate per row
Scroll the table sideways and you’ll find the new Engagement rate column, shown as a percentage for each page or source.

How Fathom handles engagement
Fathom doesn’t have an engagement rate, on purpose. A metric that counts an 11-second visit as “engaged” needs a lot of explaining before anyone can act on it.
Instead, we show classic bounce rate (visitors who viewed one page and left), measured over a 24-hour window so someone who comes back after lunch isn’t counted as a bounce. We also measure time on site from departure pings, so a single-page visit still records how long someone actually stayed. Both sit in the totals at the top of the dashboard, and you can see them per page, per referrer or per UTM campaign.
Common questions
What’s the difference between UA and GA4 bounce rate?
According to Google, bounce rate in Universal Analytics was the “percentage of visits that did not interact with your site”, whereas bounce rate in Google Analytics 4 is the “percentage of sessions that were not engaged sessions.” A long single-page visit was a bounce in UA, and is engaged in GA4.
Why is my GA4 engagement rate so high?
Usually because of the 10-second rule: most visits that last longer than 10 seconds count as engaged, even if the person never scrolls or clicks. Too many key events, or a tag that fires twice, can push it up as well.
Can I change what counts as an engaged session?
Partly. You can raise the 10-second timer (up to 60 seconds) in your data stream’s tag settings, and you choose which events are key events. You can’t remove the two-pageview rule.
Is engagement rate the same as engagement time?
No. Engagement rate is a percentage of sessions. Engagement time is how long your site was in focus, in seconds or minutes.
See your visitors without the extra maths
If you’d like numbers that don’t need a glossary, start a free 7-day trial of Fathom Analytics. It takes a couple of minutes to add the script.
Or have a look around the live demo first.
BIO
Paul Jarvis, author + designer
