Lifecycle marketingEvent trackingPatient funnelCustomer.ioTelehealth

Lifecycle marketing that follows the patient journey

All work

The short version

In a subscription health product, almost every message a patient gets after signing up is triggered by something the product recorded: they stopped at identity verification, a doctor prescribed, a card was declined, a refill is two days away. Lifecycle marketing (LCM) turns those moments into the right email or text, and should stop when the moment has passed.

This guide covers the funnel those messages work on, which product events mark each stage of a patient's journey, how the events reach the messaging tool and come back, and what was built on them. It is a sibling to building click-funnel events you can trust and event properties: what matters and how to construct them, which cover the events and properties themselves.

The examples come from a telehealth subscription company in weight-loss and longevity treatment, where I was Head of Product and led the product and engineering team. The lifecycle team owned the messages; we owned the events. Figures are percentages or ratios from production analytics, mostly from August to October 2026, with windows noted where they differ. Event and property names are simplified from the real schema to follow the conventions in the sibling guides. Throughout, "checked out" means completed the purchase, and "started checkout" is the step before.

74%of new patients who checked out did so within an hour of creating their account
8.1%of checkouts in a 30-day window carried a lifecycle message's link tag
63%of those tagged checkouts came from abandoned-onboarding emails
87%of failed payments got the recovery email within 7 days

Three ideas run through what follows: events, not schedules, start and stop messages; the messaging tool needs the moment, not the medical details; and a message has only worked if you can show what would have happened without it, which most programs, ours included, cannot yet do.

Events, attributes and the messaging tool

A lifecycle tool such as Customer.io or Braze holds two kinds of data about a person, and getting the split right matters more than any template.

The funnel the messages work on

The funnel is the patient journey seen as shares. Each stage is also an audience: the people who stopped there are who the next message is for, and the event that moves them on is that message's exit. For new accounts created in August 2026, followed for 60 days:

Share of new accounts reaching each stage within 60 days, and the messages that work on the gap below it
StageShare of new accountsLifecycle messages that work on the gap
Account created100%Abandoned-onboarding email keyed to the last step reached
Questionnaire completed87.1%Treatment-choice and identity-verification stage emails, aimed at the biggest leak: only 20.9% of questionnaire finishers start checkout
Started checkout18.2%Checkout-stage email
Checked out7.9%Receipt, welcome and prescription updates; failed-payment sequence
First payment4.8%Follow-up reminder, refill heads-up, failed-payment sequence
Second payment3.7%From here on: refill heads-ups, cross-sell and cancellation journeys

After checkout, the patient no longer controls the pace. Of those who checked out, 99.0% were accepted as patients and 80.8% were prescribed. Clinicians and billing set the timing from here, so the messages in this stretch are mostly about explaining what happens next.

The patient journey, stage by stage

Each stage of the journey, the event that marks it, the message it triggers, the properties that message needs and how to judge it. The last two columns are recommendations.

Patient journey stages and the lifecycle messages they trigger
StageEvent that marks itLifecycle messageProperties it needsHow to judge it
Lead or waitlistLead Captured, Waitlist JoinedLead offer; launch email when a new territory opensCapture method, first campaignOnboarding starts from the message's links
Started onboarding, did not finishLast step reached: Questionnaire Completed, Treatment Chosen, Identity Verification Started, Checkout Started; should stop at Checkout CompletedOne email per drop-off point, then a follow-up at 15 to 45 daysLast step reached, onboarding versionCheckout within 7 days, against unsubscribes
Purchased, awaiting prescriptionCheckout Completed, Patient Accepted, Prescription IssuedReceipt (with an expedited-shipping branch), welcome, post-prescription seriesProduct class, billing cyclePrescribed, then paid, within 30 days
Verification problemIdentity Document Rejected"Upload rejected", asking for a new documentRejection reasonRe-upload and completion
In treatmentOrder Shipped, Provider Message Sent, Follow-up RequestedShipping notice, "your doctor sent you a message", follow-up reminderProduct class at most; the message itself stays in the portalFollow-up completed within 14 days
Refill or dose changeRefill Reminder Due, Dose Change DueHeads-up two days before the charge or changeRefill or change date; dose details shown in the portalCharged, failed or cancelled within 10 days
Payment problemPayment Failed, Card Expiring; recovery is Billing Updated then Payment SucceededFailed-payment email and SMS; card-expiry emailAmount, invoice referencePaid within 7 days
CancellingCancellation Started, Subscription Cancelled, Subscription Paused, Subscription ReinstatedCancellation email, reason-targeted follow-ups, a one-time recapture linkReason, who initiated it, product categoryReinstated within 30 days
Ready for moreactive_subscriptions attribute, Add-on PurchasedCross-sell to another product line around day 30 or 45Active subscriptions, product classPurchase of the second product
AdvocateReferral SentReferral invitationReferral linkReferred accounts that check out

