Ecommerce analytics improvements

[matt]

Placeholder for ideas of new features/improvements related to Ecommerce Analytics feature

• New reports: Days since last purchase for returning customers, Days since first visit for new customers SEE #2031
• Report: new visit VS returning visit VS returning customer

• API: Add Ecommerce metrics to Metadata API output (for Countries, Server time, Referrer, etc.)
• Add tracking of Profit revenue, either encrypted (see for example  yahoo doc), or not encrypted via the REST Tracking API

[matt]

Known limitations/features

• Tracking notes
  • If the cart is emptied, ie. call trackEcommerceCartUpdate() without calling addEcommerceItem() first, then the request will be ignored. This means, that someone emptying their cart will still appear as "abandoned cart". This very rarely would ever happen, and is useful safety guard against malformed requests
  • If visitor opens the Order confirmation page a second time, for example 1 hour later, the Order will not be tracked again (since trackEcommerceOrder(orderId, ....) has unique orderId used to dedupe). However, because of the way tracking works, the "visit" will be flagged as "ordered" but this will not count in the ecommerce reports. It simply affects the segment "visitEcommerceStatus" which will be set to "ordered" even though the order wasn't recorded.
  • When tracking product "views" using setEcommerceView(), if on a product page, the "category" third parameter is not specified, the "view" is not logged against "Product category not defined", the "category view" is not logged at all. One might expect it to be logged against the bucket "Product category not defined" (bucket used to record Product categories performance for orders/cart updates) but it doesn't for "views" metrics.
• Reporting UI: we process tax/shipping/discount/subtotal/revenue for each segment (country, referrer keyword, etc.) - should we display it in the UI or keep it for the API? If in the UI, must display it in some "advanced" ecommerce table view as it is too much data. Currently, we only display in ui the overall sum of tax/shipping/discount/etc

Other ideas:

• New metric in UI: Product pageviews (from Custom vars), % visits who view product page + sparkline?
• Best referrer, keyword (sorted by AOV desc)

[peterb]

I got a bit feedback on ecommerce analytics with a few proposals:

• add a possibility to log the payment type of a conversion
• add a field to record the payment type cost (e.g. creditcard payment, 10 cents plus 2.5 percent of transaction, etc.)

[matt]

Great suggestion in this forum post

• Piwik could provide ecommerce product recommendation system, based on ecommerce activity on the site. This is similar to other products that can use GA API to provide recommendations, such as:  http://www.liftsuggest.com/how-lift-product-recommendation-works For example, Piwik could provide "top sellers", "Best in Books", but also "You have seen this product, check out these other products"

[matt]

Moved to another ticket:

• Tracking: Given (idSite, orderId), enable update of previously recorded orders via the Tracking API (to correct previous orders that have been updated later on, or track orders in previous days) --- see #2584

[matt]

See also request  from forum

• Display top products report in the Ecommerce & Goals report directly, avoiding the click to ecommerce report

[Ravi Pathak]

Replying to matt:

Great suggestion in this forum post * Piwik could provide ecommerce product recommendation system, based on ecommerce activity on the site. This is similar to other products that can use GA API to provide recommendations, such as: www.liftsuggest.com/how-lift-product-recommendation-works For example, Piwik could provide "top sellers", "Best in Books", but also "You have seen this product, check out these other products"

Hello,

My name is Ravi Pathak and I am a cofounder of Tatvic. Liftsuggest is a product that we've developed based on Google Analytics. If there is anything that I can do to integrate Piwik API with Liftsuggest, I'd be more than happy.

Best, Ravi

[matt]

Ravi, thanks for posting here! Unfortunately, we don't have policy of integrating closed source third parties into Piwik, but thank you for the offer anyway. If you have in the future some open source code we could reuse, or if you would like to help us achieve good product recommendations and cross selling using Piwik datastore, it would be really great to have your help and advice!

[Ravi Pathak]

Replying to matt:

Ravi, thanks for posting here! Unfortunately, we don't have policy of integrating closed source third parties into Piwik, but thank you for the offer anyway. If you have in the future some open source code we could reuse, or if you would like to help us achieve good product recommendations and cross selling using Piwik datastore, it would be really great to have your help and advice!

Since Your platform is completely open source,I'd be willing to share some code algorithm & would love to provide help & advice, without any issue, related to our product recommendation engine. I can be reached at rp at liftsuggest dot com, when you take up this issue.

[mohelten]

Hi,

I miss the tracking of payment type after ordering. I could set a custom variable but I think that should be made by trackEcommerceOrder(). It would be great if this would be integrated in one of the next releases!

Best regards, Moritz

[mohelten]

Hi again,

it would be fantastic to include the delivery time of products in addEcommerceItem(), setEcommerceView() and even in setEcommerceView(). One could analyse if products how many products are viewed with a certain delivery time and how they convert in comparison to products with another delivery time.

Best regards, Moritz

[JulienM]

+1 for payment type, eg. credit card, paypal

also useful: shipping options, eg. express, 7 days, ..

[mohelten]

+1 for shipping options. Great idea!