User Segments

Group your end users into reusable audiences — Beta Customers, Enterprise, Power Users — then use those segments to gate visibility, filter your inbox, and scope AI queries.

What Is a User Segment?

A user segment is a saved group of end users defined by a set of rules. Instead of repeatedly filtering by "users where company MRR > 5000 AND tier = enterprise," you define that group once as Enterprise Customers and reuse it everywhere.

Segments are organization-scoped and dynamic — when new end users match the rules, they're automatically included.

Where Segments Are Used

Use Case	How It Works
Visibility gating	Make a board or post visible only to a specific segment
Post-creation access	Only let users in a segment submit to a board
Inbox filtering	Filter feedback to see only posts from a segment
Ask AI scoping	"What are Enterprise Customers asking for?"
Custom field defaults	Set defaults conditional on segment membership

This is what makes segments the connective tissue between your customer data and your portal experience.

Create a Segment

Open User Segments

Go to Settings → User Segments and click New Segment.

Name your segment

Give it:

Name — what the segment is (e.g., "Enterprise Customers")
Description (optional) — a one-line hint of what defines membership
Color (optional) — used as a chip in admin

Choose match type

Decide how rules combine:

All (AND) — user must match every rule
Any (OR) — user matches if at least one rule fits

Default is All, which is right for most segments.

Add rules

Each rule has three parts:

Attribute — what user property to check (email, company MRR, country, custom field, etc.)
Operator — how to compare (equals, contains, greater than, etc.)
Value — what to compare against

Add as many rules as you need. ProductBridge shows the matching count live as you build.

Save

Your segment is live immediately. Membership is evaluated dynamically — new end users matching the rules are automatically included.

Available Attributes

Segments can be defined on any of these dimensions:

Dimension	Examples
User identity	Email (contains, ends_with, equals), Name, Avatar present
Company	Company name, MRR, customer status, renewal risk
Activity	Posts created, votes cast, comments made
Custom fields	Any custom field value on the user's profile
Integration source	Where they came from (Intercom, Slack, portal, etc.)

The available attributes are defined globally and may expand over time. If you need to filter on something we don't yet support, let us know.

Operators

The operator options depend on the attribute type:

Operator	Works With
equals / not equals	Strings, numbers, enums
contains / does not contain	Strings
starts with / ends with	Strings (e.g., email)
greater than / less than	Numbers, dates
between	Numbers, dates
is empty / is not empty	Any attribute

Examples

Match: All
Rule 1: Company MRR greater than 5000
Rule 2: Customer Status equals Active

Match: Any
Rule 1: Email ends with @acme.com
Rule 2: Custom field: Beta Opted In equals Yes

Match: All
Rule 1: Posts created greater than 5
Rule 2: Votes cast greater than 20

Match: Any
Rule 1: Renewal Risk equals High
Rule 2: Last activity more than 60 days ago

Using Segments to Gate Boards

The most common use of segments is restricting which end users see specific content:

Create a Beta Customers segment
Create a Beta Board with visibility = User Segments → Beta Customers
Only end users matching the segment see the board on the portal

This is how teams run private beta programs, enterprise-only feedback channels, or staged feature rollouts — without any custom code.

See Visibility & SEO for the full visibility model.

Live Match Count

When viewing a segment, ProductBridge shows a Matching Users count. This count is cached for performance and refreshes periodically — it may lag real-time membership by a few minutes.

For exact, real-time membership, click View Users on the segment to see the current matching list.

Segments work best when they're stable definitions of customer groups, not one-off filters. Use saved views for ad-hoc filtering of your inbox. Use segments when you want to reuse the same group definition across multiple features.

Was this page helpful?

Last updated 4 days ago

Built with Documentation.AI