The Workflow Library

Library / Marketing ops / marketing-ops-043

Consent renewal re-permission campaign before expiry

Marketing opsContactMarketing Hub ProfessionalAdvanced~55 min to buildFull spec

Outcome. Contacts whose consent has a defined expiry date get a re-permission request campaign ahead of that date, so consent lapses through an intentional yes-or-no answer, not silently through inaction that leaves the legal basis unclear.

Workflow map Enrollment, branches and actions at a glance marketing-ops-043
flowchart TD
    A[Consent expiry date is 30 days out] --> B[Set status = Requested, send renewal request]
    B --> C{Wait until Renewed, expire 20 days}
    C -->|Expired| D[Send reminder email]
    D --> E{Wait until Renewed, expire 10 more days}
    E -->|Expired| F[Set status = Lapsed, set non-marketing]
    C -->|Renewed| G[Reset consent_expiry_date forward]
    E -->|Renewed| G
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse in jurisdictions or internal policies where consent is treated as time-bound, a common practice even where not strictly mandated, often 12 or 24 months, and needs active renewal rather than assumed indefinite validity.
  • UseUse alongside marketing-ops-020's legitimate interest annual review, for portals tracking multiple legal bases.
  • SkipDo not use if the legal basis for the relevant contacts is not consent-based, for example legitimate interest or contract. Renewal campaigns are a consent-specific concept, not universal across legal bases.
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.3 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.12 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.