Nurture emails sent at specific times

JC100
Level 2

Nurture emails sent at specific times

Hello everyone,

 

We're having trouble setting up Nurture emails to be sent at specific times.

 

We have three different emails that need to be sent at different times: email05-mar in March, email05-apr in April, and email05-may in May. These three emails belong to a single campaign called Email05.

 

We've set up the availability of each email in the Streams section, but we're having difficulty in the Flow of the Send Email campaign for Email05. Specifically, we can't use the "Add Choice" option to set up rules like "If the system date is between March 1st and March 31st, send email05-mar."

 

We considered creating three campaigns with a recurrence during a specific time range, but the frequency itself became an issue. Alternatively, we're wondering if it's possible to add three Send Email actions to the flow and let the stream availability control which email is sent out.

 

Any advice would be greatly appreciated.

 

1 REPLY 1
Darshil_Shah1
Level 10 - Community Advisor + Adobe Champion

Re: Nurture emails sent at specific times

What's the frequency of the email send? (weekly 1x, 2x)? I bet if you're able to set the required frequency in the engagement program stream, you'd be able to set it in the normal smart campaign as well. You could also create 3 separate streams to house 3 content pieces and transition people to the correct stream at the start of each month, or as per your requirement (e.g., transition eligible people to the April stream at the beginning of April month)? This would work until you don't need to send months-wise emails simultaneously to people, as a person cannot co-exist in multiple streams. Also, creating a default program setup with static lists, a couple of operational campaigns, and a campaigns for sending out each month’s email sounds better than creating an EP with 3 streams (with just 1 content in each) to accommodate different send times. Also, with regards to stream content availability, once the availability of an cotent ends (or of the availablility date is in future), it'd be as if the content isn't present in the stream and using this in conjunction with 3 send flow steps might not work (and doesn't appear to be the best way out here).