Skip to content
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

Better ecommerce reporting in Piwik #6177

Open
mattab opened this issue Sep 9, 2014 · 7 comments
Open

Better ecommerce reporting in Piwik #6177

mattab opened this issue Sep 9, 2014 · 7 comments
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.

Comments

@mattab
Copy link
Member

mattab commented Sep 9, 2014

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!

@mattab mattab added the Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. label Sep 9, 2014
@mattab mattab added this to the Long term milestone Sep 9, 2014
@hpvd
Copy link

hpvd commented Apr 1, 2015

some missing values for store performance overview are documented here: #7617

@hpvd
Copy link

hpvd commented Apr 1, 2015

does not solely fit to ecommerce, but of course it's very important for ecommerce is the topic costs, e.g. cost per revenue
#4458

@hpvd
Copy link

hpvd commented Nov 7, 2015

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
Copy link

hpvd commented Nov 7, 2015

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:

  • every analysis need data which has to be tracked before (the more the better for your statistic)
  • the integration of the possibilities of additional data tracking in the plugins, available for several shops (see https://piwik.org/integrate/#ecommerce-online-shops), would take some time too.
    So Piwik has to implement this as soon as possible.

@mattab mattab modified the milestones: Mid term, Long term Dec 23, 2015
@mattab mattab added Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. and removed Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. labels Dec 23, 2015
@hpvd
Copy link

hpvd commented Jan 5, 2016

ecommerce: track more details of abandoned cart:
extracted from: #9176

Piwik could track details of abandoned carts:

  • items
  • quantity
  • price

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:

  • Name
  • SKU
  • Original Price
  • Price (on cart, after discount)
  • Quantity

2) For cart in general:

  • ShownTotal Revenue
  • Shown Tax amount
  • Selected Payment method
  • Shown payment cost
  • Selected Shipping type
  • Shown Shipping Cost
  • Discount offered
  • Discount reason e.g. coupon

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
Copy link

hpvd commented Jan 5, 2016

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

Piwik is already tracking details of orders:

  • Order Revenue grand total (includes tax, shipping, and subtracted discount)
  • Order sub total (excludes shipping)
  • Tax amount
  • Shipping amount
  • Discount offered

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:

  • Name
  • SKU
  • Original Price
  • Price (on cart, after discount)
  • Quantity

2) For order in general:

feel free to add some more!

@tsteur
Copy link
Member

tsteur commented Feb 11, 2020

refs #11615

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

3 participants