Mailchimp Tags vs. Groups vs. Segments: What Actually Separates Them
A tag is a free-form label you apply to a contact by hand or through automation. A group is a predefined category a contact picks (or gets assigned to) within a signup form, often used for self-selected preferences. A segment is a saved filter built from any combination of tags, groups, and other properties, re-evaluated automatically. All three can only act on data that already lives on the contact record.
How tags, groups, and segments actually differ
Tags are the loosest of the three: type a new one and apply it, no setup required beforehand. They're good for ad hoc labeling, flagging a VIP customer, marking someone as a webinar attendee, without building a whole preference structure first.
Groups require upfront setup: you define the categories (say, "Interested in: Product A / Product B / Product C") and they typically show up as checkboxes on your signup form, letting a contact self-select which ones apply. They're built for structured preference capture, not quick ad hoc labeling.
A segment doesn't hold contacts directly, it's a saved filter: "tagged VIP AND in the Product A group AND opened an email in the last 30 days," for instance. Build the filter once and Mailchimp keeps the matching list current on its own, unlike a static export that goes stale the moment anything changes.
You can create a segment inside Audience > Segments, picking any combination of tags, group membership, engagement history, or other contact properties as filter conditions.
The limit underneath all three
A segment's filter can only check fields that are already on the Mailchimp contact record. If your real segmentation logic depends on something living in another system, a loyalty tier, a support ticket count, lifetime order value from an accounting platform, the segment builder has nothing to filter on until that value gets synced onto the contact as a merge field or tag first.
This is the same underlying gap our Mailchimp integrations work → addresses from the data side: get the real number onto the contact record, and the segment you've already built starts filtering on something that's actually true.
What that looks like built out
Tags applied automatically from real account data
A customer's lifetime value, support history, or subscription tier from your actual systems lands as a tag or merge field, so a segment built around it reflects reality instead of a guess.
Segments that stay accurate without a manual re-tag
Instead of someone periodically exporting a list and re-tagging contacts by hand, the sync keeps the underlying fields current, so the segment's own automatic re-evaluation does the rest.
What does your segment actually need to know that Mailchimp doesn't have?
If the real answer lives in another system, that's a sync, not a reason to build the segment on a guess.
Building segments around data that only exists in a spreadsheet somewhere?
Tell us what your segment is really trying to filter on, and where that number or status actually comes from. We'll get it onto the contact record so the segment can do its job. Segmentation is one example; n-frames automates whatever's manual anywhere in your business.
Let's talk