New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full support for Filters #15438
Comments
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) |
vote 👍 |
Hi there, 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) |
@tsteur It seems that I missed the configuration option in the documentation. Thanks for the hint and the update. This will be fine for us for the moment. 👍 |
Hello, is this config still available (working) with version 4.2.1?: Thanks a lot |
Hi @Petsios, Nothing changed about this since the release of Matomo 4: Lines 205 to 209 in d099f75
|
Hi, sorry for the question ... |
Hi all, I can really recommend migrating to https://posthog.com/. We did this after the fact that Matomo cannot provide real segmentation and cohort analysis. Its open source, self hosted and super powerful. |
@jr-ewing Isn't that kind of automatically defined by the segment? As soon as an action dimension is used its an action scope otherwise it's visit scope. Or what exactly do you mean here? |
Customer's request: I want to build widgets that work with the filters. |
@KarthikRaja1388 Are you able to explain that a bit more? Does he want to e.g. show an page url report, that only contains urls that matches a certain pattern, or is that request really about filtering the data before archiving? |
@sgiehl Will post the customer's full question: In the Custom Report Plugin I have the option of filters. So I want to build widgets that work with the filters. Segments not working for me - in this case. What I want to recreate is the table under "Pages". My widget should have the same columns as under "Pages". In addition, I want to display the entry columns, which you can currently find under entry pages. So I would like to show the values of a URL. |
Matomo: What is the feature you are missing the most in Matomo and why? |
Question: |
Since Segments cannot be used as filter anymore (see #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.
How
As Matomo also advertise to be a replacement of Google Analytics, then lets see what they do:
Source: https://developers.google.com/analytics/devguides/reporting/core/v3/reference#filters
For rich possibilities of Filtering the massive amount of data a regular website/app gets, we need the following operators:
Metric Filter Operators
==
!=
>
<
>=
<=
Dimension Filter Operators
==
!=
=@
!@
=~
!~
It would be a big plus if we could get support for Regular expression in those filters.
Filter Syntax
Given the fact that Segments are alreadty supported, we only need to invent a
filter
parameter.Example:
The text was updated successfully, but these errors were encountered: