Smart List
A smart list is a dynamic CRM segment whose membership updates automatically whenever a contact starts or stops matching its filter criteria.
Key takeaways
- Re-evaluation may be event-driven, scheduled or lazy, and the timing decides who receives what.
- Relative-time criteria create a rolling window that contacts leave without any action.
- Every smart list needs an explicit exit rule, not only entry criteria.
- The list holds no history, so it cannot say who belonged last month.
- Membership counts are a snapshot, so two reports hours apart legitimately disagree.
In depth
Re-evaluation is where platforms differ, and the difference decides behaviour. Some recompute membership the moment a field changes, some run the query on a schedule measured in minutes or hours, and some resolve it lazily when a campaign actually executes. Movement also runs both ways, so a contact can enter on Monday and leave on Wednesday without anyone touching the rule. Whether the sending workflow triggers on entry or checks membership at every step is a separate setting again.
Criteria that reference relative time turn the list into a rolling window: a rule saying activity in the last thirty days quietly removes people on day thirty-one. Criteria that sit on fields owned by an integration inherit that integration's latency, so a lead who converted an hour ago may still be in the wrong list. Query complexity has a cost too, since deeply nested conditions over a large database slow evaluation. Responsiveness and stability pull against each other here.
The practical uses are routing and entry into always-on programmes, where the audience genuinely changes every day and nobody wants to maintain it by hand. Pair each list with an explicit exit rule rather than relying on the entry criterion to stop being true. In a scorecard funnel a robust rule usually combines something durable with something recent, such as the tier a respondent reached together with a completed lead form, so membership does not evaporate the moment activity pauses.
A smart list cannot tell you who belonged to it last month. There is no history, only the current answer to a query, so any question about a past cohort has to be answered from campaign send records instead. Counts shown in the interface are a moment in time, which is why two reports run hours apart disagree and neither is wrong. For anything that must be auditable months later, a live query is the wrong instrument entirely.
Example in practice
How to measure it
Watch the daily rate of additions and removals rather than only the total. A stable count can hide heavy churn in both directions, which usually means a criterion sits right on a threshold and contacts oscillate across it. Compare the inflow with how many members actually reach the first step of the campaign, since that gap shows how many left again before anything was sent to them.
Then judge the rule by outcome: what share of contacts entering the list eventually reach the goal it exists to serve, whether that is a booked meeting, a reply or a purchase. A criterion admitting many contacts with a low conversion share is too loose. Record median tenure as well, because a very short one means the rule is unstable rather than selective.
Common mistakes
The failure that surprises people most is a contact leaving halfway through a sequence. If entry depended on recent activity and the person goes quiet, they drop out of the audience and the remaining emails never arrive, which looks like a delivery bug rather than a rule doing exactly what it was told. Decide deliberately whether membership is checked once at entry or at every step, and choose criteria that stay true for the whole programme.
The second is using a smart list as a reporting cohort. Figures pulled on Monday and Thursday will not match, and nobody can reconstruct which contacts a campaign actually reached. Snapshot the membership into a fixed list before reporting on it. Teams also build criteria on fields that an integration updates on a delay, then treat the resulting lag as a platform fault rather than as the latency they designed in.
Frequently asked questions
What criteria can power a smart list?
Almost any contact attribute or behavior, such as quiz score tier, lifecycle stage, last email open, page views, or form submissions. Combining several conditions with AND/OR logic lets you target very precise micro-segments.
Can a contact be removed from a smart list automatically?
Yes. The moment a contact no longer matches the criteria, the platform drops them from the list. This is what keeps the audience clean and prevents irrelevant messaging.
What is the difference between a smart list and a static list?
A smart list stores a query and recalculates who matches; a static list stores a fixed set of contact records that only changes when someone edits it. Use the smart list when the right audience genuinely shifts over time, and the static list when you need the same people every time, or an auditable record of who was contacted.
How often does a smart list actually update?
It depends on the platform. Some re-evaluate within seconds of a field changing, others on a scheduled interval, and others only when a campaign runs against the list. Check your tool's documentation before building anything time-sensitive, because a rule that assumes instant updates will behave unpredictably on a platform that refreshes hourly.
What happens if someone leaves a smart list mid-campaign?
That depends on whether the workflow triggered on entry or checks membership at each step. Trigger-on-entry platforms usually finish the sequence regardless; step-checking platforms stop sending as soon as the contact no longer matches. Neither is wrong, but the two produce very different results from an identical rule, so confirm which applies.
Can one contact belong to several smart lists at once?
Yes, and that is normal, since the lists are independent filters rather than folders. The problem is not the overlap itself but the sending on top of it. Add a global frequency cap or a suppression rule so a contact matching three programmes does not receive three unrelated emails in the same morning.
Can I use a smart list for reporting?
Only for current-state questions such as how many contacts match a definition today. It cannot answer historical questions, because membership is recomputed each time and nothing records who matched previously. If you need a defensible number, export the members to a fixed list or report from the campaign's send log instead.
What criteria work best in a smart list?
Combine a durable attribute with a recent signal. The durable part, such as a qualification tier or a role, keeps membership stable; the recent part, such as a form completion, ensures the contact is genuinely current. Avoid rules built entirely on relative time, since those make people fall out on a fixed schedule regardless of fit.