Outcome. A single form submission routes automatically to the correct legal basis and follow-up path based on whether the contact is in the EU, instead of applying one blanket consent flow to everyone regardless of region.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-025
flowchart TD
A[Form submitted] --> B{Country in EU/regulated list?}
B -->|Yes| C{Consent checkbox checked?}
C -->|Yes| D[Set legal_basis_type = Consent, set consent_capture_date]
C -->|No| E[Set legal_basis_type = Not applicable, no marketing list add]
B -->|No| F[Set legal_basis_type = Legitimate interest, standard list add]
When to use it, when not to
- UseUse when you run one global form for a lead magnet or newsletter and need EU submissions to go through explicit consent capture while non-EU submissions can proceed under a lighter-touch basis.
- UseUse when your legal guidance distinguishes EU (and other similarly regulated regions, if applicable) from the rest of your audience for consent purposes.
- SkipDo not use this fiche as your source of truth for which countries count as "EU" for legal purposes; that list must come from your legal or compliance team and be kept current as regulations or your risk posture change. (check in your portal: exact country list to treat as EU/regulated for your organization, this is a legal determination, not a technical one)
- SkipDo not use if you already run fully separate forms per region. This fiche solves the single-form, mixed-audience case.
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.4 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.7 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.
