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

show detailed cart history with items added/removed not an aggregated view of it #3160

Open
anonymous-matomo-user opened this issue May 31, 2012 · 4 comments
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.

Comments

@anonymous-matomo-user
Copy link

As noted in #2528 the visitor log only shows the current (aggregated) state of a cart in Piwik 1.7.1. Even like the reporter of #2528 I thought after reading:

--- from doc doTrackEcommerceCartUpdate ---
On every Cart update, you must call addEcommerceItem() for each item (product) in the cart, including the items that haven't been updated since the last cart update. Items which were in the previous cart and are not sent in later Cart updates will be deleted from the cart (in the database).
--- from doc doTrackEcommerceCartUpdate ---

I could see which items are added or removed from a cart similar to the log that show each visited page. Just show each cart change as an extra log entry timely fitted in the page log with the information what items are added, what items are removed and which items has a changed quantity. As far as I can see the information much of the information is already contained in the database so this is maybe only some other way to show the cart updates. The only missing information is when a quantity changed.

I will create a screenshot what I think is a better way to show the cart updates.
Keywords: ecommerce, addEcommerceItem

@anonymous-matomo-user
Copy link
Author

Attachment: An example of a better way to show cart history.
piwik.png

@mattab
Copy link
Member

mattab commented Jun 1, 2012

Thanks for the proposal. unfortuantely we don't have the data available, we only know the latest status of the cart. We would know the deleted items however, so we could display that somehow, but let's create a different ticket if needed.

Wont fix because of implementation / lack of data

@anonymous-matomo-user
Copy link
Author

I don't understand why a feature request is closed with "wontfix"?

I could understand a "wontfix" if the request goes far away from the project goals or the request is simply not possible to implement. But I can't imagine why a cart history is impossible to implement. I even could understand if someone sayes: "Hmm, this is not a priority we set the milstone to version 99.".

Surely today piwik misses some data but that's the reason I choose "feature request". It should be even possible to gether the required information without any API change or some codes changes in the store code that uses the ecommerce api. You can alway compare the old cart with the new one and create all required information.

I think it would be nice to enhance piwik to show a much more detailed view what's happening in a store than today.

@mattab
Copy link
Member

mattab commented Jun 1, 2012

Sure we might end up implementing it (we sometimes reopen tickets ;)) but OK to leave it open, as indeed it might be something more users will request

@anonymous-matomo-user anonymous-matomo-user added this to the Future releases milestone Jul 8, 2014
@mattab mattab modified the milestones: Long term, Mid term Dec 23, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
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

2 participants