Audience Segmentation

Build and compare customer segments by behavior, lifecycle, plan, attributes, and campaign eligibility with size and overlap visible. The screen connects Segments and Builder so growth teams can find the “Create segment” action while checking segments and addressable.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Power users · 18% and At-risk accounts · 9%, rather than an empty visual shell.

Audience Segmentation
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Create segment

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Growth teams need a clear “Create segment” action without losing sight of segments, addressable and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Create segment is clearly available where the task happens.
  • Main view: Segments keeps the starting point obvious.
  • Connected view: Builder supplies nearby context.
  • Metric: Segments is visible with a meaningful value.
  • Another signal: Addressable helps people judge what to do next.
  • Representative record: Power users · 18% makes the example specific.
  • Second record: At-risk accounts · 9% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading segments without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for builder; clarify who can continue.
  • Success after choosing Create segment; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Segments → Builder → Create segment → Review outcome

Patterns used

Analytics, Segments, Builder, Overlap, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Power users · 18% with At-risk accounts · 9%. Make segments clear, then use addressable to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Create segment” action. The happy path alone is not enough.

Related UI examples: Campaign Builder, Marketplace Seller, Content Calendar.

Start from this in Figr

Design a audience segmentation screen for our existing software product. Use our real design-system tokens, components and product language. Show Segments and Builder, include believable records such as Power users · 18%, and make create segment easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr