An unsubscribe is only useful if every connected system respects it
An unsubscribe needs to stop the relevant marketing across every connected system that can send or re-add the contact. Define the preference scope, record the request, propagate the suppression and test imports and automations against it. A working link in one platform is only part of the process when a CRM, another audience or a later spreadsheet can change eligibility.
Put the advice into practice
Give the first enquiry a useful follow-up
Plan campaigns, nurture and customer emails with clear triggers and review.
Plan your email programmeDefine what the request changes
Start with the wording presented to the recipient. Is the action an unsubscribe from a particular publication, a preference change or a stop to all marketing from the organisation? The systems should apply the meaning the person was given, rather than quietly interpret a broad request as a narrow tag change.
Keep marketing preferences distinct from operational relationship information. A customer may still have an active engagement after opting out of marketing. Classify service communications according to their actual content and purpose; do not use an operational label to bypass a marketing preference or attach unrelated promotion automatically.
ACMA’s unsubscribe guidance says commercial-message unsubscribe options must be clear, honoured within five working days and functional for at least 30 days after sending. They must not require a login, extra personal information or a fee. Design the process to act promptly rather than treat the outer deadline as a routine waiting period.
Trace every route that can change sending eligibility
| System or route | Required behaviour | Test case |
|---|---|---|
| Sending platform | Apply the relevant unsubscribe state and stop eligible marketing | Use an approved test address to complete the real preference action |
| CRM connection | Carry the preference without overwriting it from a stale record | Change another CRM field and confirm suppression remains |
| Additional audiences or platforms | Respect the intended organisation-wide or publication-specific scope | Check the same approved test record in each relevant destination |
| Spreadsheet import | Preserve suppression instead of treating every row as newly subscribed | Import a controlled record with a prior unsubscribe |
| Automations and queued messages | Check the current eligibility and relevant stopping rules | Confirm the opted-out test record does not receive the marketing step |
The map should identify a responsible owner for each connection and for the process as a whole. A suppression field that exists but is not consulted by a sending rule is not an effective control.
Check what the platform does across audiences
Mailchimp’s import documentation states that it excludes duplicate, bounced and unsubscribed addresses already stored in an existing audience, but audiences are independent and it cannot detect those states across separate audiences. That is a concrete reason to inspect the architecture rather than assume an account-wide protection.
Review the actual integration direction. A platform may send an unsubscribe state to the CRM, while an older CRM value later writes a subscribed state back. Decide which event takes precedence, how conflicts are handled and whether a renewed subscription requires a supported permission process. Do not infer consent from a routine data update.
Retain the minimum suppression evidence needed under the organisation’s approved data-handling and retention practices. Removing the only record of an opt-out can make a later import look like a new contact. At the same time, suppression does not justify keeping unrelated personal information indefinitely. Assign that retention decision to the responsible owner.
This review concerns legitimate communication preferences. It should not be used to weaken authentication or expose contact data while connecting systems.
Test the path that could accidentally re-add a contact
Consider a hypothetical organisation using one newsletter platform and a CRM export. A reader unsubscribes successfully, but the next monthly export contains an older subscribed value. If the import is allowed to overwrite the current preference or feeds an independent audience without the suppression, the person may be included again.
A useful test follows an approved record through that exact sequence: unsubscribe, verify the recorded state, run the controlled connection or import and inspect the final sending eligibility. Include queued automations where they form part of the process. Do not test by sending unwanted marketing to a real recipient.
Monitor integration failures and exceptions. If a preference update cannot reach another system, record the failure, prevent the relevant send where possible and assign a person to resolve it. An integration diagram is incomplete without a plan for a connection that is temporarily unavailable.
Review the map after adding a new form, audience, CRM field or sending tool. Our guide to respectful personalised marketing provides the relationship context; the suppression map makes that principle operational across the tools.
List every system that can send marketing or write a subscription status, then test one approved unsubscribe through the complete path. Include the result in an email systems review.
