Retention Stage

✅ Start / Stop conditions

• Start:
  Every day for the dynamic segment of all paid active users (who have trained at least once in the last two weeks).
• Stop when:
  SubscriptionCanceled.

🎯 Audience

• Engaged users only.
• Exclude inactive cohorts, recent complainers, and users in conflicting sequences.
• Optionally split into morning/evening segments based on preferred time.

🔁 Workflow description

• Structure: 1 regular message per day using the One from Many workflow block. This block diversifies communication, tests different versions of your message, and automatically prioritizes the one with the highest engagement.
• Optionally run two similar workflows corresponding to the user’s preferred time:
  • morning reminders
  • evening reminders

📊 Message personalization

• Data from contact fields (e.g., $fitnessGoal)

⏱ Timing

• Send each day at the user’s habitual time.

📡 Channel mix

• Push notification.

📈 Success metric

• Action completion rate.

Read the full Reminders guide >

✅ Start / Stop conditions

• Start:
  Every day for a dynamic segment: users who have a streak for the target action and did not complete it today (streak at risk).
• Stop when:
  SubscriptionCanceled.

🎯 Audience

• Users who already show habit-forming behavior (an existing streak).
• Exclude:
  • cold / inactive users
  • users currently in conflicting flows
  • users who already completed the target action today (to avoid duplicate reminders)

🧩 How to build the dynamic segment (using the streak condition)

Use the segmentation condition streak to verify that a series of events (and conditions inside them) happened consistently over a specific time range:

• streak → N → previous complete days/weeks/months: the target event must occur at least once in each of the previous N complete periods.

Add an extra condition like “no target event today” so the workflow triggers only when the streak is actually at risk.

🔁 Workflow description

• Structure: max 1 message per day, only if the streak is at risk.

📊 Message personalization

• Data from contact fields (e.g., $fitnessGoal)

⏱ Timing

• Send daily at the user’s most likely engagement window (or a default local time).
• If you re-check the segment multiple times per day (e.g., hourly), still enforce max 1 send/day per user.

📡 Channel mix

• Push (recommended to use One from Many to automatically prioritize the best-performing variant and diversify your communication).

📈 Success metrics

• Streak retention rate (share of users who maintain their streak).
• Action completion rate on reminder days.

✅ Start / Stop conditions

• Start when:
  MilestoneAchieved fires (e.g., 10th workout/lesson, 7 days active, level-up).
• Stop:
  After a single send.

🎯 Audience

• Users who reached a tracked milestone.

🔁 Workflow description

• Structure: One celebratory message + optional “share” or “next step” CTA.

📊 Data & personalization

• Start event payload example:

  • planName
  • milestoneName
  • milestoneValue
  • shareLink (optional)
  • nextGoalDeepLink

• Message personalization:

  • user stats
  • next recommended goal (optional)

⏱ Timing

• Immediately after the milestone event.

📡 Channel mix

• Mobile push.

📈 Success metric

• Next-action rate within 24–48h.

✅ Start / Stop conditions

• Start by event:
  • MilestoneAchieved
  • SupportContacted
  • SubscriptionCanceled
• Regular workflow for segment (once an hour): users who have completed the target action (X time during X days), e.g.,: 2+ training completed during the last 7 days).
• Stop when:
  feedbackSubmitted during the last 8 weeks or unsubscribed.

🎯 Audience

• Qualified users based on trigger:
  • engaged users after meaningful action
  • support-touch users
  • churn-risk users after cancel

🔁 Workflow description

• Structure: 1 ask + 1 reminder if the first was not opened.

📊 Data & personalization

• Start event payload (optional):

  • usageLevel
  • lastActionDate
  • supportStatus

• Message personalization:
  Micro-survey; messages may differ by subscription/plan type.

⏱ Timing

• Within 1–12h post-trigger.
• Reminder +48h.

📡 Channel mix (invites)

• Email.
• Push.

📈 Success metrics

• Response rate.
• Detractor rescue rate.
• Promoter review lift.

✅ Start / Stop conditions

• Start when:
  The user is activated.
• Stop when:
  TargetFeatureUsed or SubscriptionCanceled.

🎯 Audience

• Users with proven intent who haven’t adopted a key feature.

🔁 Workflow description

• Structure: 2–5 messages:
  • why it matters
  • how to start
  • social proof
  • quick demo

📊 Data & personalization

• Start event payload example:

  • targetFeatureKey
  • userSegment
  • featureDeepLink
  • tutorialLink

• Message personalization:
  Tailor to the goal segment and show the shortest path to success.

⏱ Timing

• Message 1: +24–72h after qualification.
• Follow-ups: daily.

📡 Channel mix

• In-app walkthroughs.
• Email for deeper explanation.
• Push for timely prompts.

📈 Success metric

• Feature adoption rate.

✅ Start / Stop conditions

• Start when:
  User meets eligibility (e.g., active 30 days, high engagement, low refund risk) and billingType = Monthly (regular workflow for segment scheduled once an hour).
• Stop when:
  AnnualPurchased or SubscriptionCanceled.

🎯 Audience

• High-LTV monthly subscribers.

🔁 Workflow description

• Structure: 1 email with a discount as a reward for user activity.

📊 Data & personalization

• Message personalization:
  • personal savings estimate
  • benefits tied to their usage patterns

⏱ Timing

• When eligibility condition becomes true (hourly evaluation if using “regular workflow for segment”).

📡 Channel mix

• Email.

📈 Success metrics

• Annual upgrade rate.
• ARR lift.