alJE
April 22, 2021, 1:20pm
1
I am configuring a segment as follows :
actionUrl does not contain /ae/
However when I go to the Pages report, I can still see all the pages with /ae/.
Lukas
(Lukas Winkler)
April 26, 2021, 9:30am
2
Hi,
This is expected as the segments are applied to visits (so you now only see visitors that at one time accessed a page that contains /ae/
.
You can see here for more information and workarounds:
https://matomo.org/faq/how-to/how-do-i-get-matomo-segments-to-behave-as-a-filter/
opened 07:32AM - 22 Jan 20 UTC
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
```
alJE
April 26, 2021, 12:51pm
3
I don’t think that this is the expected behavior as I am excluding all visits to /ae/ and when I am applying the segment, I still see pages with /ae/ in the Pages report. It is weird, because when I try to see the visitor log for those visitors who had a visit to /ae/ pages within this segment, Matomo says that these visits do not belong to this segment and doesn’t show their visitor log. So in conclusion, the /ae/ pages appear in Pages report even though the segment is excluding those pages.
1 Like