Custom
Tap into API mappings for the shopping carts we support and create any type of "if this, then do that" messaging solution for your store.
Why you should use it
Craft any custom messaging rules you need to connect with your customers or staff to streamline tedious processes.
If this, then do that...
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
How to get started
Login to your account
Click the Add New in the bottom left corner
Select ‘Add Workflow’
Select ‘Marketing’
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
Settings
Workflow name – the “friendly name” for your workflow, customers will not see this
Sending Filter - send to all customers, only to subscribers or send only to a specific email address
Send - send immediately or specify a time in the future to send the message.
Advanced
Order Count Is - Trigger a message if a customer has an order count according to the selected count.
Limit Products Visible - By default, all products that were purchased are shown in the email message; if you would like to set a maximum number of products to be displayed, enable this option.
Price Trigger - When enabled, trigger messages based on if an order is greater than or less than a specific price level.
Product Filter - If you require certain products to be in a cart before a rule is triggered, add the product codes in the text area. If you have a product filter set and a general abandoned cart rule configured, the most specific rule will fire when there is a match.
Blacklist - Enter individual email(s) or domains that you would like to prevent this workflow rule from sending to. For domain blocks, use asterisks before the domain name e.g.
**@domain.com.Usage Limits - When activated, this setting will limit the number of emails that are sent to a customer email address. This feature does not impact other messaging workflows of its type and is only specific to the rule being created.
Dashboard overview
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
Logs
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.
Conditional logic
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
Advanced custom meta
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
More information
Compatibility
All shopping carts are supported by this messaging workflow.
Last updated