After our existing drip nurture ran its course we decided to kick things up a notch. We may have gone overboard in the number of things we added, with flow steps and skipping emails, but it SHOULD be really cool. My problem is my unfamiliarity with nested Programs within the streams. I've read, and re-read the documentation, and I must be glossing over the most critical part, but I can't seem to get a consistent movement from program to program, within the stream.
So, my question is this:
The docs I can find indicate the importance of membership status within the program, as to who will get the email, and states that if it's done wrong they will stay in a loop status without getting the email, or moving on (this is where I am). But it doesn't get too in depth on what program status' are needed, what will not work or what exactly it should be to function.
So, in my stream I have Program 1, Program 2, Program 3. Some people should go from one to the other, but some should skip Program 2. Therefore, if I add the people that should skip to Program 2 as a member, with a custom status of 'skipped' before they hit that part of the stream -- what am I missing to indicate to the stream to pass them to Program 3?
My thought is that the member status 'skipped' is not a program tag value of 'success' but it shouldn't be, since that's not a success metric of the program. But does it have to be in order to successfully skip?
I realize this may be confusing - please ask questions so that I can clarify anything that's misunderstood. THANKS!
Solved! Go to Solution.
Hi JD,
By using choices, we're forcing them to skip the flow action instead of restricting them from becoming qualified for the campaign. As in nested programs, the cast is the event when the selected campaign triggers, where we have the flow action to send email - when we use choice in flow, instead of filters in smart list, the lead, though becomes qualified for the campaign, but would need to qualify for the flow action based on choices. Being a member of a smart campaign should not restrict them to get the next planned email. As per the document on product docs, the leads won’t receive the email if they’re a member of the program (not smart campaign) - We’ve observed that being a member of smart campaign doesn’t automatically makes a lead member of the program as well.
Hope this helps,
Balkar
Hi JD,
For having some leads skip the nested programs, we can use choices to filter out people from receiving content of a program, and they can receive the next program's content. The choice can be a member of smart list, where you define the criteria to be leads who should not skip program 2.
Hope this helps,
Balkar
What are the choices? When I want them to skip, I add them as a member of the campaign. But being a member, it seems that while they don't get that email (as planned) they also do not move on to the next nested program. How do I move them? I don't want them to be members of the next program because then they won't get it... I'm lost.
Hi JD,
By using choices, we're forcing them to skip the flow action instead of restricting them from becoming qualified for the campaign. As in nested programs, the cast is the event when the selected campaign triggers, where we have the flow action to send email - when we use choice in flow, instead of filters in smart list, the lead, though becomes qualified for the campaign, but would need to qualify for the flow action based on choices. Being a member of a smart campaign should not restrict them to get the next planned email. As per the document on product docs, the leads won’t receive the email if they’re a member of the program (not smart campaign) - We’ve observed that being a member of smart campaign doesn’t automatically makes a lead member of the program as well.
Hope this helps,
Balkar