Learning path · Level 8 · Tutorial 3

Map Welcome, Nurture, and Post-Purchase Automations

Map compact welcome, nurture, and post-purchase workflows with clear entry, timing, branching, and stopping rules. Validate them through fictional contact walkthroughs without requiring paid automation features or an integrated store.

  • Level: Intermediate
  • Duration: 25 min
  • 8 steps
Start tutorial Back to the path
Map Welcome, Nurture, and Post-Purchase Automations

What you will go through

  1. Choose the Lifecycle Purpose and Entry Event Choose a lifecycle purpose and the event that should begin its contact-specific workflow. 2 min
  2. Build a Testable Workflow Specification Turn lifecycle ideas into compact workflow specifications with explicit checks, branches, holds, and endings. 3 min
  3. Check What the Workflow Can Actually Know Identify the minimum evidence behind workflow triggers and conditions, and route unresolved required data safely. 3 min
  4. Map a Welcome Sequence That Keeps the Signup Promise Create a compact Welcome workflow for Northstar Paper, from confirmed signup through safe completion or an early exit. 3 min
  5. Map Nurture Around One Decision Barrier Build a finite Nurture workflow for Northstar Paper that addresses the declared Routine fit barrier and stops safely when purchase status or relevance changes. 3 min
  6. Separate Post-Purchase Service from Marketing Separate confirmed-order service actions from consent-dependent post-purchase marketing in a compact workflow map. 3 min
  7. Resolve Overlap, Frequency, and Re-entry Add shared controls that prevent duplicate enrollment, conflicting lifecycle messages, and sends based on outdated eligibility. 4 min
  8. Validate and Finish the Three Workflow Maps Trace fictional contacts through three lifecycle workflow maps, repair unsafe paths, and finalize internally consistent specifications. 5 min

What you will learn

  • Create a text-based workflow for each lifecycle purpose, specifying triggers, delays, conditions, message purposes, exclusions, and exits.
  • Identify which subscriber or purchase data each workflow needs and what remains unavailable without a suitable integration.
  • Prevent conflicting messages through send-time permission checks, sequence priorities, frequency limits, and re-entry rules.
  • Separate operational post-purchase messages from promotional follow-ups that require appropriate marketing eligibility.
  • Trace fictional contacts through the workflows and correct missing branches or unsafe continuation rules.

Before you start

  • Design a Permission-Based Email List
  • Draft an Accessible Email Campaign
  • Map a Customer Journey and Marketing Funnel
  • Review Product Pages, Carts, and Checkout

Step 1 of 8

Choose the Lifecycle Purpose and Entry Event

Choose a lifecycle purpose and the event that should begin its contact-specific workflow.

Recognize the starting model

Campaign or lifecycle workflow?

A one-time campaign is planned around a selected send occasion: for example, one announcement to a chosen audience on a particular date.

A lifecycle workflow is different. Each contact enters when a relevant event happens, then can continue over time. The map is about the contact’s path, not one shared send date.

For Northstar Paper, start by naming one purpose and the event that begins that purpose.

Two different sending models

A comparison of one calendar-based send to a group versus separate contacts entering timelines after individual events.

A campaign begins with a chosen occasion; a lifecycle workflow begins separately for each contact when an event occurs.

Pair each purpose with an event

Purpose determines the entry event

Choose the lifecycle purpose before drawing a workflow:

  • Welcome establishes the signup relationship and begins delivering the promise of planning tips and product updates.
  • Nurture helps a contact work through one known decision barrier. Here, the barrier is Routine fit: uncertainty about fitting weekly planning into an existing routine.
  • Post-Purchase supports the customer relationship after a confirmed order.

Each purpose needs an explicit entry event: something that happened and can place a contact on that path.

Lifecycle purpose and entry event

Northstar Paper uses these purpose-to-event pairings. They are entry events, not message schedules.

Use one clear event to begin each lifecycle workflow.
WorkflowIntended outcomeEntry event
WelcomeEstablish the signup relationshipSignup confirmed
NurtureAddress Routine fit for a potential buyerWelcome completed
Post-PurchaseSupport the customer after an orderPurchase confirmed

Use records without a live tool

State is not an event

A segment or record value describes a current state. It does not say when a contact should enter a workflow.

For example, “Marketing eligibility: Eligible” tells you a current status. It is not an entry event. “Signup confirmed” records that something happened, so it can identify an enrollment moment.

Likewise, “Purchase status: No confirmed purchase” is a state; it does not establish a start time for Nurture. An event such as Welcome completed can do that.

Example

Plan with fictional records

You can plan and test these maps in a document—no activated automation tool or connected store is required. Use fictional contact-event records to make the starting point visible.

Example record:
Contact A
Hour 0: Signup confirmed
Marketing eligibility: Eligible

The event gives Welcome a possible start. The eligibility value is a contact state that will matter when the map is developed further.

