The Workflow Library

Library / Lead nurturing / lead-nurturing-044

A/B tested nurture email path

Lead nurturingContactMarketing Hub ProfessionalAdvanced~45 min to buildFull spec

Outcome. A nurture sequence randomly splits contacts between two email variants at a key step, so the team can measure which version performs better before committing to one for the rest of the audience.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-044
flowchart TD
    A[On A/B test audience] --> B{Randomly split 50/50}
    B -- Path A --> C1[Set variant = A]
    C1 --> D1[Send: Variant A]
    B -- Path B --> C2[Set variant = B]
    C2 --> D2[Send: Variant B]
    D1 --> E[Delay 3 days]
    D2 --> E
    E --> F[Send: shared follow-up]
    F --> G[Set ab_test_nurture_completed = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when there is a genuine open question about which subject line, CTA, or content angle performs better, and enough enrollment volume to reach a meaningful sample size within a reasonable time.
  • UseUse as a temporary structure: run the test, read the results, then simplify the workflow back down to a single winning path once a decision is made.
  • SkipDo not use this for low-volume nurture tracks (under roughly 200 enrollments over the test period); the split will not produce a reliable read, and the added complexity is not worth it.
  • SkipDo not test more than one variable at a time inside the same split (do not vary subject line and CTA and send time all at once); isolate the variable to know what actually drove the difference.
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.8 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 lead nurturing 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.