@atom-box opened this Issue on June 13th 2022

It is a big limitation that Matomo only tracks three things at the product level.

"Because we have a very specific business, our __ products are quite complex. As a consequence we need to track a lot of data related to them in order to build some custom reports or build some benchmarks. Related to products, I only found the 3 very classical dimensions Product SKU, Product Name, Product Category and I did not manage to find a way to push more product attributes. "

"Is it possible to define custom dimension at product level ?"

@Chardonneaur commented on June 14th 2022

@atom-box isn't it a custom dimension at the action level?

@gorfo66 commented on October 17th 2022

We have the exact same requirement in my company. We have very complex products and SKU is not enough to track properly them. We absolutely need to have more custom dimensions that we could use to build finer reports.
Action or Visit scope is definitively not enough

@Chardonneaur commented on October 25th 2022

@gorfo66 thank you but could you give a use case example? because in Matomo you can extend the number of custom dimensions at the action level. For example 50. How does custom dimension at the action level would differ from defining it at the product level?
Without this, I guess that we cannot visualize the final result.

@gorfo66 commented on October 25th 2022

@gorfo66 thank you but could you give a use case example? because in Matomo you can extend the number of custom dimensions at the action level. For example 50. How does custom dimension at the action level would differ from defining it at the product level? Without this, I guess that we cannot visualize the final result.

Unless I'm wrong, Action variables are defined from the URL of the browser. I don't understand how we could apply this approach to the product scope.

We are building ticket retailing applications. We are already massively using product SKU in order to aggregate some info, but we need more flexibility to be able to capture things like advance purchase, date, time, type of ticket, rows, etc.

I can see that we are not the only ones to request such a flexibility.
This is something that is really blocking us from getting out of Google analytics.

@Chardonneaur commented on October 25th 2022

@gorfo66 thank you for the details. In fact, custom dimensions at the action level are defined for the action, so it can be linked to any actions: url, event, form, search etc. I didn't test it, but to me, an order is an action, so you can defined your custom dimension to it.
In GA, you don't have this concept of action, Matomo has, so my guess here, you can achieve what you expect here, date is a custom dimension at the action level, type of ticket same thing etc.

@gorfo66 commented on October 25th 2022

@gorfo66 thank you for the details. In fact, custom dimensions at the action level are defined for the action, so it can be linked to any actions: url, event, form, search etc. I didn't test it, but to me, an order is an action, so you can defined your custom dimension to it. In GA, you don't have this concept of action, Matomo has, so my guess here, you can achieve what you expect here, date is a custom dimension at the action level, type of ticket same thing etc.

GA4 is event based. The concept of action is the foundation of their new system. Everything is action because everything is event.

One order contains several products and for each product could have various values for the same dimension.

I'm really not convinced by the concept of dimension at action level for this specific usecase.
It would be a hacky workaround and not a sustainable solution.

@Chardonneaur commented on October 25th 2022

Ah, we may are reaching a point here "various values for the same dimension", do you mean multiple values for the same dimension?
Like, coupon code dimension could store multiple values "AUTUMNSALES, VIPPERSON" am I correct? (so to say a list of values.

@gorfo66 commented on October 25th 2022

Ah, we may are reaching a point here "various values for the same dimension", do you mean multiple values for the same dimension? Like, coupon code dimension could store multiple values "AUTUMNSALES, VIPPERSON" am I correct? (so to say a list of values.

Think about product dimension as the brand.
You can purchase at the same time a t-shirt Nike and shoes Adidas.
At the end end of the day, you will want to build reports regarding how many Nike products were purchased.
Ok, you can merge all that into the product SKU (and this is what we are doing to some extends) but this merge approach has some limits.

@Chardonneaur commented on October 25th 2022

Ah, I am starting to see it, an order is an action, but an order can have multiple items within it, and items are not action based.
So that's why one would need custom dimensions at the item level am I right @gorfo66 ?

@gorfo66 commented on October 25th 2022

Ah, I am starting to see it, an order is an action, but an order can have multiple items within it, and items are not action based. So that's why one would need custom dimensions at the item level am I right @gorfo66 ?

Yes exactly.

@Chardonneaur commented on October 25th 2022

Perfect, legitimate ticket for sure.

Powered by GitHub Issue Mirror