Add Hourly Recurrence Frequency to Batch Smart Campaigns

[Ashley_Chavez]

Pretty self-explanatory. I have a batch smart campaign that I need to run every hour on a daily basis with no end date. Since "hour" is not a frequency option, I had to create 24 recurring batch smart campaigns to achieve this result. I'd much prefer to manage this through on smart campaign, as opposed to 24!

[Justin_Cooperm2]

It will help us evaluate this idea if you explain the use case a bit. What is the campaign doing every hour?

[Anonymous]

I have a series of batch campaigns set up to clear two MQL fields (check box and a date stamp) when certain scenarios take place: we're able to identify the company isn't a fit, bad location fit, etc.

[Anonymous]

We want this to send emails to people who did something a little under a day ago (at the time they did the action). See Re: Can you trigger on score changes 24 hours ago without a wait step?

[Devraj_Grewal]

In my case, a group of prospects get marked a certain status when an email is delivered (ex. Stage 2). The next day at 6AM, we want to change a data value for these Stage 2 prospects so our business development team knows to call them that business day and move them to Stage 3. However, the email being delivered happens over the course of many hours. So not everyone will be delivered the email and changed to Stage 2 by the time the batch campaign is running the next morning at 6AM to change the data value for all those at Stage 2. So instead of the batch campaign running one time to change the data value, it would be beneficial to have it running hourly so it catches any prospects who are changed to Stage 2 after the first run at 6AM.

[Justin_Cooperm2]

Why don't you just use a trigger campaign?

[Devraj_Grewal]

The reason is that I would need to create a separate trigger campaign just for the one-off cases of data value changes and then need to have it activated for just the next day because I do not want to mark that data value until the next morning. Since I also cannot schedule a triggered campaign to activate on a certain day, it would be much simpler and less susceptible to error if I just run the batch more often.

[Casey_Grimes]

This feature would be especially useful when you have trigger campaigns that need somewhat regular updates but do not need to happen immediately--some examples I can think of off the top of my head are scoring campaigns (which you may want to update during the day but non-exception scores probably don't need to happen in real time), program status changes for emails, lead lifecycle corrections (I usually run nightly campaigns to ensure records that may have had race conditions and wound up getting different values re-align), etc.

Basically, any time you don't have anything high-priority enough to justify a trigger on a mature instance in order to keep performance high.

[Wyatt_Bales4]

From experience, Marketo's ability to trigger off-of Account updates isn't 100% reliable. However, batch campaigns are more accurate when qualifying records based on Account-level fields. Currently we're facing issues with Opp constraints preventing triggers from working but yet batch campaigns work (there's a Support case open). I understand have an hourly campaign isn't ideal from a system perspective but a "once every 3 hours" option would be great at least.

[Srujan_Vishwana]

I think the frequency of firing off batch campaigns should be unique to each Marketo instance. As Wyatt Bales​ says 'once every 3 hours' works for them, Marketo should be able to provide that flexibility for each instance.