The name of the module where you can create automated journeys. Sometimes it’s used as an adjective to describe the type of journeys you can create in the module.
In the running, paused, and stopped journey, above the canvas, a user can enter the Analytics section. After double-clicking the node, a statistics panel appears on the right side of the screen.
The type of the journey that involves data integration with external sources. Such a journey can be triggered by receiving data requests from external tools (for example, an ecommerce platform) and the data from Synerise can be sent to external tools in response to circumstances specified in the journey. To build such a journey, users can use only business-oriented nodes and it doesn’t require customer data.
The area on the interface where you create a diagram.
The type of the journey that uses customer data and reacts to the customer behavior in a defined way.
The structure of the journey (nodes and paths).
The counter you can find in the analysis of a journey. It shows the number of times customers entered and left a node.
The counter you can find in the analysis of a journey. It shows the number of times customers arrived at a node.
While defining the settings of a node, a user has the possibility of using data (event parameters) received in the preceding node in a diagram. This provides a possibility of inserting dynamic values, for example in the input or request in a webhook.
Read more about event context here.
In the journey that has the following structure:
Transaction (trigger) > Send email (action) > End
The template of the email in the Send email action contains a dynamic value taken from the parameters of the
transaction.charge event that defines the total cost of the purchase:
Thank you for your purchase. The total value of your cart is:
The number of times customers arrived at the final step of the journey (the End node). The number is not equal to the number of unique customers who finished the journey - one customer can participate in the journey many times (if the customer meets the conditions of the trigger that starts the journey).
The global scope is available in the Analytics section of a journey. It shows the ratio of the number of paths that met the requirements necessary for action performance to the number of all paths launched in the journey.
It allows you to receive data from external sources which triggers a journey. It requires creating an incoming webhook.
This piece of information is displayed on the list of journeys. It informs about the number of times a journey is launched (and still in progress).
A sequence of nodes that together describe a scenario and define the course of actions to be performed in defined circumstances. This term refers to the concept of an automated process - a customer entering and completing this process. The structure of the journey is referred to in the documentation as a diagram.
The limit users use to define the allowed number of repetitions of the entire journey. It also concerns the limits within the nodes. You can find more information about capping here.
There are three types of statuses:
- Draft - It is a journey that has been saved but it hasn’t been activated yet.
- Running - It’s an activated journey.
- Paused - It’s a journey that is stopped temporarily.
- Stopped - It’s a journey that is stopped permanently.
Each status allows certain scope of actions. The scope of actions:
*The editing option allows changing the settings in the nodes only. You won’t be able to add new nodes to the diagram.
Node Context menu
The menu that appears after a right click on the node.
It allows you to send data to external sources but also use Synerise open API. This requires creating an outgoing webhook.
A user starts a path every time they meet the requirements of the trigger of a journey. The path reflects the progress of a customer in a journey.
The duration of the state between arriving at the step and execution of the activity set in the node logic (it’s connected with the Delay node). This piece of information is available in the Analytics section in the journey.
This piece of information is available in the Analytics section in the journey. Time it took a path to reach a step from the starting point (trigger).
It’s the structure of data a user must select or create while preparing an outgoing webhook.