Segments

Segments are reusable user groups you can reference in feature flag targeting rules. Instead of repeating the same targeting conditions across multiple flags, create a segment once and use it everywhere.

Benefits:

• Reuse – Define user groups once, use across many feature flags
• Maintain – Update targeting logic in one place
• Organize – Group related conditions together

Segment Types

Supaship supports two types of segments:

Conditional Segments

Dynamic user groups based on targeting conditions. Users are automatically included/excluded as their attributes change.

Use cases: Premium users, users in specific countries, users with certain plans

Example: “Premium Users” segment includes users where plan = 'premium' OR (subscription_status = 'active' AND plan_tier > 'basic')

List Segments

Static lists of specific user identifiers. Manually add/remove users as needed.

Use cases: Beta testers, internal team, VIP customers

Example: “Beta Testers” segment contains: user-123, user-456, user-789

Creating a Segment

1. Go to Segments in your project
2. Click “Create Segment”
3. Enter a name and choose type (Conditional or List)
4. Configure:
   • Conditional: Add targeting conditions (e.g., plan = 'premium')
   • List: Add user identifiers (e.g., user-123, user-456)
5. Click “Create”

Using Segments in Feature Flags

Reference segments in your feature flag targeting rules:

1. Open a feature flag → Targeting section
2. Add/edit a targeting rule
3. Select “Segment” as the attribute
4. Choose your segment from the dropdown

Now you can use the same user group across multiple feature flags. Update the segment once, and all flags using it update automatically.

Best Practices

Naming: Use clear, descriptive names like “Premium Users” or “Beta Testers”

When to use Conditional:

• User group changes automatically based on attributes
• You want dynamic evaluation (e.g., all premium users)

When to use List:

• Small, static group of specific users
• Manual control needed (e.g., beta testers)

Limitations

• Project-scoped (not shared across projects)
• Conditional segments use AND logic (all conditions must match)
• Cannot nest segments (no segments within segments)