Thank you for your help. The cloning does work. Emails are our only content… and I think since the cloned emails have different email IDs that it treats it as a new, unsent email. To simplify unsubscribes, instead of cloning the entire engagement program, we cloned the emails and put them in a separate stream in the same engagement program and transition those that complete a cycle/stream to the next stream. This requires a lot of duplication or deciding to drop subscribers after x number of cycles, which is probably what we'll have to do. If we did that, I assume if they resubscribe, they will go straight to exhausted content status?
Since it is a daily email, most people don’t notice/open every email so we do see some engagement when it comes around the second and third time etc.
In my ideal world, there would be a flow action that cleared the send history for the emails in that program so they could start the stream over. Food for thought.
... View more
Thank you for any pointers you could give me... We have an engagement program that sends daily emails similar to a 'Tip of the Day' type of product. We have limited content (90 days worth) so we would like to loop the email content because some subscribers have been subscribed for over a year. Currently, since engagement programs, by design, won't send emails that have been sent before (based on email ID alone, I believe), we clone emails and create separate streams, and move those with exhausted content over to the new stream. This we do every 90 days and would like to avoid this duplication if possible. My understanding is that removing someone from an engagement program and re-adding them will not reset their email sent history, so to speak. So is there a better way to loop content? Or is there a way to allow for repeat content?
... View more