Condition Nodes

The condition type nodes are used to filter the contacts so you can segment them more precisely within the actions o the workflow. We can decide which steps the contacts will take, wether they fullfill the conditions or not. 



Within the condition type nodes, we can see 6 different categories:




Check workflow value

This is one of the most useful and versatile nodes among all of them. It allows us yo check values of a particular field. It could be system or custom fields. The type of field (boolean, text, integer, etc) is also important when it comes to checking the values.

For example, if we want to do a promo campaign, we might want to check if out contacts are subscribed to the email newsletter or not. That way, we can decide which is the most effective method to impact our contact's base.



For an example, we'll go to the configuration of the node and, from the left column, we'll drag the field "newsletter subscription status" to the center. Since this is a radio type field, you can only check if it's selected or not. For that, we'll drag the "literal" field from the right column. It will allow us to choose if the contact is subscribed, so we'll just set it up like in the following image:






Check attribute

It works similarly to the previous node, but it can only be applied to contact fields, both system and custom.

In this example, we'll use the node to ask if the contact has the field "mobile phone status" as active. Depending on the answer, the contact will be impacted differently: if they have the mobile active, we'll send him a SMS; if they don't, we'll use a web content. 



For this action to be effective, we will do as in the previous node, but this time, using the field "mobile phone status". We'll do something similar with "literal" field. It should look like in the next image: 



Is in segment

It's used to ask contacts within the workflow if they belong to a certain segment that you can choose from the configuration screen. In this example, we'll ask if the contact belongs to a segment. If they do, we'll remove them, and if they don't we'll send them a web content.



Configuration screen is simple, since you only have to select the segment that you want to involve in the workflow:



Remember that you can also choose a segment in the "Start" node, so if you choose one there, don't select it in the "is in segment" node, since it would be redundant. 




Has received email

It asks if the contact has received one or more emails sent via Connectif. It has several configuration options that could make a huge difference depending on the strategy behind the workflow. If we leave the default settings (any email, email type and date), all the contacts that have received an email since they are part of the platform will go through. To prevent this and create more specific strategies, you can select a particular email, or the number of emails that the contacts need to have received to continue. We can even choose a time interval or fixed date. It all depends on the strategy.

We'll use this example in which, if the contact has received a specific email regarding their abandoned cart, the system will get that last cart and send a discount email. On the contrary, if they haven't received the abandoned cart email, we'll program a 15 day wait and then we'll ask again:



The node "has received email" is set up this way to follow our own example:



Has opened email

Similar to the previous node, but this time the action needed is actually opening an email. We'll use an example in which, if the contact has opened a specific email, they will be added to a segment. If not, the email will be send again.



Same configuration options as the previous node too. In this case, we'll select a specific email and a time interval of 15 days. This way, the contact only needs to have opened the email once in the last 15 days to advance.



Has clicked link

Also similar to other nodes in this category. It checks if the contact has clicked a link within an email. In this example, we'll ask if the contact has clicked the unsubscribe link on the footer of the email in the last 5 days.



In the settings, we'll select the particular email and link that we are interested in for this strategy. If you don't select an email and leave the default option on, you can only choose one the option "any link". As usual with this category, we can select time interval and dates. If we don't, the system will search all the contact's history of clicking in emails.






Has received SMS

Works similarly to the "has received email" node. With this example, we'll ask the contact if they have ever received a SMS message. If they have, we'll add them to a segment. If they haven't, we'll send them a web content that contains a form, so they can provide their phone number. 



The node has the same setting options as the email equivalent. You can select an specific SMS or any, as well as the number of times that it has been received. Also, you can choose the type of SMS, transactional or newsletter, and the date or time interval in which it has been received.






Has visited page

It asks if the contact as visited a particular URL of our site. If the settings are left in the default state, the node will register every visit to the URL that a contact has done in their whole history. If you don't want that to happen, there are several ways to change the settings. For one, you can select the amount of times that an URL has to be visited for the node to activate. You can also select a specific URL or just how it begins, as well as the date or interval in which the event has to take place. The goal of all of these options is to make your strategy more efficient. We'll now go to a case of use in which we'll add the contacts to a segment if they have visited the URL. If they haven't, they will receive a web content that links that specific page. 



After that, we can add more conditions. In this case, we'll use two, one related to the tags and the other to the categories. If you use this type of conditions, which are optional, a contact needs to fulfill all of them to go through. So, if the contact has visited a page that has the specified category but not the specified tag, they won't continue, since both need to be true.



