Every online business is different. Trigger email messages when customers of a certain group checkout, transactions occur in a geographic location or when orders go from one order status to another. Create workflow rules that cater to your store’s processes and be more efficient.
Use for custom backorder notifications, internal messages and more
Focus on specific customer groups, order statuses, and/or purchase amounts
Add any combination of values and filters to initiate a message
Login to your account
Click the Add New in the bottom left corner
Select ‘Add Workflow’
Choose ‘Custom Workflow’
In step 1, toggle desired settings
In step 2, add your conditional logic by constructing any combination of API mappings
In step 3, add the name, email and subject customers will see when the message arrives
Select a starter template to use, or add content using the WYSIWYG editor
In step 4, confirm settings and activate
The overview dashboard will show all-time historical stats for the workflow, no matter if rules have been deleted.
Messages pending – count for pending e-mails that are scheduled to be sent
Messages sent – count for sent messages
Opens – number of times messages have been opened
Clicks – number of times messages have been clicked
Conversions – number of conversions resulting from this type of workflow
Revenue – total sales attributed to this type of workflow
Activity chart – weekly view of sent messages
The logs area of this workflow will display log events between specific date ranges.
Pending – shows messages that validated based on rule criteria and are scheduled to be sent.
Sent – shows information about messages that have been sent as a result of meeting rule criteria.
Conversions – displays relevant conversions as a result of a workflow message triggering.
Blocked - listing of email addresses that did not qualify for defined rule criteria.
And/Or – structures the conditional logic for the rule
API Mappings – available meta for a shopping cart’s API
Conditions – is, is not, greater than, less than, contains, does not contain, begins with, ends with
Conditional Value – text, date or integer
Use one asterisk * to trigger any qualifying value
Construct as many conditional logic rows as necessary
We have several advanced meta-logic variables that can be used in custom workflows for situations where standard platform meta needs an additional layer of control.
Order Status Was – the previously saved order status used in conjunction with the current one
Customer Has Spent – historical purchase amounts
Customer Order Count – historical number of orders
All shopping carts are supported by this messaging workflow.