Skip to content

Commit 7bdb18c

Browse files
Merge pull request #783 from plausible/cms/blog/2024-12-06-everything-that’s-complicated-to-do-in-google-analytics-than-plausible
Automatically generated. Merged on Netlify CMS.
2 parents 5cf1e9d + 869e408 commit 7bdb18c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2024-12-06-everything-that’s-complicated-to-do-in-google-analytics-than-plausible.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ But if you want to know where these insights are typically housed (based on the
6464

6565
**Bounce Rate**: Bounce rate is also available as a metric which needs to be manually added to any of the reports you are viewing. It is not available by default and there’s no one-stop place to view it.
6666

67-
**Time on Page**: This is not available. But you can find the Average Engagement Time per User and Average Engagement Time per Session metrics to be added to any report. You may also find these in the Engagement Overview report.
67+
**Time on Page**: "Time on page" was sunset after UA but you can find the Average Engagement Time per User and Average Engagement Time per Session metrics to be added to any report. You may also find these in the Engagement Overview report. But [we found them](https://plausible.io/blog/time-on-page-ga-vs-plausible) to be underreporting by as much as 80% as compared to Plausible's Time on page.
6868

6969
P.S. While editing any standard report to add such metrics, don’t forget to “Save” them. It will avoid the trouble of adding the metric again and again.
7070

0 commit comments

Comments
 (0)