-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Ecommerce Tracker API: allow to update, or cancel, any order given its Order ID #10893
Comments
@S1awa in the visitor log for this day, do you still see the "cancelled order" or do you just see the new "order with revenue 0" ? |
@mattab I still see the original order and the log from when the API cancel command was called, but it is kind of incomplete. |
Actually we wont be working on this one at this point |
Renamed issue title to also include in the scope the "Update order" feature. |
fyi: When tracking an order that has the same OrderID Matomo gives the following error: |
I would also like to give a shout that "update e-commerce order" would be a very useful feature. |
i've exactly the same error too:
|
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/duplicate-tracking-of-ecommerce-orders/31789/5 |
I have exactly the same problem. Is there any workaround or do I have to live with wrong ecommerce data in matomo when an order was refunded? |
Related issue: #5292
I am trying to remove a canceled order with the Tracking API:
http://developer.piwik.org/api-reference/tracking-api
Here is how the call looks like:
https://mypiwik.com/piwik.php?idsite=7&rec=1&url=https%3A%2F%2Fmysite.com&apiv=1&idgoal=0&ec_id=1611210002&revenue=0&ec_st=0&ec_tx=0&ec_sh=0&ec_dt=0&token_auth=xxxxxxx
It appears in piwik
But even after I invalidate and re-process the past reports (http://piwik.org/faq/how-to/#faq_155) the statistics show revenue for the original order.
![stats](https://cloud.githubusercontent.com/assets/20663500/20509159/b8dc8b7c-b0a1-11e6-8b4b-226e915259f3.png)
Am I missing something?
The text was updated successfully, but these errors were encountered: