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.92k stars 2.66k forks source link

Better ecommerce reporting in Piwik #6177

Open mattab opened 10 years ago

mattab commented 10 years ago

This issue is an open issue where we would like to brainstorm ways that Ecommerce reporting could be improved in Piwik.

Please suggest any suggestion or idea you may have as a comment here!

hpvd commented 9 years ago

some missing values for store performance overview are documented here: https://github.com/piwik/piwik/issues/7617

hpvd commented 9 years ago

does not solely fit to ecommerce, but of course it's very important for ecommerce is the topic costs, e.g. cost per revenue https://github.com/piwik/piwik/issues/4458

hpvd commented 9 years ago

summary taken fromcomments in #8758:

from professional POV to be honest, in the field of ecommerce at this time Piwik (2.1.5) is "only" "pretty fine". The ease of integration is of course perfect thanks to several plugins for several shop systems (https://piwik.org/integrate/#ecommerce-online-shops) but the number of data tracked and the possibilities to analyse them are not.

To make it "really good" some important points are missing: features not only for documenting the things you may receive also from your shop software, but features to give statistics which enable you to make good strategic decisions on it for the future direction and setup of your store. e.g.

To make it "damn awesome", in addition maybe even more unique features are needed to be apart from the competition e.g.

hpvd commented 9 years ago

the most important point is, to give the possibility to start tracking the needed data as soon as possible (#9176 #9177), the analysis can be added a little later.

The reasons for this:

hpvd commented 8 years ago

ecommerce: track more details of abandoned cart: extracted from: https://github.com/piwik/piwik/issues/9176

Piwik could track details of abandoned carts:

That's great. The results are showen e.g. in visitor log please see attachment.

The question for the shop owner is not only what he has lost but also even more important why did he lost this order?

To get a little help with the answer one need piwik to track some more data of the of abandoned carts:

Depending on the point of leaving the shop, the visitor may have seen and done (chosen) everything.

With this, these things should be also be tracked and be visible within piwik in same manner they are tracked on a successful order.

1) Details for each item on cart:

2) For cart in general:

even if some are not set (because not shown to visitor), one should still show the items but with the remark "not seen"

Only with this information one could identify the reason for leaving the shop

2015-11-06_14h55_21

would be really great to start tracking of all data soon (first step, because they are needed to have good statistics afterwards) Showing and using the data could be added a little later (second step, e.g. in visitorlog, a new abandoned cart overview page etc...)

hpvd commented 8 years ago

ecommerce: complete tracking of order's details extracted from #9177

Piwik is already tracking details of orders:

This is great so far but some important things are missing for making good decisions on base of Piwiks data for the right direction/future of business concepts and details (e.g. strategy of products, prices and discount, shipping, payment etc.)

Since there was just a ticket opened collecting all important data to be tracked on abandoned carts #9176, the same items are of course important for completed orders.

Here is the list:

1) Details for each item in order:

2) For order in general:

feel free to add some more!

tsteur commented 4 years ago

refs https://github.com/matomo-org/matomo/issues/11615