Has viewed message (deprecated)

It's used to ask about the opening of messages that appear on the page, similar to popups. We'll use the following case of use: if the contact has opened any message, they'll get a web content with some sort of promotion. If that's not the case, they will be added to the segment of contacts that have never opened a message. 



Similarly to other nodes, you can set if it's a specific message or not, the number of times it's been opened and the date or intervals. We'll use the default in this case, since it will be more effective for our strategy.



Has submitted form

It's relevant to remind everyone about the distinction between trigger and condition type nodes. If put this node after an event that includes a form, it won't work. That's because the node asks the question immediately after the previous node is executed, so the contact doesn't have time to fill the form. There are two alternatives to make it work, you either use a "on form submitted" node or "wait" and set up a "has submitted form" that coincides with the interval in the "wait" node. That way, the contact will have time to submit the form. Here's an example of the second case:



It's similar to the setting options of the other nodes in the section. It allows you to send a specific form and how many times is sent and the date filter. Here, we'll select a popup as the source of the form for the specific option and we'll use an interval of 1 hour that matches the "wait" node:



Has opened notification

It's used for contacts already subscribed to push notifications if you want to know which ones were opened. An equivalent in other node category would be "has opened email". In this example, we'll select contacts that are subscribed to notifications from the start, in order to make it more efficient.



Same setting options than in the previous node. In this case, we'll ask if the contact has opened one specific push at least once between two set dates. If the contact meets the conditions, they'll get a different push; if not, they'll be added to a concrete segment:



Has clicked notification

It's used to check if a contact has clicked any of the links that a push contains. For this example, we'll use a similar case that of the previous node, but reverting the possibilities according to the contact's action.



The setting options are the same as always, including the chance to choose a specific push. In this case, we won't specify, since we just want to know if the contact has clicked two push notifications in the last 10 days. If that's the case, we'll add them to a segment. If they don't, they'll be sent another push.






Has purchased

It asks about the purchases that a contact has made up to that point. Like in other similar nodes, you can set it up to ask the number of purchases or the dates. In this case, we'll use a workflow with the following structure:



The main new feature in the settings department in regards to other categories of nodes is the option to add conditions to filter data, like the total price of the purchase. You can add all the conditions you want, but remember that the contacts need to fulfill them all to continue. So don't make the conditions mutually exclusive. There are two subcategories of conditions: the ones related to products (brand, category), and the ones related to the purchase (total price, total quantity, payment method).

For our example, we want the contact to have purchased at least 3 times in a 30 day interval. Also, we'll add a condition so that the total price has to be more than 150€ between all three purchases.



Has visited product

It's used to impact the contact with different actions if they have visited a particular product on our site or not. In this example, if the contact, that needs to have a registered email, meets the conditions that we'll explain later, they will be added to a segment. If not, they will receive an email highlighting products from a certain category.



Like in previous nodes, we can choose the amount of times that the products have been visited, as well as the dates or intervals. After that, we can add conditions related to the products. We can choose specific products or categories that the contact has visited. In the case of this example, we'll only let pass the contacts that have visited at least 5 products of the same category in the last 3 days.



Has searched product

It's applied to searches of products on the website. In this example, we'll take contacts that have their emails registered. We'll ask if the have searched for products that get'll get to in the settings page. If they have, they'll be added to an "interested in" segment. If they don't, they'll get an email highlighting the products in question.



Has the same setting options as the previous node, conditions included. For this example, we'll set a condition that involves the contact searching for "sport shoes" at least 5 times in a spam of a week. That way, we can see the level of interest in that category, and if they do it, they'll be added to the segment.



Has abandoned cart

Registers contact activity in search of abandoned carts that meet the settings configuration. In this example, we'll start with contacts that already have an email registered. If the contact has abandoned  a cart according to the settings conditions, the system will get the last cart and send a reminder via email. If they don't, the system we'll get the best selling or more visited products and will send an email with them.



Setting-wise, we have two subcategories in the "add condition" option, but this time we don't have anything related to purchase, such as payment method, since it's not relevant for this node. In this example, we'll make it so contacts can continue when they have at least one abandoned cart in the previous 5 days and the subtotal among the carts is less than 10€.


Was this article helpful?
0 out of 0 found this helpful