Group users with segments

Create manual or rule-based segments from user, account, activity, and company data, and use them to filter feedback and control access.

JM
James Morton
Written By James MortonLast updated 1 day ago

Segments group your users by plan, company, country, activity, or any attribute you track. Use them to filter feedback by the customers who matter most, and to decide who can see specific boards, roadmaps, changelog labels, or a private portal. This article covers manual and dynamic segments, the attributes rules can use, and where segments are used.

Where segments live

Segments are managed in the Users area of the admin (open Users from the sidebar). The Segments section of its sidebar lists every segment. From there you can:

  • create manual segments by hand-picking users
  • create dynamic segments that fill themselves from rules
  • filter the users list by segment
  • edit, re-evaluate, or delete a segment

Custom attributes that rules can read are defined in Settings > Users (for people) and Settings > Companies (for companies).

Segment types

Manual segments

Assign users yourself. Use manual segments for curated groups like beta testers, design partners, or key accounts.

  1. In Users, click New segment (the + next to Segments).
  2. Choose Manually assign users to this segment.
  3. Enter a name and optional description, then create the segment.
  4. Select users in the list and use Add to segment. Use Remove from segment to take them out.

You can also add a user to segments from their detail panel.

Dynamic segments

Define rules and let Quackback keep membership up to date. Use dynamic segments for groups like "Enterprise plan", "Signed up in the last 30 days", or "US-based active accounts".

  1. In Users, click New segment.
  2. Choose Auto-populate based on rules.
  3. Enter a name and optional description.
  4. Add one or more conditions.
  5. Choose whether users must match ALL or ANY of the conditions.
  6. Click Create segment.

Tip: Start with one or two broad segments, such as "Enterprise" and "Free". You can refine later.

Attributes you can use in rules

Built-in fields

Attribute

Type

Notes

Name

text

Display name.

Email

text

Email address. Matching ignores case.

Email Verified

yes/no

Whether the user has verified their email.

Locale

text

Language from the identity provider (en, en-US). Only set when SSO or social sign-in provides it.

Account

Attribute

Type

Notes

Principal Type

choice

user or anonymous. Useful for excluding anonymous voters.

Account Age (days)

number

Days since the account was created.

Country

text

Two-letter country code (US, GB), captured at sign-in. Only filled in when a geo-aware proxy or CDN sits in front of Quackback.

Last Active (days ago)

number

Days since the user's most recent session.

Sign-up Source

text

How the user first signed up, for example credential, google, github, sso, or email for magic link only.

Activity

Attribute

Type

Notes

Post Count

number

Posts the user has submitted.

Vote Count

number

Votes the user has cast.

Comment Count

number

Comments the user has written.

Company

Attribute

Type

Notes

Company plan

text

Plan of the user's company.

Company monthly spend

number

The company's monthly spend.

Company size

text

The company's size.

Company industry

text

The company's industry.

Tip: Combine company and user conditions, such as "Company plan equals Enterprise" and "Post Count at least 1", to find engaged users at your biggest accounts.

Custom attributes

Attributes you define in Settings > Users appear in the rule builder too. Send their values from your app when you identify users in the widget, or through the REST API. Custom company attributes from Settings > Companies appear in the company group.

You can also match on a Custom metadata key that isn't defined as an attribute.

Operators

Each attribute offers the operators its type supports:

  • Text: equals, not equals, contains, starts with, ends with
  • Numbers: greater than, at least, less than, at most, equals, not equals
  • Most attributes: is set and is not set, handy for finding users with a missing value
  • Principal Type: equals and not equals only

The value field suggests existing values from your workspace as you type, so spelling stays consistent.

Keeping dynamic segments up to date

Dynamic segments re-evaluate automatically every hour. To refresh one immediately, hover it in the Segments section of the Users sidebar and click the Re-evaluate icon. Manual segments aren't affected.

Edit and delete segments

Hover a segment in the Users sidebar to Edit its name, description, or rules, or Delete it. Deleting a segment removes all of its memberships.

Note: You can't convert a manual segment into a dynamic one or the other way round. Create a new segment instead.

Where to use segments

  • Feedback: filter posts by who submitted them. See Triage feedback in the inbox.
  • Users: show only members of a segment.
  • Board access: limit viewing, voting, commenting, or posting on a board. See Organize feedback with boards.
  • Roadmaps: show a roadmap only to certain segments, or include only posts from certain authors. See Build a public roadmap.
  • Changelog: restrict labels to segments, and send an entry's notifications to selected segments only.
  • Portal access: let segment members into a private portal without individual invites. See Control portal access and sign-in.

Was this helpful?

Your feedback shapes what we write next.