I'll use this example, even though there's the new Mail Program type, where I built a complete mail blast program.
The program has these assets:
- Email - Email
- Trigger - Opens email
- Trigger - Clicks any link
- Trigger - Conversion
- Trigger - Unsubscribes
- Report
- Campaign - Master
The triggers refer to the email in the smartlist and in the flow they update the program status accordingly. The master campaign has a dummy smartlist with recipients and some of the criteria we always use and the flow sends the email, updates the program status to Sent, and sends it again if they didn't open the email in 3 working days. Some of the assets also use program tokens so you only need to set them once.
The idea behind this is that when you clone the program all the new assets are still connected to the new assets in the same way the original program was. In other words a marketer would only need to update the texts in the email and the smartlist with recipients in the master campaign and they are done.
- This saves a huge ammount of time
- Reduces issues and fault
- Creates consistancy in all campaigns
Als omake sure people only clone directly from the original dummy campaign, which you keep up-to-date. This will make sure all campaigns are always using the latest settings. And it prevents clones from clones, as every little (css) mistake gets cloned over and over again, untill there are dozens of issue with your emails (e.g. MsWord tags).
.png)