Implemented
0
Feature request: Allow session properties to be saved as segments
Source: umami-software/umami#4507 · opened by @sethschori
Describe the feature or enhancement
Use case: We want to segment all of our traffic by two session properties. We're already sending those session properties to Umami, and it works to add them manually as filters. Right now, we have to go through the multiple clicks each time — or save the URLs for boards, overviews, etc. in some other place (like a Notion page) — if we want to use that combination of session properties as a filter. It would be much more convenient if that session property filter combination could be saved as a segment. That would allow easily adding the segment across boards, overviews, and other places. I don't think this matters since I don't think segmentation and filtering are pricing tier features, but we're using Cloud Umami.
Request: Allow session properties to use the same "Save segment" feature that commonly used filter items (path, country, browser, etc.) are already able to use.
Use case: We want to segment all of our traffic by two session properties. We're already sending those session properties to Umami, and it works to add them manually as filters. Right now, we have to go through the multiple clicks each time — or save the URLs for boards, overviews, etc. in some other place (like a Notion page) — if we want to use that combination of session properties as a filter. It would be much more convenient if that session property filter combination could be saved as a segment. That would allow easily adding the segment across boards, overviews, and other places. I don't think this matters since I don't think segmentation and filtering are pricing tier features, but we're using Cloud Umami.
Request: Allow session properties to use the same "Save segment" feature that commonly used filter items (path, country, browser, etc.) are already able to use.
No pledges yet. Be the first to back this.
Comments
Similar requests
Session identity stitching (v3.3.1) silently overwrites the linked distinctId when two different users share the same session hash (IP + User-Agent)
0 votes · 0 comments
[improvement] add per session view
3 votes · 0 comments
Heartbeats for more accurate visit duration tracking
10 votes · 0 comments
Suggestions for Useful Options
1 vote · 0 comments
Share URLs with pre-applied filter or segment
0 votes · 0 comments
No comments yet.