Campaign is Requested best practices

[WY]

Hi guys, 

How do you explain this trigger in Marketo in the easiest way, please?
And what are some of the Marketo best practices to use this trigger in campaigns? 

Any ideas are much appreciated! 
Many thanks

[Katja_Keesom · Accepted solution]

This would be a trigger that goes hand in hand with the flow step "Request campaign" that you would use in a different smart campaign. A common use case would be a central process that can be triggered from several local programs' smart campaigns or a daisy chain type process where you let someone run through a flow, wait for a number of days and then run a new smart campaign with a new set of filters to run the next step in the process.

There is an alternative process nowadays called "Execute campaign", so please make sure to use the best solution for your use case.

[WY]

Hi, @Katja_Keesom 
Thank your for your reply. Apart from goes hand in hand with the flow step 'Request Campaign'. What are some of the scenarios where you would use only the 'Campaign is Requested, source is Marketo Flow Action' in a smart campaign without requesting another campaign somewhere? 

As for the new process 'Execute Campaign', I know there are a lot of documentation out there, it is still a bit confusing to understand. How would you explain to someone (limited marketo knowledge) the simplest way on this new process, please? 

Thanks again for your help : ) 

[SanfordWhiteman]

---

What are some of the scenarios where you would use only the 'Campaign is Requested, source is Marketo Flow Action' in a smart campaign without requesting another campaign somewhere?

---

There are none. This doesn’t make sense: a requestable campaign that’s never requested does nothing.

Of course you can request a campaign using the API (so Marketo Flow Action isn’t the only option). But if you never request it using the applicable method, why would you have it as a trigger?

[EllenSchwier]

Hi,

It might help to think about Executable Campaigns versus Campaign is Requested in terms of multiple smart campaigns.

Smart Campaign number 1 is your main one. 

Smart Campaign 2 is requested.

Smart Campaign 3 is executed.

Smart Campaign 1 will pause all other steps until the executable campaign is done running, while the requested campaign will happen at the same time. My classic example is having an executable campaign to clean up country values before you continue with the Flow steps that use country to determine specific data values.  But a requested campaign needs to happen after a specific step (but nothing else is dependent on it).