Where messages have room to act

Timing tells you what kind of message belongs at each stage. We estimated it by re-running funnels with windows from one hour to 60 days.

How the data flows

The app never sent a patient an email or text itself. Templates, delays, branches and exits lived in the messaging tool; the codebase owned the events.

  1. The product records the moment. Browser and backend send track and identify calls to Segment. Server calls go through a durable outbox that retries four times with exponential backoff and sends identify calls ahead of track calls.
  2. Segment fans it out to Customer.io for email and SMS, to Mixpanel, and to any other destination that needs it. A few calls, such as an identify client and profile deletion, went to Customer.io directly.
  3. Engagement comes back. Customer.io's delivery and engagement events return through their own Segment source into Mixpanel, on the same user timeline as the product events.
  4. Links close the loop. Every link carries UTM tags, so a checkout after a click is recorded with the message that preceded it.

Delivery shows whether it works: 92.6% of new accounts got at least one email within 14 days, and 99.0% of checkouts got one within 7 days, usually the receipt, about six and a half minutes after purchase. The other 7.4% of new accounts are the gap to monitor (example 8).

A checkout event, simplified, with illustrative names and invented values. It names the product class outright, because a journey should never have to work it out (example 3 shows why).

{
  "type": "track",
  "event": "Checkout Completed",
  "userId": "3f9c2a7e-51b4-4c0e-9d1a-7b2e8c40f611",
  "timestamp": "2026-10-14T18:27:05Z",
  "properties": {
    "product_class": "glp1",
    "billing_cycle": "monthly",
    "onboarding_version": "v2",
    "utm_source": "customer.io",
    "utm_campaign": "abandoned_onboarding_identity_1"
  }
}

A profile update, with trait names in the same style and all values invented. The subscription list is re-sent whenever a treatment is created, started, prescribed or paused. The backend builds the referral link and passes it as a trait, so no patient ID appears in a URL; the design for recapture links follows the same pattern.

{
  "type": "identify",
  "userId": "3f9c2a7e-51b4-4c0e-9d1a-7b2e8c40f611",
  "traits": {
    "first_name": "Alex",
    "onboarding_version": "v2",
    "sms_opt_in": true,
    "active_subscriptions": [
      {
        "product_class": "glp1",
        "status": "active",
        "next_billing_date": "2026-11-04",
        "billing_cycle": "monthly"
      }
    ],
    "referral_link": "https://portal.example.com/r/k7Qm2xR9"
  }
}

What comes back from Customer.io uses its own Title Case event names (Email Delivered, Email Link Clicked, Email Converted, SMS Failed) with snake_case properties, and trigger_event_id points to the product event that started the journey. Values invented:

{
  "event": "Email Converted",
  "properties": {
    "campaign_name": "abandoned_onboarding_identity_1",
    "journey_id": "jrn_example_01",
    "action_name": "Email 1",
    "template_id": 1234,
    "delivery_id": "dlv_example_01",
    "trigger_event_id": "evt_example_01"
  }
}

Applied examples

Aggregate patterns from the same company, not individual patients. Figures are mostly from 30-day windows in September and October 2026, with other windows noted.

1. Abandoned onboarding, rebuilt by stage