Practice: identify the right starting point

Classify the purpose or record

Match each Northstar Paper scenario to the most accurate label.

Tap an item and then its matching pair.

Step 2 of 8

Build a Testable Workflow Specification

Turn lifecycle ideas into compact workflow specifications with explicit checks, branches, holds, and endings.

Name every part of the path

From an idea to a testable workflow

A workflow specification is a testable set of instructions—not just a list of messages. It states what starts enrollment, what information is needed, when a decision is due, and what happens for every relevant outcome.

Use the same headings each time so another person can trace the workflow without guessing. A path should always show where it stops, pauses for missing information, or may later begin again.

The specification headings

Use these headings in every workflow specification.

A compact specification makes the workflow reviewable before any tool is configured.
HeadingWhat it defines
TriggerThe entry event that starts evaluation.
Entry checksWhether enrollment is appropriate now.
Data neededRecords required for decisions.
TimingEntry-relative proposed due times.
ConditionsQuestions that branch the path.
Message purposesWhy each message exists, not full copy.
ExclusionsWho or what must not receive a path.
Exit rulesHow the current sequence ends or pauses.
Re-entryWhether a later event may enroll again.

How the pieces connect

A labeled workflow diagram showing an entry event, entry check, delay, three-outcome decision, message action, endings, and a hold path.

The diagram gives the path; the written specification explains what each shape and branch means.

Make timing and uncertainty explicit

Check twice when timing creates a gap

An entry check answers: “Should this contact enroll when the entry event happens?” A send-time check answers: “Is this scheduled message still appropriate now?”

For example, a contact can pass an entry check at Day 0 and have a different Marketing eligibility record by Day 2. The later check uses the current record. A delay creates a future decision point; it never guarantees that a message will be sent.

Example

Illustrative planning fragment

Trigger
Signup confirmed

Entry checks
Marketing eligibility is Eligible.

Data needed
Marketing eligibility and Welcome status.

Timing
Day 0: enter. Day 2: proposed decision point.

Conditions
At Day 2, check current Marketing eligibility.

Message purposes
Provide the next promised planning-related guidance.

Exclusions
Do not enroll an Ineligible contact.

Exit rules
Ineligible at the later check -> End sequence. Unknown required value -> Hold for review.

Re-entry
State this explicitly in the finished workflow; this short fragment does not assume a rule.

Tip

Unknown is not No

A condition needs an explicit route for uncertainty. Do not treat an Unknown record as either Eligible or Ineligible. “Hold for review” preserves the distinction between missing information and a deliberate sequence ending.

Practice: decide at send time

Apply the later check

A contact passed entry checks as Eligible. At the Day 2 send-time check, Marketing eligibility is now Ineligible. What should the workflow do with the planned Marketing message?

Build the path

Complete a testable skeleton

Complete the missing timing, send-time condition, and two ending outcomes in this workflow skeleton.

markdown
Trigger: Signup confirmed
Entry checks: Marketing eligibility = Eligible
Data needed: Marketing eligibility
Timing: : proposed Marketing message
Conditions at the proposed time:

  Yes -> Send planned Marketing message -> 
  No -> 
  Unknown -> Hold for review
Re-entry: State explicitly; do not assume it

Step 3 of 8

Check What the Workflow Can Actually Know

Identify the minimum evidence behind workflow triggers and conditions, and route unresolved required data safely.

Name the source for each decision

Evidence before action

A workflow can act only on evidence it can identify. For every Trigger, Entry checks, or Condition, name the record that supplies the answer.

For Northstar Paper, keep the map minimal:

  • a signup confirmation supports Signup confirmed;
  • the current Marketing eligibility supports a marketing send-time check;
  • a declared Decision barrier supports barrier-specific relevance;
  • a Welcome completed event supports Nurture entry;
  • a confirmed purchase record supports Purchase confirmed.

A segment or elapsed time alone is not evidence that an event happened. The record must answer both what happened and, where relevant, when it happened.

Evidence feeds workflow decisions

A diagram shows distinct subscriber and order records feeding event and decision nodes in a workflow.

Each workflow decision needs a specific, identifiable source record.

Minimum evidence for common decisions

Use explicit preferences and confirmed events as planning signals. Do not use an email open as proof of permission, workflow completion, or product interest.

For a purchase-based decision, the minimum reliable evidence is stronger than a click or a waiting period: the record must match the contact to an order, include an Order ID, and show the purchase event time. For example, Order ID: NP-101 can support a purchase only when it is tied to the correct contact and has a recorded confirmation time.

Minimal map records

The fields below are sufficient for this fictional map; collect no extra fields merely because they might be available.

