header
No Status

Allow configured "Segments" to be used anywhere as a filter within PX, not just within the Engagemen

  • 3 October 2019
  • 5 replies
  • 63 views

Userlevel 5
Badge
Posting this for several customers, since I believe this is a great feature request!

------------------

Currently, Segments can only be used for targeting Engagements through Audience Rules and not directly in Analytics. Because of this, customers must use/create custom filters that mirror their Segments to do something similar within Analytics.

It would be great if including Segments criteria as an option everywhere that a filter could be used.

@ciarapeter @mickey @shira


5 replies

Userlevel 3
Hi @link_black tnx for posting this. I'd add this a bit more details. For instance, if I make a segment „Self-service customers,“ I'd like to be able to apply that segment in the rule „is“ or „is not“ for:



• Cohort analysis

• Adoption

• As an engagement audience (send, e.g. welcome message to segment „first sign up“)

• Audience preview (account and user level)

• Etc.





I worked a lot with segments and segmentation in my experience, and I'm looking on ways how to incorporate it now with the analytics PX offers.

Userlevel 5
I add a wholehearted +1 here.

Filtering the different analytics views by Segment would make it easier for PX admins to enable other team members to get value out of PX. One of my team members could filter by segment, rather than needing to build out a nuanced filter themselves.

My way to accomplish this currently is to create Public filters that are relevant to different people. Where I get stuck is that applying a Public filter to a report overwrites other filters currently applied.

For example, someone on my team may want to see how many times users engaged in ____ feature. Once they see that, they may want to see that information filtered by a certain segment of users. They may want to see that info for several segments of users at the same time. If we could filter by Segment, we could set the Segment logic to OR and create a... Super Segment! (Now I'm just making up words)

Another valuable application would be filtering by a Segment made up of power users. Every org is going to have a different definition of what a power user looks like. The value I could see here would be:

  • analyzing power user behavior - what are they doing differently? are they spending more or less time in the product? etc
  • removing power users when analyzing the "Average" user - great, power users are engaging in the new features, but what about the rest? Are those features relevant to a broad audience or just very experienced users?
The point being, filtering by Segment could allow for a more natural progression in data discovery/exploration for less data-savvy team members.

Userlevel 3

Adding another vote for this one. It would just seem natural that if a segment is setup in one part of the application, it could be used in the other parts of the application.

Userlevel 3

I also upvoted this idea. I feel that filters and segments indeed are very similar concepts. Additionally, it seems that filters on dashboards and analytics, filters on engagements and segments sometimes contain different properties to be used in filtering that could also be used in other places.

Userlevel 2

💯 this would be huge!  We also selected Pendo b/c segments weren’t universally available in PX.

Reply