Situation. Everyone who created an account without checking out got the same abandoned-onboarding flow, wherever they stopped. In October 2025 the lifecycle team proposed flows keyed to the exact drop-off point.

What was built. Six stage emails keyed to the furthest onboarding step reached and meant to stop at purchase (current versions date from December 2025), then a 15-to-45-day email and a long-tail one.

Result. These emails accounted for 63% of checkouts carrying a lifecycle link tag. The identity-verification email had the biggest stage audience, matching the weakest step in the onboarding funnel: just over a third of those who started identity verification went on to start checkout. About 7% clicked, 7% converted on the tool's goal and 5% unsubscribed. The treatment-type and treatment-choice emails did worse, with unsubscribe rates (7.8% and 6.7%) more than double their 3.2% click rate. Among August 2026 accounts followed for 60 days, clickers converted at 21.6% against 2.3% for recipients overall, but clickers select themselves, so that gap cannot be read as the email's effect.

Lesson. Splitting by stage makes sense, because the stage tells you what to say, though we had no before-and-after to prove it. Every stage email costs list, and some stages lose more than they win. These emails are separate from the redesign in the onboarding case study, which moved more people to start checkout without a clear increase in purchases; they work on the people the funnel still loses.

2. The long tail that cost more than it earned

Situation. A reactivation email went to people 120 to 150 days after abandoning onboarding. Nothing had happened to them; only the clock moved. Its audience was about eight times the biggest stage email's.

Result. 0.27% clicked, 1.0% unsubscribed and about 1 in 10,000 recipients checked out: roughly 100 unsubscribes per checkout. Broadcasts looked similar: only 2.8% of onboarding starts from October's newsletters became checkouts, against 13.6% for lifecycle-tagged traffic overall.

Lesson. A message triggered only by the clock is a broadcast in disguise. Report unsubscribes per checkout, and reactivate only with a real reason, such as a new product line or a price change.

3. A new product line broke "if not A, then B"

Situation. Journeys decided a patient's product line by elimination: not line A, so it must be line B. That broke when a third product line launched.

What was built. Engineering and the lifecycle team agreed to add one explicit property, product_class, to the checkout event and leave every existing property alone, so live journeys kept working.

Result. In the rollout week, 12.5% of checkout events lacked the property; from the next week, none did. Part is still open: the messaging tool still recognized one line only by a version tag, so a patient buying an add-on to that line could look like a patient on another, and the lifecycle team has asked for an explicit product category.

Lesson. Send categories explicitly, add properties rather than changing them, and check coverage weekly until it hits 100%.

4. Failed payments across email, SMS and automatic retry

Situation. Over the past year, about 6% to 9.5% of paying patients had a failed payment each month.

What was built. The lifecycle team's email and SMS sequence starts on Payment Failed (amount, invoice reference); recovery shows up as Billing Updated then Payment Succeeded, and those are the events it should exit on. The current version dates from January 2026. In October 2026 we added automatic retries: up to six over about seven weeks, front-loaded in the first three days, before an invoice is marked uncollectible.

Result. For failures from September 1 to October 20, 2026:

Lesson. Exits need as much design as messages. Ours did not stop on cancellation at first, so check that every journey exits on success, on cancellation and on anything the system does by itself, such as a retry. A simple check catches leaks: compare the people a sequence reaches each week with the people who entered it, and look into any gap the sequence's length does not explain. Once the system recovers payments by itself, the messages must know what it is doing.

5. Inside treatment: follow-up, refill and cross-sell

After the first payment, lifecycle messages mostly support care rather than sell, and the three kinds behaved very differently.

Lesson. Messages tied to something the patient already means to do, such as finishing a follow-up, get acted on. A new decision, such as adding a product, does better where the patient already is, in the portal. Cross-sells also raise the HIPAA marketing question covered below.

6. Cancellation: the save happens in the product

Situation. Cancelling triggered a cancellation email, reason-targeted follow-ups and, for some, a one-time recapture link.

