Marketo Nation,
I am trying to migrate a series of emails from another system into Marketo. These emails in our other system were all set up individually and go out on set days after someone downloads our app (e.g. Day 1, Day 3, Day 7, Day 12, etc.).
The complication is that we want to send unique emails at certain steps in the process based on the user’s engagement with the app (uploaded documents, invited others, etc.). We would prefer not to use dynamic content for these emails, because we would like to layer on additional dynamic content based on certain user profiles.
We also cannot just create separate nurture journeys, because we need it to be updated in real time, and not just at the beginning of the journey. For example, if someone invites someone in the app on day 6, the email they receive on day 7 should reflect that.
We have looked in to using a standard Marketo Stream nurture flow, but we are struggling with how to guarantee that the emails will go out on the exact days we specify (e.g. Day 1, Day 3, Day 7, Day 12, etc.) and not accidentally send emails too close together and annoy our users. Using that same example, if we created an “Invited another user” stream, and they invited another user on Day 6, how could we prevent the system from “resetting the clock” on when they get an email in the next stream (we would need to keep the exact same email cadence as users move between streams).
Any thoughts on the best way to do this (without just recreating all of the emails individually) would be appreciated!
Thanks!
Charlie
Solved! Go to Solution.
Hi Charlie,
My take on the build:
You could still build an engagement program that has the relevant streams and create a logic that allows each user to individually enter the engagement program and flow through in their own cadence.
You will not be able to send the email in the recipient time zone if you are using a default email program in the stream.
Summary:This allows each user to go through the engagement program in their own cadence and if you move the user to another stream, the user should retain their "pause" from engagement program and on resuming they will be moved into another stream. The engagement stream will go through the cadence everyday, find the records that are in "normal" status and execute the relevant programs.
Regarding the actual content of the emails? I do not see an alternative other than using dynamic content or individual emails. You could add individual emails depending on their journey as a choice step in the send email flow step.
Just my 2 cents.
Let me know what you think
Thanks
Floyd