What happens with 2 concurrent automations?

Hi there,

I am setting up an evergreen sequence, that will have links to occasional promotions.

Those promotions would be triggered by someone getting tagged when they click on a link to get more info.

I plan to email regularly to build a relationship on the evergreen list.

I am worried people will get double emails on some days, one from the promo campaign and then the regular evergreen campaign.

How can I handle it so the promo replaces the evergreen daily sequence for a few days for those subscribers who have expressed and interest, then the evergreen one resumes?

I am only on day 2 with AC, so apologies if this has been asked before.

Thanks.

1 Like

Hi Colette,

One was to do this would be to add"pause" between each of your email messages in the evergreen campaign where you could check for a tag telling that campaign to wait.

So if you had a tag named PauseEverCamp you would do something like this:

Have the promotional campaign

  • apply the PauseEverCamp tag
  • send the email
  • wait some period of time
  • remove the PauseEverCamp tag

Between each message of the evergreen campaign you would

  • wait 1 day (or how many you want)
  • wait until conditions met (tag PauseEverCamp doesn’t exist)
  • send next email

HTH

1 Like

Thanks :slight_smile:

I think with and if else conditional statement I can get it to work.

  • Pre branch evergreen email with promo link - tag interested readers
  • if reader is tagged evergreen AND promo do this branch
  • else if reader is tagged evergreen only, do that branch
    *make the branches the same duration
  • use goto to on promo branch to return to main sequence

That might do it?

There’s always more than one way to tackle these things :slight_smile: - give it a shot!

1 Like

While there are multiple way sot do a lot in automations, I will say it’s best to look a year down the road. What if you have four lead magnets with appropriate email automations on top of promotions and other things. This is where tagging is helpful. I tag people with my product tags when they buy the product. Then, if there is an automation that promotes that product, I make sure that people with that tag are omitted.

1 Like

Colette, many paths lead to the same peak as @rebar says. IMO the best way to accomplish what you’re trying to do would be to do this:

and then this:

You can install these both here and here.

Set your wait timer to the minimum interval of ineligibility after sending a promo and this will make sure the recipient never gets a promo more than 1x/mo. As @tigergreenproduction advocates, you ideally want a durable, robust solution like this one that will work in any situation and accommodate you down the road as complexity blossoms. This is a modular approach and you can always get fancy with it if you wanted to add branching logic and tags for rotating different flavors of promos.

With visualizing this stuff it’s helpful for me to picture scenes that personify what I need. The way I imagine this specific scenario is that the first automation is just a gatekeeper guy checking to see if the “light switch” is on or off every time the visitor indicates interest. When it’s on he calls up the delivery man to execute the promo who then turns off the light switch for a month and re-enables it a month later when the recipient is eligible again. You can then start to think about who else they would need to call and what activities they would perform if you want to get more sophisticated with it.

FYI I teach a bunch of this stuff in my ACmastery.com course if you’re interested. White belt level is free and it’s fairly affordable for more advanced belts plus you can join our private monthly mastermind where we help you power through challenges like this. Good luck.

1 Like