SOLVED
We recently set up an engagement program in which we want emails to be sent every 2 weeks. We also included multiple days that emails could send: Tues, Wed, Thurs. (See screenshot below for set up). The reason for this was:
1) If new members come in after the email is sent (say on a Tuesday) we don't want them to wait 2 weeks to start
2) We have daily limit set in our instance, so if they reached the daily limit for that cast we didn't want them to wait 2 weeks for the next email, as that would mean 4 weeks between emails for this engagement program.
What happened is that emails were sent 3 consecutive days instead of waiting 2 weeks. For example, people that received email 1 on Tuesday, received email 2 the next day on Wednesday, and email 3 the next day on Thursday.
Is this the behavior that is supposed to happen with this set up? We expected that if they received email 1 on Tuesday, it would wait and send email 2 on Tuesday 2 weeks later.
We are also using email programs and not email messages in the Streams. Would this impact the behavior?
Any insight into what is the expected behavior and thoughts into how we could set this up correctly to achieve our desired behavior would be appreciated.
1 ACCEPTED SOLUTION
Accepted Solutions
Is this the behavior that is supposed to happen with this set up? We expected that if they received email 1 on Tuesday, it would wait and send email 2 on Tuesday 2 weeks later.
What happened is exactly in line with what you've configured, but not quite in line with what you expected. The schedule that you've set up translates to: run the stream cast on Tuesday, Wednesday, and Thursday every 2 weeks (in total the stream would do 3 nurture casts every 2 weeks, i.e., 3 casts in week 1, no casts the following week, and then 3 nurture casts the week after.)
We are also using email programs and not email messages in the Streams. Would this impact the behavior?
This doesn't impact the way streams cast the content, you'd have seen the same results even if you'd have used the plain email assets in the stream.
@janetmb wrote:
We recently set up an engagement program in which we want emails to be sent every 2 weeks. We also included multiple days that emails could send: Tues, Wed, Thurs. (See screenshot below for set up). The reason for this was:
1) If new members come in after the email is sent (say on a Tuesday) we don't want them to wait 2 weeks to start
2) We have daily limit set in our instance, so if they reached the daily limit for that cast we didn't want them to wait 2 weeks for the next email, as that would mean 4 weeks between emails for this engagement program.
1) You could send the first welcome email via a trigger campaign to ensure the email is sent to the person as soon as they are added to the nurture. You can also use the advanced wait properties so people who get added to the nurture outside of business hours receive the 1st email on the next business day. Once this email is sent, you can then add people to the engagement program's correct stream so people would receive the subsequent content in the next cast. If you decide to go via this approach, make sure to remove the 1st content offer from the engagement program's streams.
2) This is def. a curve ball; essentially, you could run a batch campaign every week that sends the next nurture email to the person the following week. Make sure to add this person as a member of the nested default program for which you've sent content via the batch campaign so it gets skipped in the next regular cast of the engagement program stream. I wouldn't recommend going the extra mile to set this up unless you really want to, as setting something of this sort doesn't guarantee that the person would receive the nurture email still (in case the person has already exhausted the email comm limit for the next week before this batch campaign runs) and this would essentially disturb your bi-weekly regular nurture cadence. You should do the lead nurturing with regular default programs and send campaigns instead of relying on the engagement program and creating a ton of setup to modify how it operates OOTB. Hope this helps. Let us know if you have any additional questions.
Is this the behavior that is supposed to happen with this set up? We expected that if they received email 1 on Tuesday, it would wait and send email 2 on Tuesday 2 weeks later.
What happened is exactly in line with what you've configured, but not quite in line with what you expected. The schedule that you've set up translates to: run the stream cast on Tuesday, Wednesday, and Thursday every 2 weeks (in total the stream would do 3 nurture casts every 2 weeks, i.e., 3 casts in week 1, no casts the following week, and then 3 nurture casts the week after.)
We are also using email programs and not email messages in the Streams. Would this impact the behavior?
This doesn't impact the way streams cast the content, you'd have seen the same results even if you'd have used the plain email assets in the stream.
@janetmb wrote:
We recently set up an engagement program in which we want emails to be sent every 2 weeks. We also included multiple days that emails could send: Tues, Wed, Thurs. (See screenshot below for set up). The reason for this was:
1) If new members come in after the email is sent (say on a Tuesday) we don't want them to wait 2 weeks to start
2) We have daily limit set in our instance, so if they reached the daily limit for that cast we didn't want them to wait 2 weeks for the next email, as that would mean 4 weeks between emails for this engagement program.
1) You could send the first welcome email via a trigger campaign to ensure the email is sent to the person as soon as they are added to the nurture. You can also use the advanced wait properties so people who get added to the nurture outside of business hours receive the 1st email on the next business day. Once this email is sent, you can then add people to the engagement program's correct stream so people would receive the subsequent content in the next cast. If you decide to go via this approach, make sure to remove the 1st content offer from the engagement program's streams.
2) This is def. a curve ball; essentially, you could run a batch campaign every week that sends the next nurture email to the person the following week. Make sure to add this person as a member of the nested default program for which you've sent content via the batch campaign so it gets skipped in the next regular cast of the engagement program stream. I wouldn't recommend going the extra mile to set this up unless you really want to, as setting something of this sort doesn't guarantee that the person would receive the nurture email still (in case the person has already exhausted the email comm limit for the next week before this batch campaign runs) and this would essentially disturb your bi-weekly regular nurture cadence. You should do the lead nurturing with regular default programs and send campaigns instead of relying on the engagement program and creating a ton of setup to modify how it operates OOTB. Hope this helps. Let us know if you have any additional questions.
.png)