Examples of fields and the decisions they can support.
Record labelExample valueCan support
Marketing eligibilityEligibleMarketing send-time check
Decision barrierRoutine fitNurture relevance
Welcome statusCompletedWelcome completed entry event
Purchase statusConfirmed purchaseConversion or post-purchase path
Order IDNP-101Match a confirmed order to a contact
Last marketing sendDay 0Later scheduling review

Handle missing or stale records safely

Unknown is not a negative answer

No confirmed purchase and Unknown are different records.

Use No confirmed purchase only when a trustworthy, current purchase record was checked and found no matching confirmed order. Use Unknown when the purchase feed is unavailable, stale, or cannot reliably match the contact and order.

Missing information must not quietly become “No.” If an acquisition workflow needs purchase status and that status is Unknown, the affected action goes to Hold for review. It must not continue based on an assumption.

Warning

Safe fallback for unavailable data

Apply the same safety rule to permission. A marketing message needs current Marketing eligibility. If the value is Unknown, do not treat it as Eligible; place the affected action in Hold for review.

A supplied contact-event log can simulate these decisions in a text map. In a real process, an authorized manual check can provide an answer. Neither approach creates a live automated event feed, so the workflow should not pretend that unavailable data will update itself.

Example

Worked record: unresolved purchase evidence

Contact C has this record at a proposed marketing send-time:

  • Marketing eligibility: Eligible
  • Purchase status: Unknown
  • Order ID: unavailable
  • Last marketing send: Day 0

The planned marketing action depends on whether the contact is still on a nonbuyer path. Because purchase status cannot be resolved, the map should route that action to Hold for review, rather than infer that no purchase occurred.

Practice: map evidence to action

Evidence mapping check

Match each workflow decision or situation to its minimum evidence or safe next action.

Choose the evidence or fallback

Match every item to its correct evidence or action.

Tap an item and then its matching pair.

Step 4 of 8

Map a Welcome Sequence That Keeps the Signup Promise

Create a compact Welcome workflow for Northstar Paper, from confirmed signup through safe completion or an early exit.

Anchor the Welcome workflow to signup

Start with a valid welcome entry

A Welcome workflow begins when something happens for one contact: Signup confirmed. It is not triggered merely because someone currently belongs to a segment.

For Northstar Paper, the Day 0 purpose is to acknowledge the signup and deliver on the promise of planning tips and product updates. Before enrollment, check current Marketing eligibility: Eligible can enter; Ineligible ends the sequence; Unknown goes to Hold for review.

Day 0 is the trigger time. Day 2 is 48 hours after that trigger, not two days after a previous send.

The Welcome path at a glance

A flowchart showing Signup confirmed leading through eligibility checks, a Day 0 welcome message, a Day 2 recheck, and either planned completion, an early ending, or a hold.

The delayed message is a proposed action, not a guaranteed send: conditions are checked again when Day 2 arrives.

Specify two purposeful messages

Example

Write the specification beside the map

Use the same headings for the written specification and the diagram. This compact draft describes Northstar Paper’s Welcome workflow:

Trigger: Signup confirmed.

Entry checks: Marketing eligibility must be Eligible. Ineligible contacts go to End sequence; Unknown goes to Hold for review.

Data needed: Marketing eligibility, Purchase status, and Welcome status.

Timing: Day 0 and Day 2, measured from Signup confirmed.

Conditions: Before the Day 2 message, recheck current eligibility and Purchase status.

Message purposes: At Day 0, acknowledge the signup and fulfill the promised planning content. At Day 2, guide a relevant first planning action.

Exclusions: Do not enroll a known Ineligible contact.

Exit rules: A confirmed purchase or loss of eligibility before Day 2 ends this acquisition-oriented route. Unknown required data goes to Hold for review. After the Day 2 message, record Welcome completed, then End sequence.

Re-entry: Not set in this draft; shared rules will be added later.

Tip

Keep the promised purpose relevant

The Day 2 purpose should still fit the signup promise. It can help a contact try a weekly planning action or explore whether the Weekly Planner fits their routine. It should not become an unrelated sales series.

A confirmed purchase changes the contact’s lifecycle relevance. Do not continue an unchanged first-purchase prompt simply because it was scheduled earlier.

Separate a planned finish from a changed path

Compare completion with an early exit

These two paths look similar at entry but have different endings. Contact-event times below use elapsed hours from one shared scenario start.

Two Welcome outcomes

A planned completion is evidence that this Welcome path finished as designed. An early exit is not completion and must not create the Welcome completed event.

Both contacts received the Day 0 message, but only one completed the planned Welcome path.
ContactKey eventsDay 2 outcomeWelcome status
Contact AHour 0: Signup confirmed; Eligible. Hour 48: Eligible; No confirmed purchase.Send the relevant Day 2 message, then end.Welcome completed
Contact BHour 0: Signup confirmed; Eligible. Hour 24: Confirmed purchase.End early; skip the Day 2 acquisition-oriented message.Not completed

Warning

