Limits

Users can use different type of limits to define the allowed number of repetitions of single nodes or the entire journey.

To ensure the clarity of this document, familiarize with the following terms:

  • Journey - A whole process that is built with nodes connected in a specific order.
  • Path - A progression from the starting point to other steps in a journey. Each time a customer performs an action that triggers a journey when the journey is already triggered, the system records it as a path of a particular journey. If a customer finishes one path within a journey (which means, they go from the initial to the final node in the journey), the journey can be restarted if triggered.

Automation capping


How it works

This limit allows a user to define the number of times a journey can be started in a specific time unit. The calculation context is the entity (such as a customer) that triggers the journey, not global.

Example of use

Filled automation capping settings
Filled automation capping settings

In this example, a journey can be triggered up to 3 times in an hour. When this limit is exceeded, a new journey won't be started.

Trigger limits


How it works

This type of limit can be found in the settings of most triggers. It defines the number of paths that can be started within one journey. The default limit is set at 1 path.

This limit is particularly useful when a user wants to use a frequently occurring event as the trigger (for example, a visit to a main page of an online shop).

Example of use

Filled automation capping settings
Filled trigger limit settings of the Client Event trigger

The trigger limit is set at 1 per journey. This means that a customer who began a journey, and a path at the same time, cannot begin another path until a journey is finished.

Flow control limits


How it works

This type of limit allows users to narrow down the passages to next steps in the journey (it resembles the mechanism of a funnel).

Example of use

Merge Paths example
Merge Paths node example

In this example, the automation is triggered either by a purchase of bottle of soda or a pack of crisps. Later, customers proceed to the client filter to check whether they visited a particular URL in the specific time. If they did, a mobile push is sent to those customers.

The Merge Paths node in this example fills two functions here:

  1. It joins two separate paths.
  2. It defines how many times a customer can go through this node in a specific time unit or in a journey.
    Filled Merge Paths node settings
    Filled Merge Paths node settings

Action limits


How it works

This type of limit allows a user to define how many times an action defined in the action node logic can be repeated when customers follow the same path in one journey.

Example of use

If the settings of a journey facilitate a launch of many paths, you can, for example, limit the execution of actions in the journey to avoid sending too many messages to your customers. You can use two types of limits available in the action node settings:

  • Journey limits
  • Time limits

Journey limits

Limits of action performance per journey
Limits of action performance per journey

If the action limit is set at 1 per journey, it means that customers get only one email, even if they go through this node in the same journey several times. Another message can be sent when customers finish the journey and start it once again.

Time limits

Limits of action performance for a specific time unit
Limits of action performance for a specific time unit

The 1 time per 1 hour configuration ensures users that customers who go through this node many times in one journey get one email (only if next paths start at the same time as the first email was sent). However, when customers arrive at this node again in one journey after 60 minutes since sending the first email, another email is sent.

It's important to understand that time limits work within one journey. In other words, consecutive journeys don't process time limits of preceding journeys, even if the time of launching consecutive journey coincides with the action time limit of the preceding journey.

😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.