Este artigo está atualmente disponível em inglês e espanhol. Você pode usar esta documentação enquanto ela não estiver disponível em seu idioma.
Trigger nodes serve to reactivate the flow when a contact performs an activity on your page or meets a certain condition.
How do the different trigger nodes work?
By default, trigger nodes fall into six categories, depending on the area where they are executed.:
1. Contact
Nodes in the Contact category are triggered based on the contact's activity or information
1.1. “On searching” node
This node is used to react when a contact carries out a search on the website. In the node interface, you can configure the keywords that will trigger the node, with exact or partial coincidence.
In the example, the node will trigger when a contact searches for the exact terms “table” or “tables”.
1.2. “On entering segment” node
This node is used to react when a contact is added to a static segment. In the node interface, you can set the segment to which the contacts must be added for it to be triggered.
In the example, the node will trigger when a contact enters the “Segment example” segment.
1.3. “On leaving segment” node
This node is used to react when a contact is removed from a static segment. In the node interface, you can establish the segment from which contacts must be excluded for it to be triggered.
In the example, the node will trigger when a contact leaves the “Segment Example” segment.
2. Email
The nodes in the Email category are triggered based on the activity of the contact with the email.
2.1. “On opening email” node
This node is used to react when a contact opens an email sent via Connectif. In the node interface, you can establish the email that contacts must open in order to trigger it, which can be any email or a specific one.
In the example, the node will trigger when a contact opens a specific email called “Newsletter”.
2.2. “On clicking” node
This node is used to react when a contact clicks on an email sent via Connectif. In the node interface, you can configure the link that contacts must click to trigger it, which can be a click on any email or a specific one.
In the example, the node will trigger when a contact clicks on any link in the “Newsletter” email.
2.3. “On unsubscribing” node
This node is used to react when a contact unsubscribes from the newsletter, via the default link that can be added when editing the content of an email. In the node interface, you can establish if it will be activated with an unsubscribe in any email or in a specific one.
In the example, the node will trigger when a contact unsubscribes from the “Newsletter” email.
3. Website
The nodes in the Website category are triggered based on the activity performed on website content.
3.1. “On visiting page” node
This node is used to react when a contact visits a web page. In the node interface, you can configure the pages and devices that will activate the node, as well as those that are excluded.
In the example, the node will trigger when a contact visits any page on the website, without exclusions, from any device.
3.2. “On opening web content” node
This node is used to react when a contact opens any website content that has been sent to them. In the node interface, you can establish if it will be triggered by a specific piece of content or by any content of a certain type.
Inline web content is excluded from the configurations of this node, as it is located within the page code and is not considered emerging content.
In the example, the node will trigger when a contact opens the “Popup push” web content.
3.3. The "On clicking web content" node
This node is used to react when a contact clicks on a link in website content. In the node interface, you can establish whether it will be triggered with any click on any content, on a specific content link or a link that is not within a piece of web content.
Learn how the “On clicking web content” node works in this article.
3.4. “On submitting form” node
This node is used to react when a contact confirms the submission of a completed form. In the node interface, you can configure if it will be triggered when any form is sent, or a specific one. In addition, it is possible to filter by the URL where the form is located.
In the example, the node will trigger when a contact submits the “Newsletter” form on any page.
3.5. “On opening push” node
This node is used to react when a contact opens a web push notification. In the node interface, you can establish if it will be triggered when any notification or a specific one is opened.
In the example, the node will trigger when a contact opens any push notification.
3.6. “On clicking push” node
This node is used to react when a contact clicks on a link in a web push notification. In the node interface, you can configure whether it will be triggered with a click on any link in the notification, or on a specific one if there is more than one link.
In the example, the node will trigger when a contact clicks on any link in the “Push example” notification.
3.7. “On subscribing to push” node
This node is used to react when a contact subscribes to push notifications. The node interface has no configuration.
The example shows the interface of the “On subscribing to push” node.
3.8. “On canceling push” node
This node is used to react when a contact blocks the subscription to push notifications. The node interface has no configuration.
The example shows the interface of the “On canceling push” node.
4. Ecommerce
The nodes in the Ecommerce category are triggered based on the activity carried out in the ecommerce site.
4.1. “On purchase” node
This node is used to react when a contact makes a purchase. In the node interface, you can configure the specific features of the purchases that will trigger it.
In the example, the node will trigger when a contact makes a purchase that includes a single product whose value is equal to or greater than 100.
A series of characteristics of the filter options must be taken into account:
- "Is equal to" means that, to pass the node filter, the purchased product must meet one or more specific requirements.
- "Is included in" means that, to pass the node filter, the purchased product must meet any of the specified requirements.
- When filtering by Products in the purchase, at the top of the filter configuration, you can indicate whether a person who meets all the filters or just one/some will proceed to the next node, as shown in the following example:
4.2. “On visiting product" node
This node is used to react when a contact visits a product page. In the node interface, you can configure the specific features of the products that will trigger it.
In the example, the node will trigger when a contact visits a product page whose value is equal to or greater than 100 and that is in stock.
4.3. “On searching for a product” node
This node is used to react when a contact searches for a product. In the node interface, you can configure the specific features of the products that will trigger it.
In the example, the node will trigger when, as a result of a search, a contact visits a product page whose value is equal to or greater than 100, that is in stock and of which there are fewer than 25 units left.
4.4. “On abandoning cart” node
This node is used to react when a contact abandons a cart. In the node interface, you can configure the characteristics of the carts that will trigger it, if you want to specify these.
In the example, the node will trigger when the abandoned cart has a value greater than 100.
4.5. “On adding to cart” node
This node is used to react when a contact adds one or more products to the cart. In the node interface, you can configure the characteristics of the added products that will trigger it, if you want to specify these.
In the example, the node will trigger if there are fewer than 50 units left in stock at the time a product is added to the cart.
5. Facebook
The nodes in the Facebook category are triggered based on activity carried out in Facebook and Instagram.
These nodes will only work on accounts that have Facebook integrated. This article explains how to perform the integration.
5.1. “On visiting from Facebook” node
This node is used to react when a contact visits the website via a link or post on Facebook. In the node interface, you can configure whether it will trigger with any visit, visits from certain campaigns, visits from certain ads or from a mobile device.
In the example, the node will be triggered with any visit from Facebook.
5.2. “On visiting from Instagram” node
This node is used to react when a contact visits the website via a link or post on Instagram. In the node interface, you can configure whether it will trigger with any visit, visits from certain campaigns, visits from certain ads or from a mobile device.
In the example, the node will trigger on any visit from Instagram.
Congratulations!
You’ve reached the end of the tutorial.
Do you have questions?
Don’t forget, our Connectif specialists are here to help you. To contact them, just open a Support ticket by clicking the blue “Help” button on your dashboard.
Keep learning!
To make the most of your Connectif account, we recommend reading these articles next:
- Condition-type nodes, to filter the requirements the contacts must meet to continue through the flow.
- Action-type nodes, to execute specific operations within flows.
- Node limitations, to configure the conditions under which the nodes will not be triggered.
- Directory of workflow templates, to locate the templates available to use in your strategies.