5 Replies Latest reply on Jan 31, 2018 8:35 AM by Grégoire Michel

    One nurture, two streams in parallel rather than moving one to other?

    Shelly Wilson

      Ok..so I'm trying to muddle my way through Marketo's functionality. This week I set up a nurture programme with 2 streams. The goal is to differentiate activity/engagement between two different audiences getting the exact same content. Stream 1 is for newest leads in database. Stream 2 is for the rest of the database. For both streams, I've set the trigger as 'received email', which is an email sent from a batch campaign (I created two emails with same content but different titles going to different audiences to trigger each respective stream). And then I've added additional filters to each stream's transition rules to achieve the segmentation I want (example, Stream 1 (new leads)= received webinar email for new leads, plus IS Member of previous new leads program, plus NOT member or previous 'rest of database' program. Stream 2 (rest of database)= received webinar email for rest of database, plus IS Member of previous rest of database program, plus NOT member of previous new leads program).

       

      Then each stream is set up to get identical emails in same cadence.

       

      Does that set up sound correct for what I'm trying to achieve? Can you use streams to send a series same content to two different audiences? Or do streams only function by moving person from Stream 1 to Stream 2?

        • Re: One nurture, two streams in parallel rather than moving one to other?
          Grégoire Michel

          Hi Shelly,

           

          A few best practices rules when using nurturing programs:

          • in the smart campaigns that add persons to the streams, use iflters (batch) not triggers. Real time is not necessary here. In the “add to engagement program" flow step you can set the stream, so you do not need to add anything in the transition rules.
          • Always contain everything related to the engagement program in the engagement program. Meaning the smart campaigns that adds persons to the streams should be stored within the EP. This is for an easier maintenance
          • Do not use transition rules at all, always use smart campaigns to move people from ne stream to another. They are easier to debug and maintain and they provide more flexibility. Here as well, batch is good enough, you do not need triggers.

           

          -Greg

          4 of 4 people found this helpful