Contacts, Groups, and Segments

Mailyard Pro keeps one deduped contact pool — every contact exists once, identified by email address — and gives you two ways to organize it: groups and segments. There are no contact limits.

Groups — static lists

A group is a list you place contacts into: “Customers”, “Newsletter”, “Beta testers”. A contact can belong to any number of groups. You can add or remove groups inline from the contact panel, or use bulk actions on selected contacts — add to a group, remove from a group, change status, or delete — straight from the selection bar. Group chips show on every contact row, and a multi-select Groups filter narrows the list to everyone in any of the chosen groups.

Segments — saved filters, evaluated at send time

A segment is a saved contact filter: filter the Contacts list (by group, status, source, customer type, and so on), click “Save as segment”, and that filter becomes a sendable audience. Membership is dynamic — it’s re-evaluated when a campaign sends — so a segment like “paid customers” always means current paid customers, and the preview count always matches exactly what goes out.

Targeting a campaign

On the review and send steps, a campaign targets everyone, one group, or one segment. That’s the whole audience model — no separate tag system to reconcile.

Importing contacts (CSV)

The import wizard handles real-world CSVs:

• Automatic column mapping — first name, last name, email, and other fields detected from your headers, with a confirmation step; map any column to a custom contact field, created inline if needed.
• Conditional import rules — “if a column matches X, then add to group / set status / set source”.
• Suspicious-address detection — flags localhost, test/example, no-domain, and disposable emails, with a skip option.
• Full RFC-4180 CSV parsing — quoted commas and BOM handled correctly, with async chunked import and a live progress bar for large files.

List hygiene runs itself

Unsubscribes, hard bounces, and spam complaints (reported back by Mailyard’s bounce tracking) automatically land contacts on the suppression list, and every broadcast carries a one-click unsubscribe header (RFC 8058). Bad addresses get caught instead of quietly wrecking your sender reputation — you don’t have to manage any of this by hand.