Enable Matomo to measure backoffice and actions

What is the need / problem ?

We have implemented Matomo on all instances now (except Norway I think) which means we have data on pages in frontoffice, which is already very cool :tada:
However most inception work is occurring on backoffice currently. Moreover, pageviews is a nice indicator but having data on particular actions/elements would be better.

Who does it impact ?

The product team mostly. The users in a way because this tool can help us build a better platform.

What is the current impact of the problem ?

We have no data on how the backoffice is used. Neither do we on particular buttons/actions.

What is the benefit of focusing on this ?

Enable Matomo on a larger perimeter would help us to take decisions not based on feelings or how often and strongly some users are reaching to us through our support system, but mainly on figures (which have of course to be analyzed carefully).

Potential solutions that will solve the problem ?

On action tracking, Matomo Events seem to be an interesting option : https://matomo.org/docs/event-tracking/ but we need to access the tracking code, which is not possible through the UI right now. We would have to investigate how to do this without having to ask a developer each time we need to add one.

On backoffice, my guess is just that Matomo needs to be allowed to access the backoffice. Again, we need to investigate how to do that considering that each instance has its own access.


  • Selection of a feature candidate
  • T-shirt size of our selected feature candidate
  • Metrics to measure if need is satisfied after feature is implemented
  • Feature owners
  • Epic/projet where you can follow implementation

pinging @danielle @mbudm @Mario just fyi when looking at matomo

We’ll be looking at Matomo for the shopper flow @Kirsten, definitely not tackling the back office as part of this particular piece of work.