New to the Automation Manager is the ability to append a calendar date to an automated condition, or in other words, ONLY match targets to a workflow that meet the criteria BEFORE or AFTER a date you configure for the automation.
With the update of adding a date, users now have an extra operator to determine when in the calendar year a record may be matched into the workflow. Before this update, records could be retro-actively added to a workflow, say, if they visited a specific page of your domain. It didn't matter if they visited the page yesterday, 3 months, 6 months down the road - if they met the criteria for particular conditions, they went through the workflow.
Now, by defining a date (Before/After) records will be matched with a combination of the date defined and the condition/s defined.
There are several conditions where the date picker is not applied. These conditions are:
For the remainder of the conditions, there are 3 different types of date pickers. They are:
Activity date - This means that the record must complete the activity before or after the date selected
Date Modified - This is only for the Data-field condition. For SugarCRM and INBOX25 marketing lists, there is a date/timestamp for each change made to a data-field. The date picker will look at this date/timestamp to (Before/After) reflect if a record should match into the workflow.
Date Created - This operator is specific to SugarCRM activities/objects (i.e Calls, Opportunities, Meetings, etc.). The date picker will go off of when the activity was created in the CRM.
Here is a list of the conditions where a date picker can be defined, and what the operator for each condition is:
Landing Page-->Date [Before/After activity date]
Web Activity--> Date [Before/After activity date]
Data Field--> Date [Before/After date modified]
Campaigns--> Date [Before/After activity date]
Opportunities--> Date [Before/After date created]
Calls--> Date [Before/After date created]
Meetings--> Date [Before/After date created]
Support Cases--> Date [Before/after date created]
Quotes--> Date [Before/after date created]
Contracts--> Date [Before/after date created]
Target Lists--> Date [Before/after date created]
Let's take the example of a Data-field condition. Any change made to a data-field to the CRM that INBOX25 is synced with will have a date/time stamp associated to it. Setting the date picker parameter to any date modified change made before the date selected to the Assigned to field - for example - will bring in any records were a change has been recorded in the CRM.
Let's use this same logic for conditions where the Date picker operator is 'activity-date'. Whereas the date modified pertains to changes made in the CRM, activity date is associated with events and touch points INBOX25 is tracking locally. For example, if the activity date is after Jan 1st 2015 (01/01/2015) and you're using the Web-Activity condition (i.e Specific page on site viewed), any record who visits your site whom INBOX25 has identified as a Known Visitor will be brought into the workflow.
Lastly the date created date picker. Much like the date modified example, the only difference is the system isn't looking for any changes, but simply when the object (CRM Call, Meeting, Opportunity etc.) was created. You can find this inside the CRM by looking at the specific object.
Send an automated email with an offer to prospects who visit a splash page (Web-Activity-->Specific Page Viewed) only within a specific timeframe by combining the same condition using the Date Picker.
Only route leads to a Sales agent who have converted on a contact us from (Landing Page-->Successful Conversion) in the last 30 days.
If a lead clicked through your email after the cut-off date to take action, send them a followup email apologizing they missed the cut-off date. Push them to a page on your site with a form to enroll for future alerts/events.