Customer segmentation groups customers by shared characteristics relevant to a decision. A practical starting point is a rule that identifies which records belong.
Choose a useful distinction
Recorded location can define a regional group; purchase history can identify previous buyers. Choose a distinction that matters to the decision. These are examples, not an exhaustive taxonomy.
Combine the conditions
Mailchimp explains that AND requires every condition; OR requires at least one. A contact can belong to several matching groups.
Compare explicit answers
Fictional workshop example: customers explicitly answered whether they wanted evening sessions and materials information. This table compares both interests with either interest.
| Evening | Materials | Both (AND) | Either (OR) |
|---|---|---|---|
| Yes | Yes | Yes | Yes |
| Yes | No | No | Yes |
| No | Yes | No | Yes |
| No | No | No | No |
A missing answer remains unresolved in this example. Inspect it separately; the table models explicit answers, not software handling of blank fields.
Current members or a snapshot
Klaviyo documents dynamic segments: members enter or leave as their data meets or stops meeting the conditions. Its snapshot feature creates a separate static list of current members while the original segment continues changing.
Choose whether your question concerns current membership or who belonged at a particular time. Label a saved snapshot with its date and rule. A frozen group serves a different purpose from a changing one.
Inspect the records
Check that the required field is available to the tool. Klaviyo notes that not every synced event property is usable for segmentation. Inspect included and excluded records against your intended rule before acting on the group.