I’m representing one of those that see this new segment behavior as a defect. We are using segments for purposes that can be anything between exclude “internal users”, include “Only mobile devices”, include “Server Time 00:00-07:00” and so on. And of course, we have many segments that just include a pattern of URL’s that will narrow the scope of reports to only include a part of the website.
In the way we were using URL based segmentations pre 3.12.0 we created subset of data for our entire site. (Similar to Views in Google Analytics). All those segments are now useless after update to 3.12.0
However, I can see a need for segmentation to be session based but also a great value in being able to do versions that are event based, especially page URL’s.
In fact some variables that can’t change during a visit will always be session based. Like Device Type, Traffic Source, Geo data, Entry Page etc.
Would it be possible to have a configuration for each segment that could be set to either:
Events - Returns all events that match the criteria (With event I mean any page view, downloads, event, actions etc)
Sessions - Identify the sessions that match the criteria, and return all the events in those sessions.
I’m really looking forward to a solution or worksaround to be able to do URL event-based segmentation again.