Hi @Johannes_Boppre
Yes…And no!
In the MTM tag, you can call _paq code, but in the HTML, I advise you to use only _mtm
… As today e-commerce tracking does not exist in MTM, you can integrate the e-commerce tracking in JavaScript MTM tag…
Please note that there is a feature request in a ticket for the e-commerce integration in MTM (and an example of e-commerce code):
opened 07:35PM - 09 Oct 23 UTC
I noticed that the Tag Manager does not support Ecommerce tracking yet.
When … looking at the [JavaScript Tracker](https://developer.matomo.org/api-reference/tracking-javascript), there are 3 main `track` functionalities regarding Ecommerce:
1. Tracking a product/category page view (using `setEcommerceView`)
2. Tracking a cart update
3. Tracking an order
The other functions (`addEcommerceItem`, `removeEcommerceItem`, `clearEcommerceCart`, `getEcommerceItems`) are used for managing the *cart*.
Adding "product/category page view" was rather simple (#699).
On the other hand, tracking a cart update or an order is much harder since these two calls require knowledge of the *cart*.
From my understanding, in many shop systems, the *cart* content is stored server side, and only a *cart identifier* is stored client side. As for orders, they are also processed server side... I'm not yet sure how to deal with this.
An initial idea was something like a *cart* tag that when triggered modifes something like a *cart* variable (which stores data by using the local storage of the browser). Then the content of such a *cart* variable could be used in the tracking calls. On the other hand, this would store data on a users device which in most cases are already stored server side, so inconsistencies could arise (think of a logged-in-user who modifies the *cart* on an other device...).
Maybe cart and order tracking is out of scope for the Tag Manager and an entirely new plugin that allows users to link their shopping backend with Matomo is the best solution here.
Let me know what you think!