Segmentation
Assign records to segments from rules, and keep them assigned as the records change.
Segments that live in someone's head. Enterprise means over a thousand employees, except when it means over five hundred, except for the list the marketing team built in March. Nobody can reproduce last quarter's segment because nobody wrote down what it meant.
A segment is a rule, written once, that names records rather than listing them.
Labels are abstract until they are applied. A segment names its labels and the conditions that select them; the field the label is written to is bound when a run applies it. One segment can therefore serve contacts, leads and accounts rather than being rewritten per object.
First match wins. Conditions are evaluated in order and a record takes the first label it qualifies for, so overlapping rules resolve predictably instead of by whichever ran last.
How a pass runs
The detail
Reproducibility
The difference is whether the definition survives the person who made it.
A list is a set of record ids that was true once. A segment is a rule that is true now. The first goes stale the moment a record changes and nobody can say why a record is on it; the second re-evaluates and can always explain itself.
Because the definition is saved rather than the result, the same segment can be applied again next quarter, applied to a different object, or read by every other tool as the scope for what it does.
For agents
Reads are free and need no permission to write. Anything that changes a record is a separate grant.
list_rule_templates the segments defined on this connection readget_rule_template one segment, with its labels and conditions readcreate_rule_template author a segment writedispatch_run start a run that applies one writeWhere to start
The readiness scan runs detection against your own CRM and reports what it finds, before anything is merged.