@mattab opened this Issue on April 13th 2017 Member

As part of Ecommerce Analytics, we would like the ability to keep track of which orders were refunded and cancelled. The Tracking API should allow us to record which orders were refunded and/or cancelled. The reporting would then be updated to also report refunds and cancels, and remove the revenue amount from the Net Revenue over the period.

@marrahi commented on May 5th 2017

if i send order in negative value???


this code add value in ecommerce analytics??

@tsteur commented on March 13th 2019 Member

Also we want to handle:

  • Subscriptions
  • Churn
  • Recurring revenue
  • Forecast revenue
  • etc.
@tsteur commented on June 1st 2019 Member

Maybe also something to look into : https://github.com/matomo-org/matomo/issues/11562 carts across visits

@tsteur commented on January 8th 2020 Member

After some long consideration I figured it may not be worth it implementing subscription support right now and instead created this issue https://github.com/matomo-org/matomo/issues/15361 . A workaround is available using events and it might be better to simply write a blog on how to do this. I'm writing a guide about this

@tsteur commented on January 8th 2020 Member

@mattab I wonder how important tracking refunds (and cancellations) really are? Doesn't seem maybe too important? Eg not seeing many comments here or users asking for it. Also thinking we could introduce this feature later in a minor Matomo 4 update if needed since we mainly would need to introduce new idGoals like idGoal -2 === refund . Could move it back to priority backlog maybe?

@mfkp commented on June 23rd 2020

Just wanted to chime in that I would appreciate refund support. My main use-case is appointment bookings. If an appointment is cancelled, it would be nice to track the "refund".

@sreckins commented on September 17th 2020

I also just want to say that these features would be very helpful for me!
More detailed Abandoned Cart and Refund Information in particular.

But this seems to be low priority since Ticket #9176 was closed and not followed up for almost half a decade :(

Powered by GitHub Issue Mirror