Short answer

A group holds subscribers who were assigned to it through an action, such as a manual selection, a form, an automation or a supported integration. It has no saved membership rule that continually decides who belongs. A segment is defined by saved filter conditions and its membership updates as subscriber data starts or stops matching those conditions.

That means a subscriber can stop appearing in one segment without being deleted from the MailerLite subscriber database. These terms apply to New MailerLite. MailerLite Classic has its own help center and interface.

Original conceptual diagram: groups compared with segments Group membership changes after an assigned action. Segment membership follows saved matching conditions, such as source equals SEO AND buyer equals no. This is an illustration, not a MailerLite screenshot. GROUP SEGMENT Assigned by a person, form, integration or automation Assigned membership No continuing filter rule Saved rule determines who currently qualifies source=SEO AND buyer=no Membership updates with data
Original conceptual illustration—not a MailerLite interface screenshot. Filter words in the diagram are fictional example fields.

Which should you use?

Desired outcome Usually choose Why
Keep a named collection of people assigned by a signup form or other supported action Group Membership is assigned, rather than calculated by a standing filter
Show subscribers who currently meet several field or activity conditions Segment Saved conditions determine who qualifies
Maintain a saved view of recent signups Segment A rolling date filter can automatically stop matching older records
Manually add an eligible contact to a particular collection Group Groups allow assigned membership

A safe example: SEO contacts who have not purchased

Imagine two illustrative custom fields, acquisition_source and buyer. Neither is guaranteed to exist as a default field in your account. A segment might ask for both conditions to be true:

Condition A

acquisition_source = SEO

Condition B

buyer = no

AND means both conditions must match. OR would allow a record to match either condition in this simple, non-nested example. More complex nested filters require reviewing the exact rule arrangement.

Completely synthetic records; not real subscribers or live test outcomes.
Fictional record Source Buyer Matches SEO AND no?
A SEO no Yes
B SEO yes No
C Referral no No

If fictional record A later changes to buyer = yes, it no longer meets the example segment rule. That does not, by itself, delete the record from the account or remove it from unrelated groups.

Why might a subscriber appear to be missing?

  1. First distinguish segment membership from subscriber status or account deletion. They are not the same event.
  2. Consider whether a subscriber was ever assigned to the group. Matching a field alone does not automatically assign membership to a group.
  3. Read the saved segment's AND/OR logic carefully, including any additional group filters, time windows or custom-field values.
  4. Look for rolling date conditions; their matches can change without anyone deliberately removing a contact.
  5. Respect contact consent, unsubscribed status and suppression: do not re-import or re-subscribe somebody just to diagnose a count.
Important: This is an educational explanation, not a tested current UI procedure. Do not make changes to a production list based solely on the fictional example. MailerLite's settings, available features and interface may vary by plan and change over time.

Check your understanding

Can a record belong to a group but fail to qualify for a segment? Yes. Can a record stop matching a segment without leaving the overall subscriber list? Yes. Would changing the segment filter itself automatically create new group assignments? No. The saved group and segment mechanisms are different.

Open the ungated group/segment decision worksheet →

Evidence, dates and limitations

Evidence type: Official vendor documentation, source-checked October 17, 2026. The primary conceptual guide was last edited by MailerLite on June 12, 2026. Earlier controlled-account observations from a separate research project were archived, but this article does not present those observations as a current Software Help HQ test. No current account access or current MailerLite screenshots were used for this guide.

Version: New MailerLite, not MailerLite Classic. The article does not verify every plan-specific feature, current screen label or subscriber-management procedure. For operational account changes, read current vendor help and protect real subscriber consent and status.

Official source documentation

Software Help HQ is independent and is not affiliated with or authorized to act as MailerLite support. Product names identify the software discussed. No referral compensation is associated with links in this guide.