Most of the documentation out there about using engagement programs shows you just dropping emails directly into the stream. However, you can also drop programs into them, and there are many situations where you might want to put your email inside of a program instead of directly into the stream.
Why use nested programs?
There's a lot of confusion out there about how things work when you put programs inside a nurture. To clear up the confusion and confirm my own experience, I did a lot of testing of all kinds of scenarios, such as:
The three main conclusions:
1. When using nested programs, deciding whether or not to send the email to a person is based on:
What this means is that it does not matter if the person already got the email or not. If the person is a member of the program, they will not get that email. If they are not a member of the program, but have gone through that program ID before in the nurture program, they will not get that email. Only if you are brand new to the program will you get that email.
2. You can reuse an email someone has already gotten if you put it in a new program, regardless of where the email is stored (Design Studio, local to the program, local to another program).
The main difference with these options is the reporting and ease of use. When you use a Design Studio email in multiple programs in an engagement stream, the different sends are treated as separate sends in the Engagement Stream Performance report. In the regular Email Performance report, they are treated as the same email and all the metrics are rolled up into one line.
3. If you want to resend something, it is always safest to create a new program and smart campaign.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.