Audiences

In Contacts → Segments, an audience can use assignments or conditions. Choose its type at creation; it cannot change later.

Use assignments for explicit membership

Create a segment with a recognizable name and add contacts from its details. Remove them without deleting profiles. Integrations, imports and automation actions can also add assignments.

Use this type for selections maintained by your team or an external system. Repeating an assignment does not create another member or a fictitious journey entry.

Use conditions for a dynamic group

Select profile fields, custom fields or membership in an assignment segment. Group rules with All to require every condition or Any to accept at least one. Use operators offered by the field type.

For example, combine language equal to es-CR and company being present. A missing value is distinct from zero, false or an empty selection: use the appropriate presence condition.

Condition membership is recalculated when data or assignments change. Members cannot be added or removed manually; change the rule or its source data. Membership rules only reference assignment segments to avoid circular dependencies.

Evaluate before preparing a broadcast

Save changes and use Evaluate. Evaluation runs in the background and the detail history shows generations. Wait for a complete generation of the current revision before selecting it for a broadcast.

The generation retains members found during evaluation; it is not a global snapshot if profiles change while evaluation runs. Saving a broadcast pins a particular generation. Evaluating the segment again does not automatically update saved broadcasts.

Distinguish members from eligible recipients

Members may be excluded from email when archived, unsubscribed or suppressed. Sending checks these states again. A valid empty generation does not indicate a technical failure.

Archiving retains history and frees an active slot, subject to dependencies. Resolve any broadcast or automation still using the audience first. Restoring checks the plan limit and reconciles conditions again. See broadcasts and automations.