New Workflow Features You Won’t Be Able to Live Without

Matt Davis, Senior Product Manager

Author Bio

Matt Davis is responsible for delivering solutions at the heart of the Bronto Marketing Platform, including workflows and automation, reporting, analytics and API, to help retailers maximize the impact of their marketing campaigns. He has over a decade of experience in product management and marketing in the software-as-a-service (SaaS) space. Prior to Bronto, Davis served as product manager at Deutsche Bank Global Technology and iContact. In 2006, he helped start Futures, Inc., a forward-looking SaaS startup in southern California, where he played a crucial role in the development and launch of the cloud-based Pipeline platform, focused on candidate and employer matching, career marketing and professional networking. Prior to Futures, he worked in marketing and sales for Apple, Inc.

For many of our customers, Workflow Automation (or Workflows) is the well-oiled machine that powers their automated marketing campaigns. Over the last couple of months, we’ve released a handful of extremely useful features within Workflows, keeping Bronto at the forefront of the commerce marketing automation space. Let’s take a look at what’s new:

  1. RFM Fields in Trigger + Filter Nodes
  2. Node Labels
  3. Cart Phase Filter Node
  4. Date Filtering in Workflow Reports

1. RFM Fields in Trigger + Filter Nodes

New RFM FieldsWe’ve received a lot of requests for more contact field options in trigger and filter nodes to better align with those found in Segments. We listened. A full complement of RFM fields can now be found in the Contact Field Updated trigger and the Contact Field Comparison filter node. These include: Average Order Value (AOV), First Order Date, Last Order Date, Last Order Total, Total Orders, and Total Revenue.

Segment Membership triggers and filters aren’t really “new” anymore, but with the same fields now available directly from Contact Field trigger and filter nodes, there’s less of a need to create a segment for the sole purpose of triggering and/or filtering workflows. For example, let’s say you want to automatically send a specific message or offer to contacts who have spent a certain dollar amount. Previously, you’d have to create a segment to have a dynamically-updating group of contacts from which to trigger a workflow. Now, all you need to do is add a Contact Field Update trigger, choose Total Revenue as your field and specify your conditions.

Contact Field Comparison filter nodeUnless you want to track a group of contacts for future sending or promotional purposes, there’s not much incentive to take the extra step to create a segment, which is a nice time-saver. This same logic also applies to the Contact Field Comparison filter node.

PLEASE NOTE: For customers on New Order Service (NewOS), RFM field data will update in near real-time, so contacts will enter or filter through your workflow much faster. If you’re not on NewOS yet, don’t sweat it. The fields will update every 12 hours, which mirrors the same behavior of segments containing RFM metric criteria.

2. Node Labels

If you have a double-digit node count for any of your workflows, you have a lot to keep up with and it can be difficult to see which node does what at a glance. With Node Labels, that’s no longer the case. You can now change the name of any node in your workflow by simply clicking the edit icon next to the node title and entering your preferred content.

Node Label ExampleThis feature is especially helpful if your workflow includes  multiple Send Email nodes or uses triggers or filters based on data that may not be fully reflected in the regular node view. The image below provides an example of how Node Labels can make a workflow much easier to comprehend while viewing it in the Workflow Builder. You can also edit the label as many times as you want to make sure it’s accurate if the node content changes.

Workflow Example Using Node Labels

3. Cart Phase Filter Node

Cart Recovery users now have access to a handy new node which allows contact filtering based on a specific Cart Phase. If you use the app, you can find this node in the Filters section of the Workflow Builder directly under the Cart Status node.

Cart Phase Filter Node Example
When added to your workflows, the node lets you easily filter contacts based on a specific cart abandonment phase, including Shopping, Billing, Order Complete, Order Review, Payment, Shipping Info and Shipping Method.

This single node makes Cart Recovery so much more powerful because it allows you to send targeted content to contacts that abandon at each of these phases and reach them faster. For example, you may have typically waited 2 days and sent a more generic cart abandonment email, but now, you could target contacts who drop out in the Billing phase and send a follow-up email focused on billing info within 30 minutes. You could then automatically move these potential customers to the list of your choice for future contact. And that’s just one use case.

Workflow Example Using Cart Phase Nodes

REMINDER: This node is only available if you have purchased Cart Recovery. If you haven’t, what are you waiting for? It pays for itself in no time! The ROI our customers are seeing has been off the charts, and this new node will push it even higher. Contact your Account Manager today to learn more.

4. Date Filtering in Workflow Reports

Last but not least, we have extended Date Filtering into Workflow Reports. As with a Message, Delivery or Delivery Group report, you can easily filter your stats by date range. The dropdown menu functions the same way, so the date filtering experience across all core reports is consistent.

These are just a handful of the new features in Workflows. We have many more exciting things planned for the rest of the year. Stay tuned!


XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">