Contacts

This article describes the legacy Contacts screen for accounts awaiting the unified audience migration. Migrated accounts use the Subscribers catalog: one profile, separate consent for each newsletter, and newsletter-owned groups. Their old /contacts links open that catalog.

Statuses

The Contacts page lists the open newsletter's contacts, newest signups first. Filter them by status, or search by email address.

Segments

A segment picks some of your contacts with a few conditions, and keeps up to date as they change. The Contacts page shows each one as a card with its count: click it to list its contacts, and the export follows. New segment opens the editor, with a few starting points:

• Engaged: opened in the last 30 days.
• New: signed up in the last 30 days.
• Inactive: missed at least 5 issues in a row.
• Never opened: never opened and signed up more than 30 days ago.

Conditions can be on opens and clicks, issues missed in a row, the number of emails opened, the signup date, where they signed up (the signup form, an import, by hand or the API) and the email address, 10 at most. A segment matches all of its conditions, or any of them. In the send step, pick one to send an issue to its contacts only. Who gets it

Counts are of active contacts, the ones an issue goes to. Conditions on dates count back from now, so “opened in the last 30 days” follows time, and a send reads its segment when it goes out. A segment that a scheduled or sending issue goes to can't be deleted until that issue goes elsewhere.

Adding someone by hand

Click Add a contact and type their email address. This organizes the address without granting consent or sending an email. A new address stays pending; an existing recipient keeps their account-wide consent state.

For a whole list, import a CSV file instead: Importing contacts.

Changing a status, and deleting

Each contact's menu, at the end of their row, has what applies to them:

• Mark as active restores a dormant projection only while the recipient still has active account-wide consent.
• Mark as dormant stops issues to an active contact without unsubscribing them, as the list cleanup does. Mark them active again any time.
• Unsubscribe withdraws marketing email consent for the whole account. An attempt already authorized may still reach the provider; a withdrawal cannot recall it.
• Delete contact removes them with their dates and engagement, and can't be undone. For someone who unsubscribed, bounced or complained, ApresMail keeps a scrambled trace of the address, so adding it again never emails it. Deleting the last newsletter projection also withdraws consent, so adding the address again cannot restore sending.

Bounced and complained contacts keep their status: their address can't receive email, or they marked one of your emails as spam. No email goes out when you change a status. The API and AI assistants can change statuses too, with the same rules.

Exporting

Export downloads the contacts that match your filters as a CSV file. Its columns go back in through the import as they are, so it's also a backup.

Addresses no one can reach

When an address hard bounces or turns out to be a spam trap, ApresMail remembers it for every sender: imports and signups leave it out, and sends skip it, showing the contact as bounced. A bounced address is remembered for 180 days, a spam trap for good.