The list
Each segment shows its name, how many conditions it is built from, its size, and when that size was last counted. Three actions sit on every row: Recount, Edit, Delete.Size is a snapshot, not a live number
This is the one thing about segments worth understanding, and the Counted column is the clue. A segment’s size is calculated when you ask for it and stored. It does not update itself as contacts arrive, change, or leave. A segment counted a month ago shows what it matched a month ago. Recount re-evaluates the conditions against the contact base as it stands now.What the size counts
The size counts every contact of the workspace that matches the conditions, whichever assistant they talked to. A broadcast reaches fewer people than the size says: only those of them who can be delivered to through the assistant’s channels.Writing conditions
A segment holds any number of conditions, joined by all conditions (every one must hold) or any condition (at least one). A segment with no conditions includes every contact.- A tag condition checks one tag. To match several tags, add a condition for each and choose any condition.
- An attribute condition compares one value. Not equals leaves out contacts that have no value for the attribute.
- A group condition that names a group which has since been deleted matches nobody, so a segment never grows wider because a group disappeared.
Deleting a segment
A segment can be deleted even when a broadcast that has not been sent yet is aimed at it. That broadcast is left without an audience and reaches nobody until you choose another segment. A broadcast that is already sending is not affected.Segments and groups
Both narrow the contact base, and they are not interchangeable:
Use a segment for “everyone who bought in the last month” — nobody should have to
maintain that. Use a group for “beta testers” — that is a decision, not a
property.