Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
1 contribution to Ecommerce Email Marketing
Need help architecting age-based lifecycle flows on Klaviyo for a baby subscription brand
I am working for a ecomm subscription brand that sells baby skin care products (baby body wash, lotions, diaper rash cream, powder, etc.). If I have to setup a Klaviyo flow keeping in mind the baby's age and controlling how someone would get the email based on the baby's age how would I do it? For example if there's a milestone based email flow that sends emails every month (0-12 months), but say I have two customers enter the flow: One whose baby is 1 month old and the other customer whose baby is 7 months old, how would I control what emails should they get on Klaviyo? And how would I also control my subscription architecture (the subscription perks the 1 month old baby gets will not be useful / relevant for the 7 months old baby). And say I also want to attract & nurture expecting parents how would factor them into this flow? Thanks! :)
1 like • Aug 9
This is the response from Claude. This is a fun architecture problem because the "age" dimension has to drive three separate systems (email content, box contents, and eligibility), and they age at different rates. Here's how I'd build it. 1. Get the data model right first Everything downstream depends on a few clean profile properties: - baby_birthdate (date type — must be a true date property, not text) - due_date (date) for pre-birth profiles - parent_stage (string: expecting / parent) — your master routing switch - baby_age_months (number) — optional but very worth it, see below - birthdate_confidence (string: confirmed / estimated) — matters a lot for the expecting-parent handoff - baby_name, and a child_2_birthdate if you want to handle siblings Collect these at the earliest possible touchpoint: a two-question quiz on the popup ("Is baby here yet?" → date picker), a post-purchase survey, and an always-available "update baby's info" link in your email footer. Whatever percentage of profiles lack a birthdate is the percentage of your list that can't be personalized, so this capture rate is the real ceiling on the whole system. 2. The routing problem, and why a linear flow won't work A single flow with Delay 30 days → Email 1 → Delay 30 days → Email 2 fails exactly as you suspected: everyone starts at Email 1. Your 7-month customer would get newborn cord-care content for the next six months. There are two viable patterns. Pattern A — Segment-triggered milestone flows (recommended). Build one segment per age bucket, defined off the date property: baby_birthdate is at least 210 days ago AND baby_birthdate is less than 240 days ago → "Baby Age – 7 Months" Then each segment triggers its own small flow (1–3 emails) via the Added to Segment trigger. Your 1-month customer lands in "Baby Age – 1 Month," gets that content, and next month Klaviyo drops them from that segment and adds them to "2 Months," which triggers the next flow. Your 7-month customer enters at "7 Months" and continues from there. Nobody gets stale content, nobody gets a six-email catch-up dump, and the system self-corrects if someone updates their birthdate later.
1-1 of 1
Dani Shulman
1
4 points to level up
@dani-shulman-8649
Experimentation & analytics engineer. Building microsites as income-generating assets, plus e-commerce projects. Toronto.

Active 54d ago
Joined Aug 8, 2026
Toronto