2 Replies Latest reply on Sep 29, 2016 10:40 AM by Andy Varshneya

    Orchestrating lead creation triggers

    Josh Wood

      When a lead is created it is ideal to have the triggers fire in sequence prior to syncing to sfdc for a number of reasons (accuracy when running through routing rules, leads running through the right choices in workflows, etc). We have a number of trigger campaigns that fire at the same time as our initial lean cleanup/pass through daisy chain (enrichment, data validation, segmentation, etc).


      While the daisy chains fire in a desired order (request campaigns due to lack of flow dependencies) the triggers do not. This sometimes results in data issues if a lead isn't in the right segment when a flow dependent on segments fires etc.


      Looking for best practices on how other orgs setup and prioritize their "lead onboarding" flows.



        • Re: Orchestrating lead creation triggers
          JD Nelson

          Roughly trial & error, here. Any campaign that syncs to sfdc is delayed 15 min (we started at 5, then 10, now 15) in order for all campaigns to run.  Now, that being said, the only thing we have to wait for is the sync; we don't have dependent triggers that need to fire in order. I would test with wait steps in each to make sure they wait long enough for the previous trigger to finish; but there isn't going to be a scientific or perfect answer...

          • Re: Orchestrating lead creation triggers
            Andy Varshneya

            Seconding what JD said. Since the "Request Campaign" is both incredibly powerful and yet also considered very low priority by Marketo (no clue why), wait steps are the way to go here. Setting up rules the way JD has done is the safest route since you know it'll take some time for all the triggers to fire, and adding the wait step as the first action in the flow will allow you to control the order of operations.


            My wait steps are much more aggressive, giving pauses of 2, 5, and 10 minutes, but it's essentially the same exact concept.


            Kudos, JD Nelson!