The Workflow Library

Library / Lead nurturing / lead-nurturing-042

Franchise or territory localized content nurture

Lead nurturingContactMarketing Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A contact's nurture emails automatically reference the right local franchise or territory, pricing, and contact details instead of a generic head-office version that does not match who will actually follow up.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-042
flowchart TD
    A[On franchise audience, territory known] --> B{nurture_territory value}
    B -- North --> C1[Send: North intro]
    B -- South --> C2[Send: South intro]
    B -- East --> C3[Send: East intro]
    B -- West --> C4[Send: West intro]
    B -- International --> C5[Send: International intro]
    C1 --> D[Delay 4 days]
    C2 --> D
    C3 --> D
    C4 --> D
    C5 --> D
    D --> E[Send: shared follow-up]
    E --> F[Set territory_nurture_completed = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse when the business operates through franchises, dealers, or territories where the local unit has its own contact details, promotions, or pricing that should appear in nurture content.
  • UseUse when a territory property is already reliably set on the contact (from a form field, a zip code lookup, or manual assignment).
  • SkipDo not use this if there are more than roughly 6-8 territories; branching content that many ways inside one workflow gets unwieldy. Past that, a custom-coded lookup or Data Hub Professional's data tools that assemble the local details into a single set of tokens is more maintainable. *(check in your portal: 2026 tooling recommendation for high-cardinality localized content beyond simple if/then branching)*
  • SkipDo not use this pattern for anything requiring different legal disclaimers by region; get that reviewed separately from marketing content localization.
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.2 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.9 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.