Stocker les résultats des questionnaires découvrabilité

[maudetes]

No description provided.

[maudetes]

Switching to English for this short study

Storing surveys results in Matomo

We compile here some results for a study to store survey results in Matomo.

Features list can be found here.

Features that may be used to store survey results could be Event Tracking, Custom Dimensions and Custom Variables.

Event tracking

Reference

Event Tracking adds context to the time people spend on the pages of your website or app.

Events consist of four components (category, action, name and value). As an example, for an event we could have category = Feedback, action = Search Feedback, value = Yes/No, name = search value.

Usage

See Event Tracking with Javascript.

Conclusion

It seems very easy to get started and log an event in matomo. However, by default, we don't have a direct way to cross information made by a user, except if we log an event for multiple questions.

Custom dimensions

Reference

With Custom Dimensions you can assign any custom data to your visitors or actions (like pages, events, site search, …).

You can use a Visit or Action scope. The first one being associated with a specific visitor (having only one value set per dimension), while the second would be associated with an action (page view, download). We could probably use a Visit scope and having multiple dimensions set for a visitor, in order to cross-check information.

Dimensions can't be deleted but they can be renamed.

Usage

See Creation and Tracking custom dimensions.

Limits

Values of custom dimensions are limited to 255 chars (can be changed).
Which means that we can't have huge text area, but it seems a pretty reasonable constraint for our survey.
By default, only 5 dimensions can be used per website.

Conclusion

We could create dimensions such as found-search-result (with possible values True, False), looking-for (with possible values specific-dataset, explore-dataset, specific-reuse, ...).

We could use Visit scope in order to cross dimensions per user (20% of people who didn't find what they were looking for were looking for a specific dataset, etc.), but it may imply that we track our users and we should add a cookie banner.

The limits can be parametrized and are not a hindrance in our use case.

However, the tool is not made for storing surveys by default and even if possible, parametrizing it won't be as straight-forward as a survey tool. Additionally, analysis and visualization may require more work than with a dedicated tool.

Conclusion

Matomo could be a solution to store very short survey results.

We could probably go for Event Tracking in our use case if we want to use Matomo as it seems very simple to use. But it won't directly allow to cross information between questions if we have more than one question.

An example of using event tracking to store Yes/No question (see the picture below) on api.gouv.fr can be found here. The code to send this events is located here.

[abulte]

Evalandgo dans un premier temps.