We’ve barely scratched the surface of what we can do with our automation sharing feature. We’ve got some exciting plans though.
In the meantime, I thought we could get a thread going to pass our favorite automations around.
Do you have any you can share?
Good idea Brian!
It would be very interesting to see what everyone will share.
Here’s a simple one to tag people who are not engaged anymore: http://tplshare.com/TbeqZ8e
Every time someone subscribes, he enters this automation. Each 60 days, if he has not opened any email, he’ll be tagged as “disengaged”.
From there, you can place another automation where you can re-engage contacts that are disengaged.
Hare are some automations I use to tag based on email click/open recency. They adds tags based on time passed since link click or email open.
This is advantageous for 2 reasons. One is the obvious ability to clean out those who aren’t actively opening or clicking your emails. The second is if you’re sending an offer you can send to those who have clicked a link in the last 7 days, those who are most recently engaged.
There are two automations for each. There is a Start automation and the automation that adds the tags. The Start automation waits for the activity. When it starts it clears all prior tags and stops the tagging automation. I find this easier to work with than 1 automation that kept running.
This is the click recency start automation: http://tplshare.com/YVrNs3T
It is set to start this automation after it has run and cleared all the prior tags: http://tplshare.com/AQglGuW
This is the open recency start automation: http://tplshare.com/nEkamE7
And after it runs it starts this tagging automation: http://tplshare.com/IWVFs2S
It may seem a little cumbersome to have multiple automations but it works best and keeps everything flowing smooth. When I had these as 1 automation it kept running and the user would have dozens of the automation running at the same time adding and removing tags. This is easier and automatically restarts the tagging for you.
Enjoy.
For anyone interested in automations, today we published a series of automation workflows on our blog. If you missed the last automation sharing post, here’s that one.
Hi @mfox. Thanks for the contribution here. I’m wondering what your trigger is for Email Open Recency Tagging and Email Click Recency Tagging? If it’s simple a click/open/subscribe, wouldn’t the ‘Start’ automations remove users from these ones as soon as they act?
@willrussellmarketing I’m not fully understanding your question but I’ll answer to what I think you’re asking.
There are the two ‘Start’ automations. Those are triggered when someone clicks/opens/subscribes. These remove any of the tags in the Open and Click Recency Tagging automations and ends the Open and Click Recency Tagging automation. Then, they restart the Open and Click Recency Tagging from the beginning.
I originally set this up as 1 automation but I noticed there were multiple instances of the automation running. It was removing prior tags and I noticed contacts with a 7 day tag AND a 30 day tag. That was bad and meant they would end up getting the 60 day email when they shouldn’t.
If I didn’t answer your question, please fire away again with more detail please.
Thanks for the response. Apologies for lack of clarity.
In these two instances, are clicks/opens/subscribes the trigger for both the ‘Start’ automation and the main automation?
Or, from what I read in your message, the beginning of the Open and Click Recency Tagging automations is triggered by the end of the ‘Start’ automations, and therefore require no start trigger themselves?
Thanks again!
Ah. Got it now.
Yes. Exactly correct. There is no start trigger in the Tagging Automations. They are started at the end of the ‘Start’ Automation.
These two automations tag contacts as engaged if they opened an email in the last 60 days and disengaged if it’s been over 60 days:
PART 1: Engaged (restart disengaged) — http://tplshare.com/672flq2
This automation starts every time an email campaign is opened. If they are already in Part 2 (indicated by the “waiting” tag) then it ends that automation and restarts it. If they aren’t in it yet, they are dropped into Part 2 and the automation ends.
PART 2: Disengaged? (waiting) — http://tplshare.com/GQHjiQU
This automation tags them as engaged, removes disengaged tags (if they exist), tags them as waiting, and then has them wait 60 days. If the 60-day wait expires (they haven’t been restarted by triggering Part 1 by opening an email) it tags them as disengaged and ends.
Depending on how you want to define “engaged,” you could easily modify Part 1 to have additional triggers for “Visited Web Page” or “Clicked a link.”
Thanks again @Barry for pointing out the issue with the other “disengaged” automation. For the past few days, creating this automation has been my white whale. After testing many approaches, and hitting a brick wall each time for one reason or another, I believe this is a working solution.
This is just brilliant! Thanks a lot Brian for sharing it, I’m going to exchange my disengagement automation with yours.
And you just proved that with creativity a person can bypass a situation that others think as a limit.
These are awesome words to live by!
Which other “disengaged” automation are you referring to that has a problem that @Barry pointed out? The one shared at the beginning of this thread by @emmed? Just want to make sure I grab the right automation.
Hi Enoch —
The automation that @emmed posted was the one I was referring to. It’s not so much that it won’t work, but it serves a more specific purpose. That automation will tag contacts as disengaged if they have never opened an email.
The issue is that once they open a campaign, any campaign, it will always send them to the No condition and loop them back through because the “has opened” condition is a simple yes/no and it doesn’t “care” about the 60 day wait.
The automations I posted will look for activity over the past 60 days and tag them as disengaged if they haven’t opened an email in the last 60 days.
@Brian just so I can be clear:
You are saying that if someone is in the “wait 60 days” part of the automation by @emmed then as soon as they open a campaign they will proceed through the yes/no condition and then go back up to the “wait 60 days” action?
If there is a yes/no condition after a wait then the wait is ignored?
The only issue with that automation is that if a contact opens a campaign at any point in time, they will never make it to the “Yes” condition that would tag them as disengaged. They will just continuously loop in the “No” condition because ActiveCampaign will check “Have they opened a campaign at any point in time?” Yes, they have, so “No, they don’t meet the condition ‘Has not opened any campaigns.’”
Basically, once they open an email, they get stuck in a loop that waits 60 days and then checks if they’ve ever opened a campaign.
That automation could be used to identify “dead” subscribers and bogus email addresses. I’d just remove the loop on the “No” condition so no one gets stuck in it.
I hope that was clear. If not, let me know and I’ll come at it from another angle.
Ahh! Yes perfectly clear. Thanks @Brian. So in that case, I’m glad I grabbed your 2 automations that cycle back and forth.
Enoch ‘the thick-skull’ Sears
Haha. Please don’t feel like that was a dumb question at all. I’m still trying to find the best way to breakdown and explain what an automation is doing. It’s not easy to understand how the logic and actions interact — especially if you are new to the platform.
HI @mfox - Thanks again for sharing these automations.
Quick question. Now that I’ve had these all running for a month, my reports for these are showing significantly more contacts in them than I actually have in AC.
For example, when I look at the report for the ‘Email Open’ automations some of the contacts are in there are being listed multiple times. In fact, the first email address that displays in the report is there 8 times.
Have I set it up wrong, or is this how it should be? If the latter, could you explain why each contact is displaying multiple times?
I appreciate the help!
Will
Question on these great automations, @Brian. Does ‘Disengaged? (Waiting)’ have no start trigger?