Nurturing and Streams for Email Preference Center | Community
Skip to main content
January 22, 2015
Question

Nurturing and Streams for Email Preference Center

  • January 22, 2015
  • 4 replies
  • 1412 views
I want to create a process for an email preference center that we are prototyping. I have the EPC created with different areas of interest leads can select from. An intital email blast would go out to inactive leads first to get them to the landing page. 

I also want to use the nurturing channel for my program because using different themed streams would help move them to their appropriate track. 

My questions -  is this good practice? Also, for the smart list not sure what the trigger would be?  Here is my initial smart list:



And here is my intial Flow:


I'd appreciate any feedback or best practice with what I've created thus far. Thanks!
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

Josh_Hill13
Level 10
January 22, 2015
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
Kristen_Malkov1
Level 7
January 22, 2015
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.
January 23, 2015
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)? 
January 23, 2015
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.