Result. Cost was the most common reason given, at 33.7%. 83.4% of people who opened the cancellation flow cancelled within a day, and only 1.4% of them applied the save discount offered in the flow. Afterwards, the cancellation email converted 1.8% on its own goal and no checkout in the window carried its link tag; 4.9% of cancellations were reversed within 30 days. One reason-targeted follow-up lost 12.7% of its recipients to unsubscribes.

Lesson. The save moment is inside the product flow, while the patient is deciding, not in the email that follows. Spend effort there first, and keep post-cancellation messages few and clearly useful.

7. Upstream changes that broke, or nearly broke, messages

Lesson. A journey is a contract with every upstream system. Write down what each trigger depends on (event and property names, value formats, link target) and treat changing any of them as changing the journey.

8. Messages nobody could trace

Situation. A patient's messaging profile can fail to sync without an error anyone sees, and then every message for that patient silently stops.

The repair tool. An admin button re-sends a patient's full profile: useful, and exactly where unneeded fields accumulate, so review it field by field.

A second case. One journey, an onboarding email sent after an in-person purchase, was triggered from outside the product, and nobody could quickly say what fired it or why it sometimes failed. About half the onboarding starts it drove ended in a checkout, so it mattered.

Lesson. Keep a register of every journey (trigger, exit, goal, owner, source system) and monitor the share of new accounts with a messaging profile and a first email. Nobody notices when an untraceable message stops.

The rules for health products

The analytics side is in the privacy section of the properties guide; these rules are specific to messaging. This is not legal advice, so have counsel confirm each one. Vendor terms are as documented in October 2026.

Not a HIPAA covered entity? Health data is still regulated. If you run a health app or personal health record, the FTC's Health Breach Notification Rule counts an unauthorized disclosure as a breach, and the FTC has used its general powers against health advertisers too. Washington's My Health My Data Act requires opt-in consent and lets individuals sue.

Measuring whether lifecycle messages work

The real question is whether the patient did something they otherwise would not have. First, the reporting has to be trustworthy, and ours had gaps.

95%of email opens were flagged as proxied, so opens say little about reading
43%"Email Sent" as a share of "Email Delivered", so unusable as a base
~70%of email recipients had at least one email with no campaign name (newsletters use a separate field)

Holdouts that are hard to see

Several journeys already had holdout or control arms. Customer.io still logs a delivery for a held-out message, routed to an internal trap, so in analytics these arms look sent. The tell is that not one of those held-out deliveries was opened or clicked, while ordinary deliveries showed opens on about 95%. They are real no-send groups, but recent, small and identifiable only by step name, so they could not yet show lift.

Windows and the stratification lesson

Set attribution windows from time-to-convert data, not vendor defaults. Braze falls back to a 3-day window when no conversion event is set (configurable up to 30), while our checkouts after an abandoned-onboarding email came about 10 days later on average, and most payment recoveries came after day one.

Then compare like with like. In the onboarding case study, the new version had about a fifth of the weakest week's new accounts and about three quarters of the strongest week's, while conversion moved for both versions. Pooling the weeks credited the new version with that difference, and comparing within each week removed most of the apparent lift. Lifecycle messages fall into the same trap when a holdout's share changes midway or a journey launches in a good month. Keep the holdout share fixed, stratify by lifecycle stage and by week before comparing, and count only people who have had their full window.

Migrating messaging tools without breaking journeys

If you ever move lifecycle tools, for example from Customer.io to Braze, most of the risk sits outside the tool. What to plan for, with vendor details as documented in October 2026:

A checklist

The takeaway

Lifecycle messaging is only as good as the events beneath it, and the funnel tells you where each message belongs. The messages patients acted on most were tied to a precise moment: a follow-up due, a doctor's message waiting, a payment that had just failed. Several of the ones that cost the most, or went wrong, ran on the clock alone, guessed what the patient had bought, or lacked an exit. Get the events, the exits and the identity right first, then use holdouts that can prove the messages matter, because a click rate cannot.

Work with us

Want lifecycle messages that follow the product?

I design the events, properties and journeys that connect a product to its messaging tools, with the guardrails health products need.