Outcome. An EU-region contact who fills in a signup form only counts as fully opted in after they click a confirmation link in a follow-up email, giving a documented double opt-in instead of a single unverified form submission.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-008
flowchart TD
A[EU contact created, no double opt-in status] --> B[Set status: Pending, set sent date]
B --> C[Send Confirm your subscription email]
C --> D[Add to EU pending list]
D --> E[Delay 7 days]
D --> F{Clicked confirmation link?}
F -->|Yes, any time| G[Set status: Confirmed]
G --> H[Remove from EU pending list]
E --> I{Status still Pending after 7 days?}
I -->|Yes| J[Set status: Expired]
J --> K[Remove from EU pending list]
K --> L[Set non-marketing or hold from nurture]
I -->|No, already Confirmed| M[No action]
When to use it, when not to
- UseUse when your compliance policy, or a specific market you sell into, expects double opt-in evidence for marketing consent, not just a single form checkbox.
- UseUse for net-new EU/EEA/UK signups specifically. It adds friction and a real drop-off step, so reserve it for the audience where the documentation actually matters.
- SkipDo not use it for existing customers or contacts who already have a documented legal basis through another channel (see marketing-ops-007). Re-confirming consent you already hold creates confusion, not compliance.
- SkipDo not use it as your only legal-basis control. Pair it with marketing-ops-005 for the underlying EU legal-basis gate; this fiche only adds the confirmation-click evidence on top.
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.5 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.10 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.
