Segment based on Event Category filters are not working

Narayana_Rangarajan · April 17, 2020, 8:08am

Hi Team,

I tried using segmentation on my records based on event category start with and contains.
It is fetching the wrong records.

Please find the rule and result:

The result also contains other flows whose name does not match.
Can you please help me with the same?

Lukas · April 17, 2020, 8:33am

Hi,

This sounds like

github.com/matomo-org/matomo

Full support for Filters

opened 07:32AM - 22 Jan 20 UTC

viezel

Major Enhancement

Since Segments cannot be used as filter anymore (see https://github.com/matomo-o…rg/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. ## How 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. 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 Operator | Description -- | -- `==` | Equals `!=` | Does not equal `>` | Greater than `<` | Less than `>=` | Greater than or equal to `<=` | Less than or equal to ### Dimension Filter Operators Operator | Description -- | -- `==` | Exact match `!=` | Does not match `=@` | Contains substring `!@` | 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. ## Filter Syntax Given the fact that Segments are alreadty supported, we only need to invent a `filter` parameter. ``` metric_dimension_name operator expression ``` Example: ``` filter=referrerName==Google,referrerName==Bing;country==IN ```

and the issues linked there.

Narayana_Rangarajan · April 17, 2020, 8:54am

Thanks Lukas.

I tried using [General]enable_segments_cache = 0 in config.ini.php and it worked.