Related:

https://forum.matomo.org/t/filter-page-urls-by-segments/34859

To us this is a critical bug. One of the main tasks in Matomo is no longer working as we and clients expect it. This should not have been implemented in a non-breaking minor release.

It needs to be made an optional segment option. Until it becomes optional in 4.0.x it should be reverted in a new regression release of 3.x.

Related: #15133

IMO this issue is important.

See #15130 (comment) on how to restore old behaviour. We're not planning to restore the previous behaviour as default behaviour unfortunately. Segment feature is supposed to work like it is implemented now and it was buggy how it worked before. We totally understand this is frustrating but there's no way we can make everyone happy unfortunately and we followed to what most users are wanting/expecting and how it works on other analytics solutions. The feature you're referring to be a "filter" which we don't have yet. Custom Reports supports it though.

Why is this issue closed? There is still no solution for many matomo users.
Our company have the same problem like TheFirstGoodmaN and fe-hicking. Custom Reports, Custom Dimensions don't bring the same result an to disable the new behaviour is no solution for us.

Like the example of TheFirstGoodmaN, there is no difference between page-url and action-url anymore.
As far as I know the "bug" referred only to the parameter "Page-URL", why was the function also changed for the parameter "Action-URL"?

In addition, we now even have a big data protection problem, because more data is displayed as desired/allowed. In our case, we are no longer compliant with gdpr and we can not use this anymore.

@PeteTrombone just to understand why do you not want to disable this feature to have old behaviour? In general we can't have the same feature working in two different ways and everyone would expect to behave it one or the other way. We're really talking of one feature here. Be keen to hear your thoughts on why Custom Reports did not do the trick here and what we can maybe improve. Feel free to get in touch with our support about that: shop at innocraft.com

@tsteur just looping back here. I have another scenario using Events API where it makes no sense at all.

Piwik::api('Events.getCategory', [
    ... // some params that does not matter for this example
    'segment' => 'eventAction==ViewScreen;eventCategory==ContractSigned',
    'secondaryDimension' => 'eventName'
]);

You should think that the above code would filter through all the events and only show events that

1. have eventAction ViewScreen
2. have eventCategory = ContractSigned

In 3.11 we get a list of 30 events matching , but in 3.12 - we get a list of all events (1000+)?
I dont follow how this cannot be a bug. Are we sure this is the behaviour we want?

@viezel this is really the correct behaviour and how segmentation should work. You're really more after a filter here which we don't really have yet in Matomo except for custom reports.

@tsteur I see. Then please let me know how you will only data with these 2 conditions I showed?

because filter_pattern cannot do that, so I cannot see how to achieve this now

Then please let me know how you will only data with these 2 conditions I showed?

You would either need to manually filter this data if that's an option (possibly not since you have two different segments applied and you probably wouldn't get the data you want) or you use custom reports where you can apply a filter.

I totally understand this is frustrating. This is how people expect segmentation to work and unfortunately we don't have yet such a filter feature in core that you are after.

But Filters must be top priority for you in next release, right?
I really don’t know any software platforms that takes fix/changes features with the argument “we don’t support this anymore”.
Even through we have custom reports, it will takes days to regenerate reports going back in time. It’s not really a valid solution for ongoing businesses.

We at Napp really like the mission and product of Matomo, but this move is really bad. It’s not even considered a breaking change in your changelog 😳

Your ads even talks about filtering with segments 🤷🏻‍♂️

You can filter reports through custom reports and through our API filters but in that it won't work indeed.

You can restore the old behaviour immediately by setting enable_segments_cache = 0 in your config/config.ini.php see my comment in #15163 (comment) We've added this setting in case someone really wants that old behaviour instead of just removing the old way altogether.