Dynamic vs Static Segments: Rule or Frozen List?
Dynamic vs static segments: a rule keeps its members current, a list records a moment. Choose deliberately for each one, and avoid the two classic failures.
A dynamic segment is a rule whose membership changes by itself as people start and stop matching, while a static segment is a list frozen at the moment you made it. Use dynamic for anything ongoing and static for a record of a moment.
The two kinds fail in opposite ways, so the choice should be made deliberately every time. This post explains each, shows when to use which, and describes the two classic failures that cost founders sends they did not mean to make.
Dynamic vs static segments: what each one is
A dynamic segment is a rule. The guide's example reads contacts who fit the target and clicked in the last thirty days. Nobody maintains the list. Someone who clicks today joins, and someone whose last click has aged out leaves, with no human involved.
A static segment is a list. The guide's examples are the people in the room, the pilot cohort, and the contacts sent a specific offer. It records exactly who was included at the moment you made it, and it never changes unless you change it.
| Dynamic | Static | |
|---|---|---|
| What defines it | A rule | A hand picked or frozen list |
| Membership | Changes on its own | Fixed until you edit it |
| Answers the question | Who qualifies today | Who was included then |
| Best for | Anything ongoing | A record of a moment |
| Typical risk | Late arrivals get messages about things they never saw | It goes out of date while still looking current |
When to use a dynamic segment
Choose dynamic when you want whoever qualifies today, and you want that to stay true without your attention. Every segment from the starter set in how to choose your first segments is of this kind: new and not yet contacted, engaged, cooling, dormant and customers. A contact has to move between them as behaviour changes, and a rule does that for free.
Dynamic segments are also what makes automation work. The most valuable segments start something the moment someone enters them. A new contact matches the target and gets the onboarding sequence. A contact enters high fit with recent pricing intent and the person who owns sales hears about it. Neither works if a person has to rebuild the list first.
When to use a static segment
Choose static when you need to know exactly who was included. Three situations stand out.
- A one time offer. You want to be able to say precisely who received it, and to avoid sending it to people who arrive afterwards.
- A cohort. A pilot group or the people in a room is a fact about a moment. It should not change when the rules would suggest it.
- A record for analysis. When you later compare how a group responded, you need the group to be the same group.
In each case the value is the freezing. A static list is not a lazy dynamic one. It answers a different question.
The two classic failures
Each type fails in a way the other would have prevented.
A static list used as though it were current
A list was exported months ago and is used again today. It contains people who have since bought, left or unsubscribed. You mail customers an acquisition offer, or you mail people who asked to stop. The guide puts it bluntly: rules stay current, lists do not.
A dynamic segment used for a one time offer
A rule is set up for a special offer and left running. Later arrivals qualify and receive a message about something they never saw. The offer may be over, or it may refer to context they do not have. A one time message needs a fixed audience.
| Situation | Wrong choice | What goes wrong | Right choice |
|---|---|---|---|
| Ongoing welcome for new contacts | Static | Newcomers never receive it | Dynamic |
| A single offer to named recipients | Dynamic | Later arrivals get a message they never saw | Static |
| Monthly engaged mailing | Static | Old export mails people who have since left | Dynamic |
| Pilot cohort for a study | Dynamic | Membership drifts while you measure it | Static |
Naming and defining each kind
Both kinds should be explainable in a single sentence before you build them. If the sentence will not come, the purpose is not yet clear, and the rule that results will reflect whichever filters happened to be closest.
Then name the segment for the rule, not the campaign. A dynamic segment named for its rule will make sense in six months. A static segment is the exception where a date or an event is the point, because the moment is the whole content of the list. Even so, keep the name descriptive enough that a colleague could tell what it holds.
Be careful with the words all of and any of
Dynamic segments are built from conditions, and the way you combine them changes the result more than people expect. All of narrows. Any of does the opposite, and a single loose condition can admit nearly everybody.
If a dynamic segment returns a count that startles you, hunt for a loose any of first. Start tight, then loosen deliberately. The same advice as in how to segment by fit and behaviour, where the four boxes depend on precise conditions.
Check the count either way
Whatever the kind, the number who match a segment is never the number who should receive a message. Consent, unsubscribes, bounces, missing addresses and shared addresses all open a gap between them. A static list suffers most, because those exclusions accumulate after the day it was made.
Look at both numbers before every send, and if the gap is large, find out why first. A large gap is usually the base telling you it needs cleaning, a theme developed in how to prevent duplicate contacts.
Retiring segments
Static lists are the commonest source of clutter, because each one is made for a moment that ends. A segment for a finished campaign clutters the list and invites misuse. If nobody can explain one, remove it.
The monthly hygiene pass includes two relevant checks: segments made for finished campaigns have been deleted, and no static list is being used as though it were current. A short list of segments that everyone understands beats a long one nobody trusts.
A decision checklist
- I can state the segment's definition in one sentence.
- I have chosen dynamic or static deliberately, and I know why.
- If it is ongoing, it is dynamic.
- If I need to know exactly who was included, it is static.
- My conditions narrow by default, and any widening is on purpose.
- I know both the matching count and the delivery count.
A month in the life of both kinds
It helps to see the two side by side over a short stretch. Suppose you run an ongoing rule for engaged contacts and also freeze a list of the people who were sent a specific offer.
| When | The dynamic segment | The static list |
|---|---|---|
| On the day | Holds the contacts who match the rule | Holds the contacts you sent the offer to |
| Some days later | New clickers have joined, quiet contacts have left | Unchanged |
| Some weeks later | Still describes who is engaged now | Still describes who received the offer then, and nothing more |
Both are correct. They are correct about different questions. The trouble starts only when you use one to answer the other's question.
Questions to ask before each send
Run through these every time you pick an audience. They take a minute and prevent most of the failures above.
- Do I want whoever qualifies today, or exactly the people I chose then?
- If I picked a list, how old is it, and who has bought, left or unsubscribed since?
- If I picked a rule, would a later arrival be confused by this message?
- Is the message written for this group, not reused from a general broadcast?
- Are contacts without marketing consent, unsubscribed or bounced excluded automatically?
The last point should never rely on memory. Permission to market is the first filter on any marketing audience, which means it is recorded as a structured fact on arrival and applied by the audience itself.
Frequently asked questions
Can I turn a static list into a dynamic segment?
You can build a rule that describes the same people, but it will then include whoever matches today, not the original group. If you need the original group preserved, keep the static list as it was.
Which is easier to maintain?
Dynamic, because the rule maintains itself. Static lists need you to remember what they are and whether they are still current.
Should lifecycle stage be dynamic?
Stage is a field, and segments that lean on it are normally dynamic, since you want whoever is in a stage today. How to define the stages themselves is in how to define lifecycle stages.
What if I use a static list by accident?
Check its age and compare it against who matches now. If people have bought, left or unsubscribed since, stop using it and replace it with a rule.
The full method, with the checklists, is in The Segmentation Playbook, a free 35-page playbook.