New Date Conditions Available

To squeeze the most out of ActiveCampaign, it helps to familiarize yourself with the segment builder and the conditions and data it uses. The Segment Builder appears in many places. It’s used to create segments of lists, of course, but it’s also used to:

  • Create forks in automations so contacts are treated differently (using the “If / Else” action)
  • Define Goal conditions
  • Create “Wait until…” conditions in automations
  • Create contact & lead scoring rules
  • Perform advanced searches and then bulk edit contacts
  • Filter the contacts who enter an automation.

So the conditions available to you in the segment builder are intertwined with the capabilities of the platform itself. When new segment conditions are added, it’s a pretty big deal because it enables you to do more with a number of different features.

We added Goal conditions not too long ago and today we’re excited to announce an improvement to the segment builder that has been requested by many of our most ardent advocates — better handling of dates.

Now when you have a custom date field, you are able to create conditions such as “The current date is 10 days before [custom field date]” and “The current date is 3 days after [custom field date]”

So now you can do an advanced search to find clients whose contracts expire in the next 30 days. You can have an automation treat contacts differently depending on when their free trial expires. You can have a contact’s score go up if they indicate they are making a purchase decision in the next 30 days.

This is also a helpful addition for those of you that run webinars and events.

Your automations can have “Wait until…” conditions that drip out reminders 7 days before and then the day before your webinar. You can create Goal actions so that a contact skips ahead to the correct portion of the automation based on when the webinar is happening.

These new condition options are already live in your ActiveCampaign account so you can start using them now.

We understand that the addition of these conditions doesn’t resolve all date-related situations, so we’ll continue adding to our date-based functionality as time goes on.

A trial is worth a thousand words.
Get started today, no credit card required.

 
 
  • AWESOME! This Opens a whole new world. You Guys ROCK!

  • Evielyn Chapman

    I LOVE THIS! You guys just made my life SO much easier

  • Boom!. Thanks guys.

  • Edward Haskins

    Love the new feature! IDEA: using a Goal in order to jump to a different location as in the above example seems odd. Even though it’s a great work-around, a Goal should measure some sort of achievement: conversion, sale, appointment scheduled, application submitted, etc. Instead, why not create a similar automation step called “Jump”. The Contact when entered into the automation could jump to the location that meets the conditions defined. It would be great for the example above, as well as for all those feature requests of being able to insert a contact into various points within an Automation. Yes?

    • Brian Gladu

      Fair point, Ed. Thanks for the feedback.

    • I’d like to suggest another idea. Unless I am missing it somehow, this would be so useful if we could put the dates in Message Variables and then use those in the Condition Builder and Goals. That was save the creation of a lot of custom fields that have duplicate data for all contacts. Also allow you to create campaigns you can dump whole lists into and schedule emails before a webinar date, etc. :-)

  • Great work guys, love it!!

    Will we be able to set a future date (and store it as a custom field) as well (in an easier way then setting up webhooks to do the job)?

    • Brian Gladu

      Hi Wilco! Help me understand why using the “Update Contact” action to change the value of the custom field doesn’t work in your situation. I’m sure we can figure out a way to improve things, I just need to understand what you are doing and why. Feel free to email me: bgladu@activecampaign.com

  • YES! THIS is what I have been waiting for!! Thanks guys -

  • Lawrence Ladomery

    Awesome, thank you very much.

  • Cindy

    This is great. Can someone who is using it (or any date based automations) tell me how you would go about Annually occurring events? I don’t want an attendee from current year to get it again the next year if you know what I mean. This would rack up a lot of Date Based fields if we need to put one for every year, leaving a very long scroll down for that Contact Card.

    • We have something else in the works specifically for this. Stay tuned.

  • Karey Nickel

    Yep – definitely needed that – perfect!

  • Freerk Lap

    Perfect! I was annoyed by the previous elaborate need to give a month and day. Looking forward to more advances in it. Keep up the amazing work!

  • Hey @briangladu:disqus – I don’t think I put this in the right spot so reposting comment here on its own:

    I’d like to suggest another idea. Unless I am missing it somehow, this would be so useful if we could put the dates in Message Variables and then use those in the Condition Builder and Goals. That was save the creation of a lot of custom fields that have duplicate data for all contacts. Also allow you to create campaigns you can dump whole lists into and schedule emails before a webinar date, etc. :-)

    • Brian Gladu

      This is an interesting idea, Kim. Thanks for the feedback.

  • Josh Moore

    Using Goals to skip sections like that is very clever. Just last week I set up an automation for an upcoming event and had to write if else” clauses before each “wait” sequence to check if they were entering the sequence after that email should have been sent. It worked, but using a goal like you’ve demonstrated will be much more straight forward.

    • Brian Gladu

      Yes, the Goal action simplifies that type of automation in particular. Any time you find yourself using multiple “If / Else”s, there is probably a much more simple way to do it with Goals.

  • Josh Moore

    Question: In the example shown in this post, if we wanted the start of the sequence after they register to set a tag on the person, and set the Webinar Date value, how do we make sure that first part of the sequence still happens, even if they register less than a week out? If they were to register 5 days out from the webinar that goal would be achieve immediately, which means that they would skip that first part. That is good to skip over the “one week to go” email, but how should we structure it to still do the first part of the automation?

    • Brian Gladu

      Hi Josh! You could just repeat those actions under the Goal. If the tag and date are already set, the system will just skip over them and keep going.

      • Josh Moore

        I could see that approach getting quite messy – having to repeat a series of actions after each goal just in case it skipped to that part. And also, with the way my automation has been set up, the date field is actually set at the start of the automation. So all the “wait” fields and goals need that date. I guess what I’d need to do is have a first automation that sets these tags and settings and then it triggers a second separate automation which is just made up of the reminder emails. Then the goal structure would work well. Thanks for the ideas!

        • Brian Gladu

          Yes, if you’ve got a lot of jumps it definitely makes sense to split those actions out into its own automation. Good idea.

  • So in order to use these new features the custom field should be a date type field?

    I colect the seminar date as a custom hidden field… Is there any way I can turn my custom hidden field into a date field?

  • Would like to see a webinar on this. Very good feature but need more info on how to implement in different scenarios.

  • Pingback: Dynamically Marketing Your Live Events with ActiveCampaign | ActiveCampaign Email Marketing Blog()

  • Pingback: 7 Powerful Ways to Tune Up Your Marketing | ActiveCampaign Email Marketing Blog()