Nested email program in Engagement Stream

[Anonymous]

What am I doing wrong here? My nested email program smart list is triggered by email 1 is delivered. The flow step is to wait 6 days til 8am and send the second email.

[Grégoire_Miche2]

Hi AMy,

If the nested email program is triggered by the 1 emails being delivered, you do not need to add it to the stream. The trigger will simply do it's job.

-Greg

[Anonymous]

I'm getting the following error. WHat am I doing wrong?

[Grégoire_Miche2]

Do not try to activate it and remove it from the stream, it's unnecessary. The trigger already does the job.

-Greg

[Anonymous]

Ok so how would the system know when the stream is exhausted? Right now, email 1 is the only one in the stream. Then I have a nested program inside my nurture that is triggers when email 1 is delivered, then wait 6 days in the future, and send the second email.

So that doesn't need to be in the stream view?

[Grégoire_Miche2]

Hi AMy,

No, the trigger campaign waits for the deliverance of the email and does the rest.

But, in fact, what you want to achieve (an invite and a reminder with the same email sent twice, but not to the leads who hard bounced on the first time), does not require a engagement program. A simple default program with 1 email and a batch smart campaign with the following flow would be enough :

1. send email 1
2. wait 6 days
3. send email - > choice : if email was delivered (emal is email 1) then send email 1

or

1. send email 1
2. wait 6 days
3. send email - > choice : if email is invalid, do nothing, else send email 1

-Greg

[Anonymous]

There will likely be additional emails behind the first 2. But I'm essentially setting this up for sales to use on demand. So setting up a stream instead of a 1 time email send program I how I thought I needed to approach it.

We just started with Marketo a few months ago so I'm still learning.

All your advice is much appreciated.

[Grégoire_Miche2]

Hi again Amy

Even if there is additional email in the future, as soon as you want to introduce conditions or send the same email multiple times, a standard program with a campaign is a better choice. Engagement programs are better for weekly or monthly emails (6 days wait for instance in not possible) that different each time and really nurture the lead at different stage of the funnel.

Also, testing if the previous email was delivered is not necessary : if the email address bounced hard on the previous email, Marketo will automatically filter it out next time you will attempt to send an email to that lead.

If you need a flow that sales can trigger on demand, and if your sales team use Sales Insight, the bet thing might be to design a campaign that sends all emails in a row with the wait periods in between, and set it as a triggered campaign with the "campaign is requested" trigger, with source is "sales insight". Then sales will be able at any point to add a lead or a contact to the campaign from the CRM (SFDC or MSD) using the "add to Marketo campaign" feature in sales insight.

-Greg

[Josh_Hill13]

NEsted programs just need a special campaign that says

Member of Engagement in Stream X

no activation, then drop into the stream.