AnsweredAssumed Answered

Overly complex engagement, likely a simple oversight problem

Question asked by dd34a3d5d8f9572e3905b50f127a3c0521eaf4fe on Jan 23, 2017
Latest reply on Jan 25, 2017 by 7ee334e3640daccdf4bfbed44802e4f935cb37f6

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!