Segmentation

Segmentation examples and use cases

Segmentation becomes powerful when you apply it to real scenarios. Here are common ways teams use segments to deliver better experiences.

By plan or subscription tier

Scenario: You want paying customers to see your full roadmap, but free users should only see a limited view.

Setup:

  • Pass plan: "free" or plan: "pro" via the Frill Script

  • Create segments: "Free Users" (plan equals free) and "Paid Users" (plan equals pro)

  • Create two roadmap widgets: one targeted to Free Users with public items only, another for Paid Users with everything

Result: Free users see a teaser roadmap that encourages upgrades. Paid users see your complete product vision.

By revenue or customer value

Scenario: You want to survey high-value customers about their experience without bothering smaller accounts.

Setup:

  • Pass mrr: 500 (monthly recurring revenue) as a user or company attribute

  • Create segment: "High-Value Customers" (mrr greater than 500)

  • Target your NPS survey to this segment only

Result: You get feedback from customers who matter most to your revenue, and smaller accounts aren't interrupted.

By role or permissions

Scenario: You're launching an admin-only feature and want to announce it only to admins.

Setup:

  • Pass role: "admin" or role: "user" in your identify call

  • Create segment: "Admins" (role equals admin)

  • Target your announcement to the Admins segment

Result: Admins see the announcement. Regular users don't get confused by features they can't access.

By geography or region

Scenario: You're rolling out a feature only available in Europe and want to announce it to European users.

Setup:

  • Pass region: "EU" based on your app's user data

  • Create segment: "EU Users" (region equals EU)

  • Target your announcement and widget to EU Users

Result: Only users in the affected region see the update. No noise for users elsewhere.

By beta or feature flag

Scenario: You're testing a new feature with early adopters and want their feedback before a full launch.

Setup:

  • Pass betaTester: true for users in your beta program

  • Create segment: "Beta Testers" (betaTester equals true)

  • Target an idea board widget to Beta Testers only

Result: Beta users can submit feedback on the new feature. General users don't see it yet.

By company or organization

Scenario: You have enterprise customers who need private announcements about their custom integrations.

Setup:

  • Pass company-level attributes: companyId: "acme-corp"

  • Create segment: "Acme Corp" (companyId equals acme-corp)

  • Target announcements to the Acme Corp segment

Result: Acme Corp sees updates relevant to them. Other customers don't see private company-specific news.

Combining multiple conditions

Scenario: You want to survey paying customers in North America who signed up more than 6 months ago.

Setup:

  • Pass plan: "pro", region: "NA", signupDate: "2023-01-15"

  • Create segment: "Established NA Customers" with three conditions:

    • plan equals pro

    • region equals NA

    • signupDate before 2024-07-01

  • Target your survey to this segment

Result: Only customers who meet all three criteria see the survey.

Start with one or two attributes and expand as you learn what targeting matters most to your team.

Next steps

Ready to create segments? See Custom user attributes for segmentation to set up attributes, then Creating and using user segments to build your first segment.

Was this helpful?