Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Current »

UA

image-20240611-123449.png

US

image-20240611-123805.png

RU

image-20240611-131051.png

Delay - Green block - a block for creating a temporary delay, a delay with allowable parameters, and sending the content block or action block at a precisely set time.

It can be placed after a content block or any other block.

There are three types of delays:

  1. Time interval delay

  2. Time interval delay with time frame

  3. Send at specified time

Time delay - allows you to set a delay for sending the next block of the funnel. As soon as the "Delay" block is reached, a timer is activated for the set time (delay interval). When the timer expires, the next block is sent to the subscriber

The minimum interval for "time delay" is 10 seconds.

The maximum interval is 999 days 23 hours 59 minutes 59 seconds

ksnip_20250210-070553-20250210-050556.png
  1. Time interval delay with time frame - activation of the next block after the specified interval with the indication of allowed days and hours for sending. With this type of delay, you can both schedule content sending on specified days and hours and restrict sending during undesirable times

    This type of delay works in three stages:

  2. First, the specified delay interval is applied

  3. Sending on allowed days

  4. Sending on allowed hours

ksnip_20250210-070904-20250210-050907.png

To select sending blocks on specific days of the week, click the "All days" button. A list with the names of the days of the week will open. Choose the ones you need or leave it as it is.

ksnip_20250210-071304-20250210-051308.png

Send at time – this field is used if you need to limit the sending of the block based on the time of day. For example, you may not want the tunnel block to be sent to the client at night. To do this, specify the allowed sending time, excluding the night hours. In the "Send at time" fields, set a range such as from 8:00 AM to 8:00 PM. You can also choose the time zone in which the restriction will apply

ksnip_20250210-071500-20250210-051503.png

Under this condition, if the block is activated during the night, for example at 10:35 PM, the sending of the next block will be paused until 8:00 AM. At 8:00 AM, the block will be sent.

  1. Send at specified time – this allows you to send a message at a specific time. You can specify the Date, Time, and Time Zone. Additionally, in this block, you can set an Allowable Delay for users who enter the block.

ksnip_20250210-071643-20250210-051647.png
  • If this block is activated before the specified time, the tunnel will wait until the time arrives and only then will continue the distribution along the green branch.

  • If the subscriber enters this delay block after the specified time but within the allowable delay, they will receive the content instantly.

  • If the subscriber enters this delay block after the specified time and after the allowable delay, they will receive the content along the red branch of the tunnel.

The maximum value for the "Allowable delay" field is 99 days, 23 hours, 59 minutes, and 59 seconds.

In case there is no connection from the red point and the subscriber reaches the exact date after the set delay, the user will stop moving through the tunnel

IMPORTANT: When setting delays with the option to specify a time zone, it is essential to take into account the time zone according to which content will be sent to your subscribers

IMPORTANT: When a subscriber enters a block, the scheduling of the next blocks is set. Changes to this delay do not affect the scheduled sending

IMPORTANT: Deleting a delay will result in the subsequent block not being sent

IMPORTANT: Subscribers for whom the sending is scheduled but has not yet occurred will not be available for the "send from the previous block" function

IMPORTANT: When changing time zones in your geolocation, it is necessary to plan the sending accordingly

  • No labels