Unsubscribe / subscription type suppression sync across marketing sends

Outcome. A contact who unsubscribes from any single subscription type, or asks to stop all marketing contact through another channel, is fully tracked and suppressed in one unified place, not left as a scattered record of separate opt-outs.

flowchart TD
    A[Subscription status changes OR manual request checked] --> B{Native subscription type = Unsubscribed?}
    B -->|Yes| C[Add to unified unsubscribe list]
    C --> D[Notify marketing ops]
    A --> E{Manual unsubscribe request = on?}
    E -->|Yes| F[Set all subscription types: Unsubscribed]
    F --> G[Add to Do-not-email list]
    G --> D

When to use it / when not to

• Use when you run several subscription types (Newsletter, Product updates, Events...) and contacts can be unsubscribed from one but stay opted in to others, per HubSpot's default one-click unsubscribe behavior.
• Use when a manual "please stop emailing me" request comes in outside the email footer link (support ticket, reply email, phone call) and needs the same treatment as a native unsubscribe.
• Do not use this to handle full GDPR erasure requests. That is a separate, heavier obligation, see marketing-ops-017.
• Do not build this if you only send one type of marketing email. The native all-emails opt-out already fully suppresses sends; add this workflow once you have multiple subscription types to keep in sync.