Do not turn missing data into a negative answer

If Purchase status is Unknown at the Day 2 check, do not treat it as No confirmed purchase. Use Hold for review until the required status can be resolved.

Complete and defend the map

Complete the Welcome map

Complete the missing labels in the Welcome workflow map.

markdown
Trigger: 

Entry check:
Marketing eligibility Eligible? -> Yes: Enroll
                                  No: 
                                  Unknown: 

Day 0 -> Marketing message: acknowledge signup and fulfill planning expectations

Day 2 send-time check:
Marketing eligibility Eligible? -> Yes: Purchase status Confirmed purchase?
                                  No: End sequence
                                  Unknown: Hold for review
Purchase status Confirmed purchase? -> Yes: 
                                      No: Send Day 2 Marketing message: guide a relevant first planning action
                                      Unknown: 

After the Day 2 message -> record  -> End sequence

Apply the stopping rules

Contact D and Contact E both entered Welcome at Hour 0 after Signup confirmed while Marketing eligibility was Eligible. At Hour 24, Contact D’s Purchase status becomes Confirmed purchase. At the same time, Contact E’s Marketing eligibility becomes Ineligible. Their Day 2 messages are due at Hour 48.

In 2–4 sentences, state the expected path for each contact and explain why neither should receive the unchanged Day 2 first-action message.

Write at least 80 characters (0/80).

Step 5 of 8

Map Nurture Around One Decision Barrier

Build a finite Nurture workflow for Northstar Paper that addresses the declared Routine fit barrier and stops safely when purchase status or relevance changes.

Gate enrollment by the declared barrier

Start with a relevant entry gate

A Nurture workflow is not a generic stream for every nonbuyer. It addresses one declared reason for hesitation: Routine fit—uncertainty about fitting weekly planning into an existing routine.

Trigger: Welcome completed.

Entry checks: Marketing eligibility = Eligible; Decision barrier = Routine fit; Purchase status = No confirmed purchase.

Data needed: Welcome status, Marketing eligibility, Decision barrier, and Purchase status.

Exclusions: Do not enroll contacts who are Ineligible, have a different or no declared barrier, or have a Confirmed purchase. If Purchase status is Unknown, use Hold for review rather than treating it as no purchase.

Re-entry: Not defined in this step; shared enrollment rules are added later.

The entry event is filtered by current records

A workflow diagram in which Welcome completed enters Nurture only for an eligible contact with Routine fit as the decision barrier and No confirmed purchase as the purchase status.

The entry event starts evaluation; it does not automatically enroll every contact.

Plan a short, barrier-specific sequence

Use two timed purposes, not an endless sequence

Timing: Measure both proposed message times from the Welcome completed trigger. Day 1 is 24 hours after that event. Day 4 is 96 hours after that event—not four days after the Day 1 message.

Message purposes:

  • Day 1 — Marketing: address Routine fit uncertainty with a practical, low-effort way to begin using a Weekly Planner.
  • Day 4 — Marketing: help the contact assess whether the planner fits their routine and take a purchase-related next step.

These are message purposes, not complete email copy. The declared barrier determines relevance: a contact with another barrier should not receive this Routine fit sequence simply because they have not purchased.

A delay is a wait before another decision. Before each proposed Marketing send, check whether current eligibility, barrier relevance, and purchase status still support it.

Entry-relative timing for Nurture

A nurture timeline from Welcome completed at Day 0 to proposed marketing messages at Day 1 and Day 4, with a send-time check before each message.

A scheduled slot is only proposed: a send-time check can stop or hold it.

Define the paths after conditions change

Stop, hold, or complete safely

Every changed condition needs a stated path.

Confirmed purchase: This is a conversion exit from acquisition Nurture. If it appears while the contact is waiting for Day 4, the workflow does not continue with its acquisition-oriented message.

Changed relevance: If a preference change means Routine fit is no longer the declared barrier, end this barrier-specific sequence. A separately defined relevant workflow could evaluate the contact later, but Nurture must not continue with mismatched content.

Unknown purchase evidence: If required Purchase status is Unknown at entry or before a proposed message, use Hold for review. Do not infer No confirmed purchase from missing information.

Planned finish: After the Day 4 message is appropriately sent, use End sequence. This finite workflow delivers its planned support rather than looping indefinitely for contacts who have not purchased.

Tip

Use distinct endings deliberately

A changed record does not merely update a label. It changes the path: purchase removes acquisition relevance, a different declared barrier removes barrier relevance, and missing required purchase evidence prevents a safe decision.

Apply the conversion exit

Check the conversion exit

A contact is waiting between the Day 1 and Day 4 Nurture slots. Their Purchase status becomes Confirmed purchase. What should happen next?

Apply the full Nurture logic

Draft the Nurture map

