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.
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

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.
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.





