Skip to main content

​
Summary

Segments are one of the most important bridges between audience data and campaign execution. In the current app, segments appear to be first-class operational objects with search, filtering, status tracking, pagination, and bulk management behavior. That means segment docs should focus on how teams keep segments trustworthy over time, not just how to create one.

​
Who this is for

  • Operators organizing audiences
  • Campaign managers selecting or validating target groups
  • Teammates debugging why a campaign is or is not reaching the right contacts

​
Where to find it in the app

  • Contacts → Segments
  • segment detail flows
  • campaign setup where segments are selected

​
What the current segment workflow suggests

The segments table currently supports:
  • search
  • status filtering
  • sorting
  • pagination
  • bulk selection and deletion
  • zero states and empty states
That suggests the operational questions are:
  • is the segment ready
  • what data source or logic produced it
  • how many contacts are currently in it
  • should it be reused, edited, or removed

​
Why segment status matters

The current app exposes multiple segment statuses, including queued, processing, failed, and success. That means users need documentation that treats segment readiness as an operational concern rather than assuming every segment is instantly usable.

​
A practical segment workflow

  1. create or open the segment
  2. check status before using it for campaign decisions
  3. inspect the audience size and source logic
  4. review related campaign history if the segment is already in use
  5. refresh, revise, or clean up the segment intentionally

​
What segment statuses should tell you

​
Not calculated

Do not assume the audience is ready yet.

​
Queued or processing

The segment is still being worked on. Wait for a stable state before using it as evidence.

​
Failed

Treat this as a segment problem first, not a campaign problem.

​
Success

The segment completed successfully, but the audience can still be operationally wrong if source logic or data quality is poor.

​
What to inspect on a segment detail page

The current detail workflow strongly suggests teams can inspect:
  • status
  • contact count
  • eligibility or source logic
  • linked data-source context
  • related campaign history
That makes segments much more than a naming layer for static lists.

​
Common mistakes

  • using a queued or failed segment as if it were ready
  • assuming a successful status proves the audience is correct
  • forgetting that linked data sources can drift over time
  • debugging campaign targeting before validating the segment itself

​
Success checklist

  • Segments can be found and filtered quickly.
  • Users understand whether a segment is ready to be used in campaigns.
  • Segment cleanup is possible when old or duplicate segments accumulate.
  • Segment issues can be traced back to status, source, or search/filter assumptions.