What is the difference between a group and a segment?
A MailerLite group is an explicit membership list, also described as a tag. Adding someone to a group records a classification you or another process chose. A segment is calculated from conditions: subscribers enter when they match and leave when they no longer match. A segment can use group membership alongside other supported criteria.
For example, Requested template is a useful proposed group name because it records a specific request. Signed up recently is a useful proposed segment because its membership changes over time. Keeping those meanings distinct makes it easier to explain why a subscriber appears in an audience.
| Audience label | Candidate mechanism | Reason |
|---|---|---|
| Requested onboarding worksheet | Group | Records the intentional request |
| Interested in reporting | Group | Records a declared topic preference |
| Recent reporting subscribers | Segment | Combines topic membership with a changing signup window |
| Customers needing a specific notice | Segment or explicit group | Depends on how reliably the customer state is updated |
Start with a small audience model
In a fictional reporting SaaS, a reader can request a worksheet without becoming a customer. Store the request separately from product status. Otherwise, a later campaign may mistake an interested reader for a paying account, or a customer update may unintentionally erase a content preference.
Give every group and field an owner and a plain-language definition. Write down which process adds or removes membership and what the absence of a value means. Use one authoritative customer-status field rather than accumulating groups such as Trial June, Trial July, and Trial final whose meanings overlap.
Choose the trigger after defining membership
MailerLite currently documents both Joins a group and Joins a segment triggers. For a group-triggered workflow, check whether re-entry is enabled and what should happen when membership changes. For a segment-triggered workflow, the documentation explains that subscribers can leave the flow when they stop matching its conditions.
Also distinguish a subscriber naturally meeting a rule from an editor changing the segment definition. MailerLite documents different behavior for new members introduced by editing an active segment's filters. Verify the applicable trigger and plan in the current editor rather than assuming that every way of entering a list starts the same sequence.
Walk through a subscriber before activating the workflow
Use a test subscriber and a draft sequence. Request the worksheet, change the topic preference, and update the customer state. Inspect membership and workflow activity after each change. Your expected result should identify the intended message and the reason the subscriber qualifies for it.
Then repeat the request and remove the qualifying condition. Decide whether another request should resend the material, whether a purchaser should leave a promotion sequence, and who investigates a failed update from the product. Those are business decisions to document before activating messages for the real list.
- New qualifying subscriber enters the intended workflow.
- An existing member does not accidentally start duplicate sequences.
- Loss of the qualifying condition has the intended effect.
- Re-entry matches the promise made to the reader.
- An unsubscribe or suppression is not treated as a new permission to send.
Should you use groups or segments for a signup form?
Use an explicit group when the form records an intentional request or topic choice, then build segments for changing audiences you want to derive from that information. Confirm the form's group assignment and the automation trigger together. Receiving the form submission and entering the intended sequence are separate results to verify.
Does removing a group delete its subscribers?
MailerLite states that deleting a group or segment removes the list itself, while its subscribers remain in the account. Treat audience cleanup and subscriber deletion as different operations. Before changing an actively used group, inventory the forms, integrations, campaigns, and workflows that depend on its membership.
Sources and editorial method
Official sources linked in this guide were checked on October 28, 2026. Recommendations and fictional examples are editorial analysis, not hands-on product tests or customer results. Features, prices, and plan limits can change; confirm the current documentation before choosing a plan or implementing a workflow.