Custom
Workflow Documentation
Last updated on April 12, 2017
Details
Tap into API mappings for the shopping carts we support and create any type of “if this, then do that” messaging scenario for your store.
Setup
- Login to your Vextras 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
Overview Dashboard
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
Rules
- Workflow name – the “friendly name” for your workflow, customers will not see this
- Sending filters
- Send all – send to every customer, including anonymous users
- Send if newsletter subscriber is checked or send only to registered accounts – send messages to customers who specifically opt-in
- Send only to – this filter only sends to email addresses that are defined in the rule
- Send after – time delay before a message is sent
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
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 with this workflow.