Write a compact specification for the Nurture workflow. Include:

  1. Its entry gate using Welcome completed, Marketing eligibility, Decision barrier, and Purchase status.
  2. The distinct Marketing message purpose at Day 1 and at Day 4.
  3. The path for each case: a Confirmed purchase during a wait; a preference change that makes Routine fit irrelevant; and Purchase status = Unknown.

Use the workflow labels and -> connections.

Write at least 180 characters (0/180).

Step 6 of 8

Separate Post-Purchase Service from Marketing

Separate confirmed-order service actions from consent-dependent post-purchase marketing in a compact workflow map.

Use one confirmed event, then separate the purposes

Start with order evidence

A post-purchase workflow starts only when Purchase confirmed can be tied to the correct contact and order. For Northstar Paper, a checkout visit, a cart event, or time passing is not enough evidence.

Use the record labels Purchase status and Order ID. For example: Confirmed purchase plus NP-101 can support post-purchase entry when the record belongs to that contact.

From that point, split the map by purpose:

  • An order confirmation is Operational. It concerns the confirmed order itself.
  • Optional setup guidance and a refill invitation are Marketing. They need a current Marketing eligibility check at their proposed send time.

Do not turn every message after an order into service content merely because it is post-purchase.

Two paths after a confirmed purchase

A workflow diagram separates an operational order-confirmation path from a marketing path that checks current eligibility before setup guidance and a refill invitation.

The order event can support an operational purpose, but optional marketing actions require a current eligibility decision.

Specify what each path can legitimately do

Post-Purchase specification

Write the operational and marketing paths in one specification, but keep their sending grounds distinct. Day numbers are measured from the purchase trigger: Day 3 means 72 hours after Purchase confirmed, not three days after a prior message.

An existing order system may already send the genuine confirmation. In that case, map that existing operational action; do not add a duplicate workflow confirmation. A marketing unsubscribe does not by itself cancel a necessary operational message, but operational sending still needs a legitimate purpose, a valid route, and applicable legal and provider checks.

Post-Purchase

This compact map uses only facts the workflow can support. A reliable update can make an optional follow-up irrelevant; elapsed time alone never proves delivery or product use.

Text specification for Northstar Paper's example Post-Purchase workflow.
Specification headingPost-Purchase plan
TriggerPurchase confirmed
Entry checksCorrect contact-to-order match; Purchase status = Confirmed purchase; Order ID is available
Data neededPurchase status, Order ID, current Marketing eligibility, confirmation-system record
TimingDay 0 confirmation; Day 3 optional setup guidance; Day 30 optional refill invitation
ConditionsExisting confirmation sent? Marketing eligibility = Eligible? Follow-up still relevant?
Message purposesOperational: confirm the order. Marketing: help with initial setup; invite a relevant refill consideration
ExclusionsCheckout visit; unmatched order; unknown purchase evidence; marketing-ineligible contact for marketing actions
Exit rulesExisting operational confirmation completes its action. No eligibility or an irrelevant follow-up -> End sequence. Unknown required data -> Hold for review
Re-entryA later confirmed purchase needs its own reliable order evidence; detailed duplicate-event controls are added later

Practice: classify by purpose

Classify the post-purchase actions

Match each Northstar Paper action to its correct path.

Tap an item and then its matching pair.

Draft the safe outcome for a fictional contact

Apply: map the eligibility change

Trace Contact D through a concise text map using ->.

Contact D record

  • Hour 0: Purchase confirmed for a Weekly Planner; Order ID NP-101; Marketing eligibility Eligible.
  • Hour 0: The order system record shows that its confirmation was already sent.
  • Hour 20: Marketing eligibility changes to Ineligible.

Include all three proposed message purposes with their category and timing, the send-time decision for messages waiting at Day 3 and Day 30, and the final outcome. Then state how the map would differ if Marketing eligibility had been Ineligible at Hour 0. Do not draft email copy.

Write at least 180 characters (0/180).

Step 7 of 8

Resolve Overlap, Frequency, and Re-entry

Add shared controls that prevent duplicate enrollment, conflicting lifecycle messages, and sends based on outdated eligibility.

Check again when the message is due

A release gate for every Marketing send

A scheduled Marketing message is a proposed send, not a promise. Before releasing every Marketing message—including one that has been waiting—run a send-time check:

  1. Is Marketing eligibility currently Eligible?
  2. Do current preferences and suppression records permit this message?
  3. Has a confirmed purchase or other lifecycle change made this message irrelevant?
  4. Is its purpose still relevant to this contact?

If a required record is Unknown, do not turn that into a “No.” Use Hold for review for the affected action. If a check fails, apply the relevant Exit rules. A delay only sets a possible due time; it does not bypass these checks.

The shared send-time check

A flow diagram showing every scheduled Marketing message passing through checks for eligibility, preferences and suppression, purchase status, and relevance before it can be released.

