Exits

On the Exits tab, you can split your interactions into different routes.

Splitting Distribution

The Splitting Distribution bar shows values as percentages whichever weight ratio you insert in each Exit box. This allows you to visualize the percentage of interactions that will take a specific exit.

For instance, as shown in the screenshot below, you can choose to direct 50% of your interactions to one BPO and send the remainder 50% to a different third party.

Weight ratio: You can enter any whole number between 1 and 1,000,000.
Additionally, and as mentioned in Working with variables, it is also possible to add a variable to get the weight ratio value.
Please note that the number you enter here is treated as a relative quantity, and it will be represented as a percentage in the Splitting Distribution. The Splitting Distribution is automatically calculated once you input a number.

For example, if you have two exits, and enter 5 as the weight ratio in both, the Splitting Distribution will show: Exit #1 (~50.0%), Exit #2 (~50.0%). Change this to 10 and 5, and the Splitting Distribution will be updated to: Exit #1 (~66.7%), Exit #2 (~33.3%).

📘

Note

When, at least, one variable is used to define a weight ratio field of a “Traffic Splitter” step and its associated exit is enabled, the distribution summary bar and the related percentages will not be displayed, since it is only possible to know the variable’s value during the component’s execution. Please refer to the image below.

Exit name: Choose an adequate name for the exit in order to quickly find it in the flow.

Send to: Direct your incoming traffic to a component.

Toggle: Click on the toggle to enable/disable an exit. The Splitting Distribution will be recalculated every time you do so.

• ENABLED EXIT:

• DISABLED EXIT:

Add Exit:

Click on Add Exit to add and configure more Exit boxes.

Traffic Splitter Algorithm

A deterministic algorithm is used to decide which Exit is triggered in the Traffic Splitter component. Please note that:

• The execution order of the Traffic Splitter exits is guaranteed.
• Each cycle is deterministic and includes the minimum number of interactions to get the configured distribution.
• The minimum number of interactions to get the configured distribution is calculated by dividing the sum of all weights by the Greatest Common Divisor (GCD). For example, with exits weighted 55 and 45 and a CGD of 5, the cycle length is 20 interactions.
• Exact percentage splits are not guaranteed at the end of each cycle.
• The configured split distributions are reset every time a new version of a Studio flow is published (even if the Traffic Splitter weight ratios are not changed).

Error Handling

You can use the “Error Handling” section to define the behavior for unexpected failure during the execution of a component. For the Traffic Splitter component, the default behavior on error is “End flow”. For more information on this section, please refer to the "Error handling" documentation.