Solved

More options for Saved Segments

  • 8 February 2021
  • 5 replies
  • 103 views

Userlevel 1
Badge

The definition of Saved segment is quite limited, for example it is not possible to:

  • Exclude users who performed an action
  • Filter events based on their parameters (and not just the event name)

Is there any workaround?

 

Thanks

icon

Best answer by Saish Redkar 8 February 2021, 18:12

Hey @JoeKDoe 

  1. The “Exclude users who performed an action” is something which can be easily done using behavioral cohorts. This isn’t possible using Saved Segments.
  2. When you say “Filter events based on their parameters” , do you mean that you want to build a segment for users who performed an event and select a specific event property for that event? If that’s the case, then it’s possible. 

 Most of the limitations of saved segments can be addressed using behavioral cohorts, which I just realized isn’t available on Amplitude’s Free Plan ( Platform Specialists, correct me if I’m wrong here) 

Hope this helps!

 

View original

5 replies

Userlevel 5
Badge +4

Hey @JoeKDoe 

  1. The “Exclude users who performed an action” is something which can be easily done using behavioral cohorts. This isn’t possible using Saved Segments.
  2. When you say “Filter events based on their parameters” , do you mean that you want to build a segment for users who performed an event and select a specific event property for that event? If that’s the case, then it’s possible. 

 Most of the limitations of saved segments can be addressed using behavioral cohorts, which I just realized isn’t available on Amplitude’s Free Plan ( Platform Specialists, correct me if I’m wrong here) 

Hope this helps!

 

Userlevel 2

For #1. 

As @Saish Redkar stated, this is possible with Behavioral Cohorts quite easily. A possible workaround for excluding users would be to filter for users “who performed” X event < 1 time. Here is an example: https://analytics.amplitude.com/demo/chart/new/f9hs4d3

Filtering for users “who performed X event” < 1 time

For #2. 

Saish has a great approach to “filter events based on their parameters” which is possible as he has mentioned!

 

Userlevel 5
Badge +4

@jarren.patao 
That’s a nice workaround ⚡  for #1. I almost missed the fact that we can still use the < , > operators to achieve that.

Do you see any edge cases cropping up if we use the = 0  vs < 1 clause for excluding users who performed event X ? They both seem to align logically as expected as seen here - https://analytics.amplitude.com/demo/chart/new/apx7ee2 

Thanks! :relaxed:

Userlevel 2

Hi @Saish Redkar, using “= 0” vs “< 1” should effectively behave the same for this type of analysis!

Badge

Regarding #2: I have a free plan and don’t see this option (to build a segment for users who performed an event and select a specific event property for that event). Is it available only for Pro plan?

Reply