The Workflow Library

Library / Marketing ops / marketing-ops-037

Marketing contact status sync with per-subscription-type opt-outs

Marketing opsContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A contact who has opted out of every subscription type gets set to non-marketing automatically, so you stop paying for marketing contact seats on people who can no longer be reached by any send.

Workflow map Enrollment, branches and actions at a glance marketing-ops-037
flowchart TD
    A[Subscription type status changes] --> B{All subscription types opted out?}
    B -->|Yes| C{Currently Marketing contact?}
    C -->|Yes| D[Set marketing contact status: Non-marketing]
    D --> E[Notify marketing ops]
    C -->|No| F[No action]
    B -->|No| F
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse on portals with more than one subscription type (newsletter, product updates, events, and so on) where a contact can decline all of them individually without anyone noticing they are functionally unreachable.
  • UseUse to keep marketing contact spend aligned with actual reachability.
  • SkipDo not use if you run a single subscription type. marketing-ops-004's unsubscribe sync already covers that simpler case.
  • SkipDo not use this to set marketing contact status back up automatically on re-opt-in. Route reactivation through marketing-ops-016's approval gate instead, since re-adding marketing contacts has a direct cost.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.2 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.4 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the marketing ops pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.