Use this gate at the actual release time, including after any wait.

Apply priority and the rolling limit

Resolve competition before sending

Northstar Paper uses these shared planning rules for Marketing messages. They apply across campaigns and all three workflows:

  • Marketing priority: Post-Purchase > Welcome > Nurture.
  • Frequency limit: at most one Marketing message in any rolling 24-hour period.
  • If a relevant message is blocked, use Wait and recheck at the next eligible time. Then run the full send-time check again; do not release a stored backlog automatically.

This 24-hour limit is an illustrative scenario rule, not a universal recommendation. A necessary Operational confirmation is not placed in the Marketing priority queue or Marketing frequency cap. It still needs a legitimate purpose, a valid route, and applicable legal and provider checks.

Shared scheduling rules

Use the contact record label Last marketing send to calculate the rolling limit.

The priority rule does not override the frequency limit or a failed send-time check.
SituationNext actionGoverning rule
A Marketing send occurred less than 24 hours agoWait and recheckOne Marketing message per rolling 24 hours
Two still-relevant Marketing messages are dueConsider the higher-priority message firstPost-Purchase > Welcome > Nurture
A confirmed purchase makes acquisition content obsoleteEnd sequenceConversion and relevance check
Operational order confirmation is neededSend through its separate pathNot in the Marketing queue or cap

Set re-entry boundaries and close obsolete paths

Use enrollment keys, not repeated events

Re-entry controls prevent a workflow from treating repeated records as new opportunities.

For this example, Welcome and Nurture allow one enrollment per contact. A later import, repeated Signup confirmed event, or other new record must not erase a prior marketing suppression or create another enrollment.

Post-Purchase may enroll once per distinct confirmed order. Store the matched contact and Order ID with its enrollment. If Purchase confirmed arrives again for the same contact and Order ID, such as NP-101, it is a duplicate event: do not start a second Post-Purchase workflow.

A different confirmed order can qualify for its own Post-Purchase enrollment. In all cases, current suppression and send-time checks remain in force.

Tip

Conversion changes the active plan

A purchase should do more than add a new workflow: it also ends obsolete acquisition paths. When Purchase status becomes Confirmed purchase, a waiting Welcome or Nurture Marketing message should not merely remain queued behind Post-Purchase. Apply its Exit rules and use End sequence for the obsolete acquisition workflow.

Apply the shared controls

Resolve the collision, duplicate, and unsubscribe

At shared Hour 48, resolve all three records below. State the next action and the rule that governs it.

Contact A: Marketing eligibility is Eligible. Purchase status is Confirmed purchase for Order ID NP-101. A Welcome Marketing message is waiting, and optional Post-Purchase setup guidance, also Marketing, is due. Last marketing send was at Hour 30.

Contact B: A Purchase confirmed event arrives for Order ID NP-101. This contact is already enrolled in Post-Purchase for Order ID NP-101.

Contact C: A Nurture Marketing message becomes due after a delay. At Hour 45, the contact unsubscribed and Marketing eligibility became Ineligible.

For Contact A, include the earliest hour when a deferred Marketing message could be reconsidered.

Write at least 180 characters (0/180).

Step 8 of 8

Validate and Finish the Three Workflow Maps

Trace fictional contacts through three lifecycle workflow maps, repair unsafe paths, and finalize internally consistent specifications.

The validation packet

Validate by tracing a contact path

Validation is a replay, not a guess. Take one contact’s timestamped record and move it through a draft map:

entry event -> enrollment check -> wait -> send-time check -> action, hold, deferral, or exit.

At every decision, record both the expected next action and the governing rule. A contact can be waiting without being entitled to a future send, because later events can change the path.

Keep these outcomes distinct:

  • End sequence: a known condition makes the path irrelevant or disallowed.
  • Hold for review: required evidence is Unknown.
  • Wait and recheck: a temporary frequency restriction delays an otherwise relevant Marketing message.

Use the supplied fictional records only. No email platform, connected store, or previously saved work is needed.

A trace follows changing contact records

Five contact timelines move through events, decisions, waits, sends, holds, deferred actions, and endings as their records change.

Trace from left to right. A record can change during a wait, so each proposed Marketing message needs a fresh send-time check.

Draft maps to test

These compact drafts are useful only when their paths are supported by records and shared rules. Trace the question in the last column before repairing each map.

Each draft contains a path that needs validation or repair.
WorkflowDraft pathQuestion to test
WelcomeSignup confirmed -> eligible entry -> Day 0 Marketing acknowledgment of planning tips and product updates -> Day 2 check -> Marketing first planning action -> Welcome completed -> End sequenceWhat happens if a confirmed purchase arrives during the Day 2 wait?
NurtureWelcome completed -> eligible + Routine fit + No confirmed purchase -> Day 1 Marketing routine-fit guidance -> Day 4 purchase check -> Marketing fit assessment and next step -> End sequenceWhat should happen if required purchase evidence becomes Unknown before Day 4?
Post-PurchasePurchase confirmed -> Day 0 Operational order confirmation -> Day 3 Marketing setup guidance if eligible -> Day 30 Marketing Refill Pack invitation if eligible -> End sequenceHow can the map avoid both a duplicate confirmation and a second enrollment for the same Order ID?

