Request campaign - good or bad? | Community
Skip to main content
Andy_Varshneya1
Andy_Varshneya1
New Participant
February 27, 2017
Solved

Request campaign - good or bad?

  • February 27, 2017
  • 3 replies
  • 5862 views

Over the years, I've heard a lot of information in favor of or totally against the use of the "Request Campaign" flow step. Some have said that it is the lowest priority and thus can be skipped altogether during times of heavy workload for your instance, and that in general it is also very slow. Others have said the exact opposite, saying that it is actually the highest priority and also one of the fastest ways of executing workflows.

Is there someone on Marketo's product team that can definitively say one way or the other regarding if the Request Campaign step is good or bad for building an instance that scales up with higher lead volumes?

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 Dan_Stevens_

When used properly, they are a huge time-saver.  A perfect use-case is when several smart campaigns need to reference the same flow steps.  Rather than build those flow steps in each smart campaign, build it once and then request that campaign.  For example, campaign response alerts.  Many of our programs are designed to send out an alert to the campaign manager and/or country marketer upon conversion/success.  Since there are many choices within the flow step that send out the alert to the appropriate country marketer, we build these centrally and then request them for whichever program/campaign needs them.

Another example is a central campaign for syncing leads to CRM.  Rather than include a flow step with 23 or so choices (by country) in every smart campaign where a lead may need to be synced to CRM, build it once and reference it across all the campaigns that need it.  Makes it so much easier to maintain as marketers come and go.

3 replies

Dan_Stevens_
Dan_Stevens_Accepted solution
New Participant
February 28, 2017

When used properly, they are a huge time-saver.  A perfect use-case is when several smart campaigns need to reference the same flow steps.  Rather than build those flow steps in each smart campaign, build it once and then request that campaign.  For example, campaign response alerts.  Many of our programs are designed to send out an alert to the campaign manager and/or country marketer upon conversion/success.  Since there are many choices within the flow step that send out the alert to the appropriate country marketer, we build these centrally and then request them for whichever program/campaign needs them.

Another example is a central campaign for syncing leads to CRM.  Rather than include a flow step with 23 or so choices (by country) in every smart campaign where a lead may need to be synced to CRM, build it once and reference it across all the campaigns that need it.  Makes it so much easier to maintain as marketers come and go.

Josh_Hill13
Josh_Hill13
New Participant
February 28, 2017

I agree.

Request Campaign/Campaign is Requested can be a powerful tool.

It does help if you can keep track of the reference points flowing into the trigger.

I know of one particular expert who loathes these, but it's really not that big a deal.

    Nicholas_Manojl
    Nicholas_Manojl
    New Participant
    February 28, 2017

    Not answer your actual question, unfortunately.. but here's my 2c:

    I am officially not a fan of request campaign.

    Of course it has its uses but more often than not it is a bad design choice, and makes a campaign hard to read from a marketers perspective.

      Grégoire_Miche2
      Grégoire_Miche2
      New Participant
      February 27, 2017

      Hi Andy,

      My understanding is that campaign priority is more a factor of the first step in the flow rather than of the trigger. See https://nation.marketo.com/message/139533#comment-139533

      -Greg

      Andy_Varshneya1
      Andy_Varshneya1Author
      New Participant
      February 27, 2017

      Thanks for sharing that @Grégoire Michel​! I don't understand why it's impacted by the first flow step vs second or third or etc. Is it because one a flow has started executing, every step will be executed upon regardless of resource constraints, therefore resources will be allocated to flows based on the priority of the first step?

      Grégoire_Miche2
      Grégoire_Miche2
      New Participant
      February 27, 2017

      My understanding is that the priority is set for the whole flow, not step by step. And this priority is set based on the first step in the flow.

      When the 1st flow step priority level is the same on 2 flows, then the time stamp at which each smart campaign was fired determines the priority.

      One exception, obviously: the first step after a wait. In this case, I just cannot remember what the rule is

      -Greg

        Terms & ConditionsAccessibility statement

        Loading footer...