A segment is a saved set of customer filters. Use it to compare requests from groups such as customers on a specific plan or within a revenue range.
Use Saved segments to load it again. Manage segments lets you manage saved definitions. If a segment uses billing fields, first add that data through Stripe, another integration or your customer data.
Open a feedback board as a table, using its ··· → Open as table action.
For example, 60% in a request's segment column means 60% of that request's voters belong to the segment. It does not mean 60% of every customer in the segment wants the feature. Segments can overlap, so percentages across columns need not add up to 100%.
Open the request and read its discussion before deciding what the numbers mean. A customer profile provides more context about an individual person's requests.
Choose Author segment instead if the question is "What did these customers submit?" A customer can vote for someone else's request, so the two filters can produce different results.
No. A segment stores filter criteria, not a fixed list of people. When customer data changes, the matching users can change too. Check the source data if a customer unexpectedly joins or leaves a segment.
Segments describe demand; they do not grant board access. Use user groups to give selected people access. For the top requests from one business, use its company page.