Hi everyone,
The goal is to use time delays to update of the child age profile from the point they enter. E.g. my child’s age was entered as 3 weeks. 7 days later the property updates to 4 weeks. 7 days later the property updates to 5 weeks, etc
And also allowing the ages of multiple children to be tracked and all up to the age of 4.
The flow we’ve started with only does one child age and is so large it can barely load. Does anyone have any suggestions or work arounds for this? Truly appreciate any help.
Solved
Update Property Age by weeks from 0-4 for multiple childrewn
Best answer by ArpitBanjara
Hey
The fix is to stop tracking age as a number you increment every week and start tracking it as something Klaviyo calculates automatically from a fixed date.
Store each child's birth date (or the date they were entered) as a date profile property, this will be indexed per child. You set that once, when the child is added. From there, you never touch it again. No weekly update step, no time-delay chain, no flow that grows every time someone adds a kid.
To send messages at specific weeks, use Klaviyo's date property-triggered flow type, anchored to that birthdate property, with the trigger set to repeat as needed. instead of a long chain of "wait 7 days, wait 7 days, wait 7 days," use conditional splits that check how much time has passed since the date, and route to the right message for week 0, week 1, up through week 4.
here is an article from klaviyo on how to create a date property triggered flow
let me know if this works for your use-case and if you have any follow up questions.
Thank you for posting your question here in the community.
Cheers
Arpit
+37Hey
The fix is to stop tracking age as a number you increment every week and start tracking it as something Klaviyo calculates automatically from a fixed date.
Store each child's birth date (or the date they were entered) as a date profile property, this will be indexed per child. You set that once, when the child is added. From there, you never touch it again. No weekly update step, no time-delay chain, no flow that grows every time someone adds a kid.
To send messages at specific weeks, use Klaviyo's date property-triggered flow type, anchored to that birthdate property, with the trigger set to repeat as needed. instead of a long chain of "wait 7 days, wait 7 days, wait 7 days," use conditional splits that check how much time has passed since the date, and route to the right message for week 0, week 1, up through week 4.
here is an article from klaviyo on how to create a date property triggered flow
let me know if this works for your use-case and if you have any follow up questions.
Thank you for posting your question here in the community.
Cheers
Arpit
The birth date approach is definitely the cleanest and most scalable solution. It'll save you from maintaining huge flows and make tracking multiple children much easier.
Because they age out. The client's services are only for children - newborn to 4 years old. And within that, broken up into three main categories 0-6 months, 6-15 months, and toddlers. Someone who signed up with a 2 year old won't care about the services the client provides when their kid is 5. We are building this flow so that we can build segments off it to send emails. Not to trigger flows like you are thinking.
Log in to the Community
No account yet? Create an account
Use your Klaviyo credentials
Log in with Klaviyo
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.