An unsubscribed contact is a recipient who has asked to stop receiving a particular class of subscription or marketing email. The system should persist that request and prevent covered future marketing sends unless the recipient later gives a valid new subscription or the applicable rules and product policy support another lawful state change.
UnsubscribedWhat does unsubscribed mean? A marketing preference state, not a dead email address
The crucial distinction is that unsubscribed is a preference/permission state. It is not the same as bounced, complained, invalid, deleted, or globally unreachable.
Unsubscribe scope matters
“Unsubscribe me” can mean different scopes depending on the message and preference model:
- one newsletter
- one promotional list
- all marketing from a store
- a specific product-alert subscription
- all subscription email associated with an account
For standards-based one-click unsubscribe, the URL carried in the message identifies the recipient and the list/subscription to remove. The protocol does not invent your preference hierarchy for you.
The UI and data model should make the effective scope understandable. Ambiguity is dangerous because a recipient who expects “stop all promotions” may continue receiving another stream that the system considered separate.
Unsubscribed does not necessarily mean “never send any email”
A person can unsubscribe from marketing and still require non-subscription messages such as a password reset or receipt. Google's current subscription guidance explicitly distinguishes subscription messages such as marketing/newsletters from non-subscription messages such as password resets and receipts, and recommends separate sending addresses for those classes.
For U.S. CAN-SPAM purposes, properly transactional/relationship messages are treated differently from commercial marketing messages. But the exact rules depend on message purpose and jurisdiction. So an ecommerce system should not model:
unsubscribed = block every possible email forever transactional = ignore every suppression reason
The correct behavior depends on message purpose + preference scope + suppression reason + applicable rules.
Unsubscribed is one fact among four
Re-importing a contact must not silently erase an unsubscribe
One of the most common data-quality failures is:
- contact unsubscribes
- email is exported to a CSV
- a later import includes the same address
- import code defaults
subscribed=true - marketing resumes
The import changed profile data, but the recipient never changed their preference. An unsubscribe should therefore be durable across ordinary profile updates, segmentation, list movement, and imports. A new marketing subscription should come from a deliberate resubscription path, not incidental data synchronization.
A purchase is not automatically a resubscription
A person who opted out of promotions can later place another order. The order may justify necessary transactional messages about that order, but it does not by itself prove that the person asked to resume marketing. Keep these events separate:
purchase event → order/transaction statenewsletter opt-in → marketing subscription stateunsubscribe → marketing suppression state
Combining them creates “zombie subscribers” whose marketing status changes because unrelated commerce events occurred.
Resubscription should be explicit and auditable
If a recipient later chooses to subscribe again, record enough context to explain the state change:
- timestamp
- source/form/workflow
- subscription scope
- consent text/version where relevant
- address/account identifiers
- evidence required by applicable rules
The goal is not paperwork for its own sake. It is being able to answer: why did this person start receiving marketing again after previously opting out?
What passes and what does not
- Several events can all cause an email platform to stop sending, but for different reasons
- The suppression record stores why a recipient is suppressed instead of flattening all of these into one “inactive” boolean
Common mistakes
- Treating unsubscribe as the same thing as hard bounce
- Deleting the profile and losing the suppression history
- Re-enabling marketing on CSV import
- Treating a new purchase as automatic marketing resubscription
- Applying newsletter unsubscribe to a password reset without considering message purpose
- Ignoring an unsubscribe because another list or automation stores its own state
- Hiding the scope of the unsubscribe from the recipient
Comparison
Separate the states that look like “do not send”
| Option | State | Why sending stopped | What it tells you |
|---|---|---|---|
| Unsubscribed | Unsubscribed | Recipient asked to stop a marketing/subscription stream | Preference/permission |
| Hard bounced | Hard bounced | Recipient server returned a permanent delivery failure | Address/delivery problem |
| Complained | Complained | Recipient/provider reported spam | Strong negative feedback |
| Suppressed | Suppressed | System-level rule prevents a send | Control layer; reason can vary |
| Deleted | Deleted | Profile was removed from a database | Storage state, not necessarily permission history |
Questions we get asked
Is an unsubscribed contact the same as a suppressed contact?
Not exactly. Unsubscribed describes the recipient's preference state. Suppressed describes a sending control. An unsubscribe commonly creates a suppression, but suppression can also result from bounce, complaint, or other policy reasons.
Can I still send an order receipt to someone who unsubscribed from marketing?
A marketing unsubscribe and a necessary transactional message are different categories. Google, for example, distinguishes subscription mail from receipts/password resets. Apply the rules relevant to the message and recipient rather than treating the marketing opt-out as either meaningless or universally blocking.
Can I delete an unsubscribed contact?
You may have data-retention reasons to remove profile data, but your system still needs a way to avoid forgetting an opt-out and accidentally re-subscribing the address on a later import. The exact retention design depends on your legal and privacy obligations.
How quickly should unsubscribe take effect?
Operationally, as quickly as practical. Current Gmail subscription guidance says within 48 hours; U.S. CAN-SPAM guidance says within 10 business days for covered commercial opt-outs. Other rules may differ.
Does clicking unsubscribe mean the address is invalid?
No. The address can be perfectly deliverable. The recipient is telling you about messaging preference, not mailbox existence.
OnVoard's take
Never throw away the reason behind “do not send.”
Unsubscribed, hard-bounced, complained, and administratively suppressed can all end in a blocked marketing send, but they represent different facts and different recovery paths. Preserve those facts independently so imports, automations, and transactional messaging can make the right decision later.
Every app on every plan. Connect your store and switch on the flows in an evening.