Trace the fictional contacts

Contact-event records

For each record, create a short trace ledger: current workflow state, expected next action, and governing rule. “No message” is not enough—state whether the contact ended, is held for review, or is waiting for a later recheck.

The timestamps are elapsed time from one shared scenario start. Day-relative due times still belong to each workflow’s own entry event.

Five records to trace

The records include normal progression, missing purchase evidence, a purchase during a wait, a preference change, an unsubscribe, a scheduling collision, and a duplicate order event.

All Marketing actions use current send-time checks and the shared limit of one Marketing message per rolling 24 hours.
ContactTimestamped events and current recordsTrace focus
Contact AHour 0: Signup confirmed; Marketing eligibility Eligible; Purchase status No confirmed purchase; Decision barrier Routine fit. Hour 48: Welcome Day 2 is due and Welcome completed occurs. Hour 72: Nurture Day 1 is due. Hour 144: Nurture Day 4 is due.Normal planned progression.
Contact BHour 0: Signup confirmed with the same initial records as A. Hour 48: Welcome completed. Hour 72: Nurture Day 1 occurs. Hour 100: Purchase status becomes Unknown. Hour 144: Nurture Day 4 is due.Required purchase evidence disappears during a wait.
Contact CHour 0: Signup confirmed; Marketing eligibility Eligible. Hour 24: Purchase confirmed; Order ID NP-101; correct contact-to-order match.A purchase occurs before Welcome Day 2.
Contact DHour 0: Signup confirmed; Marketing eligibility Eligible; Purchase status No confirmed purchase; Decision barrier Routine fit. Hour 48: Welcome completed. Hour 60: Marketing eligibility becomes Ineligible after a preference change. Hour 72: Nurture Day 1 is due.A preference change removes Marketing eligibility.
Contact EHour 0: Purchase confirmed for the correct contact; Order ID NP-101; Marketing eligibility Eligible. The confirmation-system record says confirmation was sent. Hour 1: duplicate Purchase confirmed for NP-101. Hour 60: another Marketing message is sent. Hour 72: Post-Purchase Day 3 setup guidance is due; Marketing eligibility remains Eligible through Hour 79. Hour 80: unsubscribe makes Marketing eligibility Ineligible. Hour 84: next possible frequency recheck.Operational handling, duplicate prevention, a scheduling collision, and unsubscribe.

Finalize the maps from the traces

Final application: repair and justify the combined plan

Create the final, corrected lifecycle plan in one concise response.

  1. Write a specification for Welcome, Nurture, and Post-Purchase. For each, use these headings: Trigger, Entry checks, Data needed, Timing, Conditions, Message purposes, Exclusions, Exit rules, and Re-entry.
  2. Use -> connections and label decision outcomes Yes, No, and Unknown.
  3. Add a trace result for Contacts A–E. For each, name the expected next action and governing rule.
  4. Make the repairs explicit: stop ineligible Marketing, exit obsolete acquisition paths after a confirmed purchase, preserve legitimate Operational handling, prevent duplicate enrollment, hold decisions without required evidence, and use Wait and recheck only for a temporary rolling-24-hour restriction.

Keep message descriptions as purposes, not full email copy.

Write at least 900 characters (0/900).

Reference resolution and completion

Completed map: Welcome

Trigger: Signup confirmed.

Entry checks: Marketing eligibility Eligible? -> Yes: prior Welcome enrollment? Yes -> End sequence; No -> enroll. Ineligible -> End sequence. Unknown -> Hold for review. Welcome status records planned completion; it does not replace enrollment history.

Data needed: Marketing eligibility, Welcome enrollment history, Welcome status, Purchase status, Last marketing send, and current preference or suppression records.

Timing: Day 0 and Day 2 from Signup confirmed.

Conditions: Before each proposed Marketing message, run the send-time check. Confirmed purchase, failed permission, suppression, or known loss of relevance? -> Yes: End sequence. Required record Unknown? -> Hold for review. Marketing sent in the prior 24 hours? -> Yes: Wait and recheck at the next eligible time, then repeat all checks; No: send the due purpose.

Message purposes: Day 0 acknowledges signup and fulfills planning tips and product updates expectations. Day 2 guides a relevant first planning action.

Exclusions: Ineligible contacts and contacts with prior Welcome enrollment.

Exit rules: Known purchase, known ineligibility, suppression, or completed Day 2 path -> End sequence. Only the planned Day 2 path records Welcome completed.

