This content has been marked as final. Show 4 replies
You would want your trigger to be
Newsletter becomes TRUE, then Add to Engagement.
But quite honestly, you want to keep your preference center flows centralized - separate from actual campaigns.
Then you can have an Engagement newsletter Entry campaign to listen for the Newsletter change and add to Engagement Stream 1. So you only need 1 step there, not two
I agree with Josh. I tend to have a separate opt-in program, which once they reach the program status of 'opt-in' adds them to various lists depending on what they've selected. Conversely, should they unsubscribe it removes them from these lists.
Based on their preferences you can drop them into an engagment program, but I'm not sure I'd combine preference flows with an engagement program like Josh mentioned.
So, are you saying a single engagement program for just newsletters for example would suffice (they would have to be opted in to get there in the first place from a trigger)?
I think the idea is that you make your functions more modular, so you have one program that simply manages subscriptions and keeps track of what type of communications someone is eligible to achieve (you can add/remove folks from static lists, use checkboxes on the lead record, etc.)
Then how you communicate with people can change and evolve over time and it isn't tied together.
The trigger of "Newsletter" changing to true could be what adds them to the engagement program then as you say.