...
- Timing conditions;
- Triggers.
Timing conditions
This type of conditions determines the time for messages sending. Only one timing condition can be chosen for each block. There are such timing conditions:
- Send immediately. The default condition. Sends the contents of the block as soon as the parental block (the block standing on the left in the branch) has been sent;
- Send with delay. Allows you to set the relative delay for sending the block. Once the block is activated, the timer is switched on for the amount of time set in the condition. When the timer expires, the message is sent to the subscriber;
- Send a particular time. Allows you to send the message at the exact time. You can specify the Date, Time and Time zone. If such a block is activated before the specified time, the tunnel will wait for the time and only then continue to send out this branch. If the block is activated after more than an hour after the specified time, then this block won't be sent, but the following blocks after it will continue to be sent, depending on their conditions.
Triggers
There are 3 basic types of trigger conditions, which in turn have options:
...
In order for the trigger condition “visit website”, it is necessary that the source code of the widget leeloo.ai be present in the site code, the address or domain of which you are registering in the condition.
Functions START / STOP
The START / STOP functions allow you to redirect clients from one tunnel to another without a subscription and stop sending messages from the current tunnel.
If the specified condition is met in the block, the following actions will be performed: Start of sending (START) messages starting from the specified block of the selected tunnel AND / OR stopping sending (STOP) messages starting from a certain block of another tunnel.
As you can see from the schema above, when you click on the "Message template" button to which a template with the name "One more template" is attached in the previous block, messages from the tunnel "Sun" will start, starting with the block "Second block of the test tunnel" and stop sending messages from the tunnel "Sky", starting from the first block. That is, the first unit will not sending.
Redirecting a subscriber to another tunnel
If you just want to redirect a subscriber from one tunnel to another after receiving a specific tunnel block, without requiring the subscriber to interact (clicking a button, etc.), then no conditions need be added. You just need to specify the completion of sending messages from the current tunnel to STOP and start sending messages from the tunnel to which you want to redirect the subscriber to START
In the case above, after the subscriber receives the block that goes before the "Second Test Tunnel Block", the tunnel "Sky" will begin to be sent from the first block and the sending of blocks from the tunnel "Sun" (the current) will cease, starting with the block The second block of the test tunnel (the block on which the condition is established). That is, the subscriber will not receive this block anymore.
| Note | ||
|---|---|---|
| ||
If the subscriber subscribed via LGT to the tunnel, reached the block where the START / STOP functions are activated, it was redirected to another tunnel and it will be signed again, then the redirection will not happen the second time. This is a protective function that aims to prevent looping of the tunnel, for example, if |
...
the redirection goes to the first block of the same tunnel. |
Movement on a particular branch when you click a certain button
An example of building tunnel blocks so that when a particular button is clicked in a tunnel message, the subscriber goes through a specific branch of the tunnel.
In the "Option Choice" block there are 3 buttons to which different links are attached. When you click on the first button, the subscriber will receive a message from the Variant 1 block and continue receiving messages from this branch. When you click on the second button, the subscriber will receive the second block of Option 2 and continue along this branch of the tunnel. When you click on the third button, the subscriber will receive the third block "Variant 3" and continue moving along this branch to the right. In the case of Option 1, the condition will look like this:
In button 1 of the "Option selection" block, the link corresponds to the reference from the condition of the block Option 1. In the second button, the link corresponds to the link from the condition of the block Option 2 and in the third button the link corresponds to the link from the condition Option 1.
| Info | ||
|---|---|---|
| ||
You can set as several conditions, then the Start and / or Stop will occur if at least one of the conditions is met. For example, set 2 conditions: 1) click on the Link button 2) visit a certain website. If the client just clicked on the button, the Start and / or Stop execution will start immediately. If there are no conditions, then the block will come anyway, based on the set time delays and timers. If one condition is met, and after a while the second, then the block won't come a second time. |
Inverse conditions
The function of the inverse condition implies that the condition is not met. When you enable this function, you need to set the time that is given to perform the specified action in the condition. If during this time the condition is not fulfilled, then the actions (Start and / or Stop a certain tunnel) are performed.
In the case of the screenshot above, if the "Message template" button to which the "One more template" template is attached has not been pressed for 5 minutes after receiving the message from the previous block, the messages from the tunnel "Sun" will start, starting with the " The second block of the test tunnel Second block"and stops sending messages from tunnel "Sky", starting with the "First block" block. Keep in mind that if you do not specify which tunnel will be stopped (usually the current one), if the condition is met, in addition to starting sending messages from the tunnel set in the Start options, a message will come from the block on which the condition is set.
| Info | ||
|---|---|---|
| ||
* The order can get the status "Failed" for several reasons. The most common of them are:
|