Should I use a static list or a segment in Whippy?
Last updated: November 5, 2026
Use a static list when an audience should stay fixed, and use a segment when the audience should update automatically from contact data.
Before you start
Decide whether contacts should enter or leave the audience automatically.
Use a static list for fixed audiences such as imports, event groups, one-time sends, or uploaded lead batches.
Use a segment for live audiences based on changing fields, tags, lists, preferences, or object data.
Steps
Identify the audience you need to create.
Ask whether the audience should remain the same unless someone manually changes it.
If yes, create or use a static list.
If no, create or use a segment.
Use static lists for one-time sends, event groups, uploaded leads, or fixed customer batches.
Use segments for recurring campaigns, live operational audiences, opt-in or opt-out filtering, or changing statuses.
Review audience membership before using it in campaigns, sequences, or exports.
Tips
Name lists with the source and date so users understand where the audience came from.
Name segments by rule intent so users understand why contacts are included.
Use segments when membership should follow the latest data.
Use static lists when you need a stable record of who was included.
Troubleshooting
If a contact joined an audience unexpectedly, the audience may be a segment and the contact now matches the rules.
If a newly added contact did not join an audience, the audience may be a static list.
If a campaign audience changed between review and send, review segment membership before sending or use a static list when the audience must not change.