Workflow types
With version 1.24.0 "Workflow type" has been introduced to Connectif.
Connectif calculates the type of workflow according to setup and nodes. Said type influences the behavior of the workflow by allowing to optimize the inner workings and performance.
The types of workflows are:
- Reactive
- Rule
- Bulk Action
- Classic
Reactive
The reactive workflows are the ones that are made according to the following characteristics:
- All the nodes connected to the "Start" node have to be of the trigger type.
Example:
Advantages
The main advantage of this type of workflow is that it makes the process start right away. The "Start" node won't require to load all the contacts. Instead, the process will happen as the events get triggered.
In the past, these type of workflows needed a lot time to start because they had to process all the contacts. It was not necessary, since the contacts that trigger the next event were a small part. Also, the triggers didn't work for contacts that weren't entirely processed by the system yet, so the delay affected the whole workflow. With this new feature, the triggers will activate immediately.
Restrictions
These workflows don't let you select the following options from the "Start" node:
- "From segment"
- "All existing"
Rule
The rule workflows are the ones that are made according to the following characteristics:
- All the nodes connected to "Start" have to be triggers.
- Trigger nodes need to follow after "Start".
- Nodes can't have contact limitations (they can have general limitations).
- Nodes can't have limitations to other nodes.
- Nodes "Wait", "Schedule" or the ones involving A/B/X Tests can't be included.
Example:
Advantages
- Same as previously discussed in reactive workflows.
- Since you don't have contact limitations, you can maximize your optimization when it comes to showing web content in your site. This is important because it affects the overall final user experience.
Restrictions
- Same as in the reactive workflows.
Bulk Action
The bulk action workflows are the ones that are made according to the following characteristics:
- Audience from the "Start" node is "All existing".
- Doesn't include any trigger nodes.
- Nodes "Wait", "Schedule" or the ones involving A/B/X Tests can't be included.
Example:
Advantages
- Improves the speed of the process in regards to a classic workflow.
Classic
Any type of workflow that is not reactive, rule or bulk action type.
How do I check the type of workflow?
Once the workflow has started, you can see the type in the "Live View" option by clicking the info icon on the "Start" node.
Reactive
Rule
Bulk action
Classic
Doesn't have an info icon.
Triggers
Triggers are the type of nodes that wait for contact events to happen (on page visits, on purchases, on clicks, etc.).
With version 1.24.0, trigger nodes always check the workflow audience before starting to process the events.
In the past, workflows like "for this segment -> on page visit -> show banner", calculated all the contacts from the segment at the beginning, and then the triggers followed. If a contact ever came out of the segment, the trigger was still active for that particular contact. So, as a result, they still saw the banner when they visited a page, even though they weren't on the segment anymore. Same happened even with anonymous contacts. With the newer version, the triggers will always check the audience, so in the previous case, the banner won't be shown, since the system will recognize that the contact is no longer there. This change of behavior makes the nodes more intuitive, and it's all thanks to the feedback from our clients.
Dynamic filter in the workflow
With version 1.18.0 we have introduced the possibility to filter products using dynamic variables.
Where can I find it?
This feature is available in condition type nodes of the ecommerce integration, as well as in the node "Get products", which has greatly improved thanks to the feature.
What can I do with this feature?
Thanks to the dynamic filter you can improve the personalization of the products recommended in cases of use such as the following:
If we want to recommend products in a banner from the same category as the product's page that they are seeing, you could do it like this:
As you can see, the "Imported Data" option appears in the filter options. Here, we can choose the information from the contact or any other node that has added information to imported data.
Another case of use can be to show a different content if the contact has purchased the product they're visiting. To follow that up, the next workflow will show a popup if the contact has purchased the product or a different product if they haven't.
The structure of the workflow and the settings for the node "Has purchased" will be as follows:
