Since Segments cannot be used as filter anymore (see https://github.com/matomo-org/matomo/issues/15163) Then I put forward this high priority feature request to add full feature support for Filtering. Suggesting
Custom Reports plugin as a solution for this feature is not an option. This feature must be part of the core offering.
Most modern web application are data driven and as part of its value proposition it will create dashboard, reports etc to inform its users of the usage of their offering. Building user defined reports/views/dashboards based on user interactions will include filtering, as the user want to see exact results. Filtering and segmentation is the essentials features of any Analytics platform. Hence, we must build this missing feature at its highest priority.
As Matomo also advertise to be a replacement of Google Analytics, then lets see what they do:
Filtered queries restrict the rows that do (or do not) get included in the result. Each row in the result is tested against the filter: if the filter matches, the row is retained and if it doesn't match, the row is dropped.
Dimension filtering: Filtering occurs before any dimensions are aggregated, so that the returned metrics represent the total for only the relevant dimensions.
- Metrics filtering: Filtering on metrics occurs after the metrics are aggregated.
- Valid combinations: You can filter for a dimension or metric that is not part of your query, provided all dimensions/metrics in the request and the filter are valid combinations. For example, you might want to query for a dated list of pageviews, filtering on a particular browser.
For rich possibilities of Filtering the massive amount of data a regular website/app gets, we need the following operators:
||Does not equal|
||Greater than or equal to|
||Less than or equal to|
||Does not match|
||Does not contain substring|
||Contains a match for the regular expression|
||Does not match regular expression|
It would be a big plus if we could get support for Regular expression in those filters.
Given the fact that Segments are alreadty supported, we only need to invent a
metric_dimension_name operator expression
Silly remark, though wouldn't it be the same feature as the shortcut one in Google Analytics? So to say applying a filter gives you the possibility to save it and to make it as custom report (though you won't have the possibility to add additional columns)
quick update here:
We'll see next year (this year is already fully planned) whether work on this or not. It's not too high of a priority because:
I do fully understand it's useful and would love to have this too. The combination of performance trouble, taking long time to develop etc while there are workarounds makes it not the best candidate to work on right now though (not saying we won't do it next year or so)