New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Average Pages per visit" metric under Visitors > Overview #14533
Comments
Yes please we too are looking for this feature. |
Agree! This is much needed. I'm using actions extensively on one site tracking outbound links etc. The metric "actions per visit" is not a very useful KPI in my case. "Pageviews per visit" is still a key indicator for user engagement - more valuable than "actions per visit". |
This issue has been mentioned on Matomo forums. There might be relevant details there: |
A serious missing data feature for a lot of my clients. One has just made massive changes to their navigation structure. Maybe it's better, maybe it is worse - without being able to see pages per visit we just can't tell :-( Actions is of no use to us in this case. |
Another custom inquiring about this metric today and how it would be useful for them. |
Another request today to see an AVG added for pageviews in the Visitors > Overview section |
Have had another customer looking for this particular metric today, also having this within Custom Reports would be handy. |
Have had another request to see this metric made available in Matomo |
Currently we report "Average actions per visit" in Visitors > Overview. Actions in this case also include downloads, outlinks, and internal site searches. (see Actions in Matomo FAQ)
It would be valuable to also report "Average pageviews per visit" because often users want just the number of pageviews per metric.
Maybe we could show both metrics in the same row eg.
3.9 actions (page views, downloads, outlinks and internal site searches) per visit, 3 pageviews per visit
(or could be on a new line).The Visitors Overview currently looks like:
The text was updated successfully, but these errors were encountered: