Ecommerce statistics - add abandoned cart metrics as plottable metric in the graph

matomo-org / matomo

Empowering People Ethically with the leading open source alternative to Google Analytics that gives you full control over your data. Matomo lets you easily collect data from websites & apps and visualise this data and extract insights. Privacy is built-in. Liberating Web Analytics. Star us on Github? +1. And we love Pull Requests!

https://matomo.org/

GNU General Public License v3.0

19.93k stars 2.66k forks source link

Ecommerce statistics - add abandoned cart metrics as plottable metric in the graph #21957

Open peterbo opened 9 months ago

peterbo commented 9 months ago

Ecommerce statistics - abandoned cart metrics are not plottable in the graph

Summary

All Ecommerce statistics should be plottable. When you click on the abandoned cart metrics, wrong graphs are shown in the diagram.

ecommerce-stats

Your Environment

Matomo Version:
PHP Version:
Server Operating System:
Additionally installed plugins:

michalkleiner commented 9 months ago

Thanks for the report @peterbo. I'm not sure if this should be a bug or an enhancement, there might be some historical reasons on why these aren't able to be plotted in the graph. I'll pass this to the product team for prioritisation where we can determine whether they should or shouldn't be and take it from there. Thanks!

peterbo commented 9 months ago

Hi @michalkleiner - I think there are two parts.

Clicking on abandoned cart metrics leads to displaying another (the wrong) graph in the diagram (BUG)
Abandoned cart metrics are not available to plot (Enhancement)

From an analyst persepective, abandoned cart statistics in an "over the period" graph would be very helpful, because reducing abandoned carts / re-engaging abandoned cart sessions are major KPIs, which you ideally want to see over time.

Stan-vw commented 8 months ago

I've created https://github.com/matomo-org/matomo/issues/22014 to split the bug and feature request part. I see how they might be the exact same (if indeed the feature never existed and will be implemented), but the "bug part" of the question might be "solved" by removing the buggy interaction rather than making it work (in case resourcing allocation doesn't allow for it)