3 Replies Latest reply on Aug 15, 2016 1:36 PM by abf3599aa3ffbdff022d2c8fa778b6f7e3348362

    Random Sample and Remove from Flow

      We recently implemented operational emails to our customers to be sent out of Marketo.  In some instances we would want a percentage of customers to receive their notice that their release is available, but need these to be sent each week in order to not overwhelm support.

       

      Thinking of using random sample and remove from flow.

      Step 1: If Random Sample is 10

      Send Email

      Step 2: if was sent email

      Remove from flow

      Step 3: Wait 1 week

       

      Repeat steps as necessary, but the last week would not name a random sample number so the remainder of the contacts will receive the notice.

       

      Has anybody ever looked at doing this kind of batch email send?

        • Re: Random Sample and Remove from Flow
          Josh Hill

          Sure.

           

          It's probably better to setup a batch to randomly assign people to a Static List and then to use

           

          if List 1, Send Email

          Wait 1 week

          if List 2, Send Email

          etc

           

          The problem with your setup is if I do Random Sample each time, then we can't be sure 100% of the people will get their list.

           

          The other consideration is this Main Group static, or will it be a continuous change. That might change my answer.

          1 of 1 people found this helpful
            • Re: Random Sample and Remove from Flow

              No, the list will not be static.  Will be using the smart list in the smart campaign, but once i set the campaign to run no others will be added to the flow as it will only be ran once.  Once the contacts enter the flow the contacts will just run thru the steps I mentioned.  Of course the last step will not have a random sample so the remainder of the list would be receive the email the final week.

               

              The reason why I do not prefer to use static lists for this is because we are trying to keep this as simple as possible so Support can run these with minimal steps.  They are basically just cloning programs from templates we are creating where we are building the logic already built in so all they need to do is update the email.  They are not going to want to add contacts to a list before each send and my manager doesn't necessarily want me too involved in the set up, with the exception of list validation and a few minor tweaks.  Trying to make it as automated as i can with minimal heaving lifting moving forward.

            • Re: Random Sample and Remove from Flow

              I see what you are saying Sanford.  It took me a minute, but I finally go there.  Looks like I need to set up an increasing random sample for each step so exactly 10% of the original list will be added each week.

               

              Week 1 is 10% (if sent email, then remove from flow)

              Week 2 is 11% (if sent email, then remove from flow)

              Week 3 is 13% (if sent email, then remove from flow)

              Week 4 is 14% (if sent email, then remove from flow)

              Week 5 is 17% (if sent email, then remove from flow)

              Week 6 is 20% (if sent email, then remove from flow)

              Week 7 is 25% (if sent email, then remove from flow)

              Week 8 is 33% (if sent email, then remove from flow)

              Week 9 is 50% (if sent email, then remove from flow)

              Week 10 is 100%