Skip to main content
"Top/Bottom List" Filters

Filter the "top n" or "bottom n" entries by metrics and numeric fields

Daniel Sternegard avatar
Written by Daniel Sternegard
Updated over a week ago

Planhat "filters" are ubiquitous to most users - it's a very flexible yet simple way of creating custom segments in your portfolio and use those segments in Workflows, NPS campaigns, reporting, etc.

Common use cases of filters in general

Some common use cases are:

  • Companies segmented by Industry

  • End-users by Role (e.g., decision-maker) or Usage

  • Issues by Health of the involved Companies

And then there are the more granular ones using cross-model filtering, like:

  • All Companies on US West Coast in the Adoption phase with <6 months to renewal, a decision-maker who gave us <6 on the last NPS, with >2 active tickets in support, with >20% decline in Week-over-Week usage over past 4 weeks, more than 2 weeks since we last spoke with them, and who were not part of this month's email campaign

These filters can then be applied to revenue data (e.g., show me NRR for this segment), Workflows (put all SMB customers in this onboarding), analytics (here is a cohort graph of Swedish customers).

πŸ“Œ You can read more here about how to design them!


Top/Bottom list - use cases

Top list and Bottom list are two filter types that combine rule-based segmentation with a distribution element. This enables users to watch the "edges" of their portfolio. Some common use cases are:

  • "Top 10 Companies by ARR"

  • "Bottom 20% of End-users by Usage" (to put them into a re-engagement campaign)

  • "The 10% of Companies closest to Renewal" for extra-intense monitoring of usage and tickets

This can also be combined with other rules, like:

  • Top 10 customers in onboarding by ARR

  • Bottom 10% of decision-maker end-users who are have renewal in next 2 months

To build this, select "Top list" or "Bottom list" under field type. Then define:

  • "Top/Bottom list by": this is the data point you want to "rank" based on (e.g., ARR)

  • "Limit Result": this is the defined cut-off point, either in count (#) or percentage (%), e.g., "10%" or "20"

  • ...any other conditions you want, like "only companies in Onboarding"

You can then use this filter across Planhat, like "ping this Slack channel when a company goes in/out of the Top 10 list by Usage", "put my bottom 20% of decision-makers by usage into a re-engagement campaign", or break down your portfolio in a management report by looking at specific cohorts.

Did this answer your question?