Consent withdrawal cascades to suppress from active lists and stop nurture

Outcome. The moment a contact withdraws consent, whether through a subscription unsubscribe or a manual request, the withdrawal cascades to a shared suppression list and force-unenrolls them from the specific nurture workflows named here, instead of leaving them mid-flight in a sequence that a single opt-out never touched.

Workflow map Enrollment, branches and actions at a glance marketing-ops-014

flowchart TD
    A[Subscription unsubscribed, manual request, or non-marketing set] --> B[Set consent_withdrawn_date]
    B --> C[Add to Global nurture suppression list]
    C --> D{Enrolled in Welcome nurture?}
    D -->|Yes| E[Unenroll]
    C --> F{Enrolled in Re-engagement nurture?}
    F -->|Yes| G[Unenroll]
    C --> H{Enrolled in Product update drip?}
    H -->|Yes| I[Unenroll]
    E --> J[Add to unified unsubscribe list]
    G --> J
    I --> J
    J --> K[Notify marketing ops with cascade summary]

When to use it, when not to

• UseUse once marketing-ops-004 (unified unsubscribe tracking) is live and you have found that contacts still receive one or two more nurture emails after unsubscribing, because the nurture itself only checked eligibility at enrollment.
• UseUse when you can name the specific active nurture and broadcast workflows that need a forced unenroll step, and are willing to keep that list current as new nurtures launch.
• SkipDo not expect this workflow to reach into a workflow built after this one without being updated. There is no native "stop everything, everywhere" action; every workflow this fiche should protect has to be named explicitly, both here and in its own suppression list configuration.
• SkipDo not use this in place of setting each nurture workflow's own suppression list correctly. This fiche's shared list only works if every relevant nurture also lists it as a suppression source.