With any new tool, there’s a slight learning curve. Included in the automated flow collection are a bunch of articles designed to help you learn and get the most out of active flows. This article is here in case you encounter any issues or simply want to gain a better understanding of automated flows.

Using an Automated Flow is much more flexible. Now, you can set it and forget it. It also allows you to set up multiple contact methods at different stages of the customer’s life. For instance, you can send a text when they sign up, an email when they place their first order, and a promotional text when they haven’t placed an order in a while. This gives you much more flexibility and creative potential in marketing, while letting CleanCloud do the heavy lifting.

CleanCloud’s Automated Flows use AND logic, this means that all conditions must be met to follow the YES path.

If using stacked conditions such as Customer Order Count = 3 & Average Order Value > 100, both of these conditions much be met for the customer to continue through the Yes path of the Automated Flow.

Automated Flows, a powerful Advanced Marketing feature, are seamlessly integrated into CleanCloud. They utilize your existing marketing consent data without the need for manual export. These flows are exclusively available to Grow and Grow+ customers.

Currently, when we deactivate an active Automated Flow, it automatically terminates any customers within the flow. We’re monitoring this behavior to identify potential optimizations for future improvements.

When using a condition 2 path, two child nodes are created. The child with more descendants is always placed on the left. This can reduce edge crossings and generally improve the readability of the graph. Placing the heavier child node (the one with more descendants) on the left may make the graph appear more compact and symmetrical in certain configurations.

As mentioned above multiple conditions will follow AND logic as explained above this means all conditions must be met to follow the yes path. This should be kept in mind while creating all Automated Flows.

Source Store is a condition within Automated Flows that applies to Multi-Store customers. It allows you to set conditions for specific stores. For instance, if you have a campaign in Store A and set a condition for Source Store A, creating a customer in Store B shouldn’t trigger the condition. However, if you create a customer in Store A, it should trigger the YES node.

If you have Source Store B and A, the condition should trigger the YES Node if you create a customer in either Store A or B.