Order of Execution of Campaigns | Community
Skip to main content
A
Anonymous
July 1, 2014
Solved

Order of Execution of Campaigns

  • July 1, 2014
  • 3 replies
  • 1549 views
Say I have multiple campaigns that all run with the trigger Lead is Created. Any suggestions on how I can control the order that they execute. 

For example,

Campaign 1: Lead is created, changes status to x if y.
Campaign 2: Lead is created, change status to b if c. 


I know I could do a "Wait for 5 minutes" in the flow for one of them, but that causes delays and not a good solution as I scale.

Let me know if anyone has any thoughts!
Thanks,
Mike
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Valerie_Armstro

Hi Mike,

Have you considered utilizing "Request Campaign"?  This way, you have campaign 2 execute once the flow steps of campaign one have been completed.

Campaign 1:  
IF: Lead is created,
THEN: Changes status x if y,  request campaign: campaign 2

Campaign 2:
IF: Campaign is requested (Marketo Flow Action)
THEN: change status to b if c.

Hope this helps! 
-Val

3 replies

A
Anonymous
July 1, 2014
Instead of a wait step you could have "data value changes" as your trigger for subsequent campaigns, and have the action in the first campaign be the trigger for  the second campaign.
Valerie_Armstro
Valerie_ArmstroAccepted solution
Level 9
July 1, 2014

Hi Mike,

Have you considered utilizing "Request Campaign"?  This way, you have campaign 2 execute once the flow steps of campaign one have been completed.

Campaign 1:  
IF: Lead is created,
THEN: Changes status x if y,  request campaign: campaign 2

Campaign 2:
IF: Campaign is requested (Marketo Flow Action)
THEN: change status to b if c.

Hope this helps! 
-Val

A
Anonymous
July 1, 2014
Thanks for the responses ladies.

Michelle, that could work but there are other situations when the data value will change.

Valerie, that's exactly what I was looking for. I was not aware of theRequest Campaign trigger. Thanks!

-Mike
Terms & ConditionsAccessibility statement

Loading footer...