Re-entry: One enrollment per contact; retain suppression across later events.

Completed map: Nurture

Trigger: Welcome completed.

Entry checks: Marketing eligibility Eligible, Decision barrier Routine fit, Purchase status No confirmed purchase, and prior Nurture enrollment absent? -> Yes: enroll. Prior enrollment or any known disqualifying result—Ineligible, different or absent barrier, or Confirmed purchase -> End sequence. Any required value Unknown -> Hold for review.

Data needed: Welcome status, Nurture enrollment history, Marketing eligibility, Decision barrier, Purchase status, Last marketing send, and current preference or suppression records.

Timing: Day 1 and Day 4 from Welcome completed.

Conditions: Before each proposed Marketing message, Purchase confirmed? -> Yes: End sequence; No: continue; Unknown: Hold for review. Routine fit relevant and Marketing eligibility Eligible with permission allowed? -> Yes: assess frequency; No: End sequence; Unknown required record: Hold for review. Marketing sent in the prior 24 hours? -> Yes: Wait and recheck, then repeat all checks; No: send the due purpose.

Message purposes: Day 1 addresses uncertainty about fitting weekly planning into an existing routine. Day 4 helps assess fit and take a purchase-related next step.

Exclusions: Prior Nurture enrollment, ineligible contacts, contacts without Routine fit, and confirmed purchasers.

Exit rules: Purchase, lost relevance, ineligibility, suppression, or appropriately sent Day 4 message -> End sequence. Unknown required evidence -> Hold for review.

Re-entry: One enrollment per contact; retain suppression across later events.

Completed map: Post-Purchase

Trigger: Purchase confirmed.

Entry checks: Purchase status Confirmed purchase, correct contact-to-order match, and a new Order ID? -> Yes: enroll for that order. Match or order evidence Unknown -> Hold for review. Known unmatched, invalid, or duplicate Order ID -> End sequence for that event.

Data needed: Purchase status, Order ID, contact-to-order match, confirmation-system record, current Marketing eligibility, Last marketing send, and reliable order updates.

Timing: Day 0 confirmation; Day 3 optional setup guidance; Day 30 optional Refill Pack invitation, all from Purchase confirmed.

Conditions: Day 0 is Operational. Existing confirmation sent? -> Yes: retain the existing action; No: send one legitimate order confirmation through its separate Operational path; Unknown: Hold for review. At Day 3 and Day 30, follow-up relevant and Marketing eligibility Eligible with permission allowed? -> Yes: assess frequency; No: End sequence for Marketing follow-ups; Unknown: Hold for review. Marketing sent in the prior 24 hours? -> Yes: Wait and recheck, then repeat all checks; No: send the due Marketing purpose.

Message purposes: Day 0 Operational confirmation; Day 3 Marketing setup guidance; Day 30 Marketing Refill Pack invitation.

Exclusions: Unmatched orders and duplicate Purchase confirmed events for the same contact and Order ID.

Exit rules: Ineligible or irrelevant Marketing follow-ups -> End sequence. After Day 30 -> End sequence. Operational handling remains separate.

Re-entry: Once per distinct confirmed Order ID.

Summary

Readiness checklist and trace resolution

Use this checklist before considering the maps ready.

  • Each workflow names its Trigger, evidence, entry checks, timing, message purposes, exclusions, exits, and re-entry rule.
  • Welcome and Nurture check prior enrollment explicitly. Planned completion status is separate from enrollment history, and suppression remains in force after later events.
  • Every proposed Marketing message uses a send-time check for current eligibility, preferences, suppression, conversion status, relevance, and Last marketing send.
  • Known disqualifying conditions lead to End sequence. Unknown required evidence leads to Hold for review. A temporary rolling-24-hour restriction leads to Wait and recheck.
  • Marketing priority is Post-Purchase > Welcome > Nurture. A confirmed purchase ends obsolete Welcome or Nurture acquisition paths; it does not merely postpone them.
  • Contact A can complete Welcome, then proceed through the finite Nurture path if each later check passes. Contact B reaches Hold for review before Nurture Day 4.
  • Contact C exits Welcome after the confirmed purchase and may enter Post-Purchase for NP-101. Contact D ends Nurture Marketing after becoming Ineligible.
  • For Contact E, the duplicate NP-101 event does not enroll again. At Hour 72, eligibility is known Eligible but the Hour 60 Marketing send blocks setup guidance, so it goes to Wait and recheck. At Hour 84, the unsubscribe makes eligibility Ineligible, so the Marketing path ends. The existing Operational confirmation is not duplicated.

Workflow maps complete

Congratulations! You completed: Map Welcome, Nurture, and Post-Purchase Automations

You validated the combined lifecycle plan by tracing changing contact records, repairing unsafe branches, and finalizing Welcome, Nurture, and Post-Purchase specifications.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate