Segmentation, Lists, and Targeting
Core concepts
Distinguish static lists (manual membership), smart lists (dynamic rule-based), and segmentations (a named set of segments applied via the segmentation field). Segmentations power dynamic content and nurture targeting. Know smart list filters (evaluated at runtime) versus triggers (event-based), and that smart lists can be nested with in list / not in list constraints.
Traps
- Assuming a smart list updates instantly - it evaluates at run time, but segmentation membership updates when the segmentation is approved/reapproved.
- Confusing segmentation (one segment per person, mutually exclusive) with smart lists (a person can be in many).
- Forgetting that dynamic content requires the segmentation to be approved and the person to be assigned a segment; unassigned people fall to the default segment.
- Using is not filters without accounting for null/blank values - blanks often fail both positive and negative tests.
Rule of thumb
If targeting must be mutually exclusive (one bucket per person), use a segmentation. If targeting is additive (overlapping conditions), use smart lists.
Worked example
You build a segmentation "Industry" with segments Tech, Finance, and a default Other. A lead with no industry value receives the default segment's dynamic content. Approving a new segmentation version re-evaluates membership - plan re-approval timing around live sends.