Login

Security and Compliance

Integration

Website Integration

Conditions Blocks

Conditions blocks check the contact's compliance with a certain condition, split the workflow into two paths (Yes/No), and run one of them depending on the answer.

There are seven condition blocks in the system:

  • Split
  • Sent?
  • Delivered?
  • Opened?
  • Clicked?
  • Included in segment?
  • Current time

Condition blocks

You can use condition blocks only after any of the general or action blocks. You can’t start a workflow with a condition block.

Important

You can add to the Start block (General blocks) only three conditions:

  • Split;
  • Segment?;
  • Current time.

Split

The block is used to split-test messages. It splits the workflow into two paths and randomly divides contacts between them. By default, the percentage ratio is 50/50, but you can change it using the slider in the settings on the right.

Condition blocks in the eSputnik system

For example, you can create a workflow to test the effectiveness of two different communication channels or two campaign types within one channel by setting the same split percentage.

The above example is a workflow testing Email and Viber. Based on the set percentage, one half of your subscribers will receive an email, and the other half will receive a Viber message. Further analysis will help determine which channel is more effective.

Sent?

Block Sent? is used to check if a message or message chain placed before this block in the workflow has been sent.

Workflow's example

The example above shows the workflow where the mobile push with the experimental recommendation algorithm is sent first. The system will not send this message without data to generate such recommendations.

At the same time, in addition to the Delivered status, mobile push notifications also have the In Progress status. It can take a long time between sending and delivery, so the Delivered? check is unsuitable.

If the check shows the system did not send the first message, the workflow will send the second one with a universal recommendation algorithm.

The Timer block is necessary for the system to have time to check the fact of sending a message. The recommended time in the timer settings is 2 minutes.

Set one of the parameters for the Sent? block:

  • Take into account only the last message: the block checks whether the last preceding message was sent.
  • Take into account all messages: the block checks whether all preceding messages were sent.

Important

The block only checks for sending within a specific workflow and does not consider whether the same messages were sent under other workflows.

Delivered?

The block checks whether the message was delivered.

Condition blocks in the eSputnik system

In this example, subscribers who received the first message would eventually receive the second one, and the rest would be in the segment with invalid contacts. Based on the result, you’ll be able to analyze the effectiveness of email as a communication channel and reduce the error rate in subsequent campaigns.

The block has 2 setting options:

  • take into account only the last campaign. The block checks whether the last preceding campaign was delivered.

Condition blocks in the eSputnik system

  • take into account all campaigns. The block checks whether all preceding campaigns were delivered.

Condition blocks in the eSputnik system

Important

The block checks only the delivery of messages within one particular workflow and does not take into account the delivery beyond it.

Opened?

The block checks whether the recipient opened the message. For example, if the recipient didn’t open your email over a certain period of time, you can send one more email but with a different subject, or send a Viber message or SMS with the same content.

Condition blocks in the eSputnik system

The block has 2 setting options (similar to Delivered):

  • take into account only the last campaign. The block checks whether the last preceding campaign was opened.
  • take into account all campaigns. The block checks whether all preceding campaigns were opened.

Important

The block checks only the opens within one particular workflow and does not take into account the opens beyond it.

Clicked?

The block checks whether the recipient clicked any element in the message. It takes into account any click on any link except the unsubscribe link. Note that you can't choose to check a specific link.

Condition blocks in the eSputnik system

In this workflow, the recipients who clicked in the first email and are expected to be interested in your offer, are sent the following email with a special discount, more details, benefits of the presented product or brand, etc. This workflow ends for those recipients who didn’t click.

Note. We recommend to additionally use the block Timer (General blocks) before the blocks Sent?, Delivered?, Opened? and Clicked?. Otherwise, for a major part of your subscribers, the workflow will run the No path.

Since the system immediately checks the condition compliance, and subscribers can’t immediately respond to your campaign, there is no reliable data to run the Yes path.

The block has 2 setting options (similar to Delivered):

  • take into account only the last campaign. The block checks whether there were clicks in the last preceding campaign.
  • take into account all campaigns. The block checks whether there were clicks in all preceding campaigns.

Important

The block checks only the clicks within one particular workflow and does not take into account the clicks beyond it.

Included in Segment?

The block checks whether the contact is included in a certain segment.

Condition blocks in the eSputnik system

In this workflow, the subscribers who are included in the segment Valid email receive an email; the subscribers who aren’t included receive an SMS. Similarly, you can use other subscriber data (activity, orders, personal data, etc.) to create the most effective and personalized campaigns.

The block has 2 setting options:

  • Segment. Required field where you need to select the segment to be checked.
  • Contact identification. Consists of three setting options - Contact’s email, Contact ID, Phone - used to identify a contact and included them in the corresponding segment. To fill the data correctly, follow the tips that appear when the corresponding field is hovered over.

Condition blocks in the eSputnik system

Important

When searching contacts for Included in Segment? block the following rules apply:

  • Contact ID has the highest priority among all parameters
  • If externaiCustomerId is specified, contact search will be performed by externaiCustomerId.
  • If externaiCustomerId is not specified, contact search will be performed by email address or phone number.

Current Time

The block checks whether the current path is triggered based on a certain date or weekday.

You can set up the following conditions for sending:

  • certain day of the week;
  • weekends or weekdays;
  • specific date.

Condition blocks in the eSputnik system

For example, you want to send different versions of your email depending on the current date: before the event and on the day of the event. Such a workflow would run as following:

  • workflow reaches the block Current time;
  • checks what the date is today (now 30.03.2020?);
  • If the date corresponds to the specified parameter, the workflow will run the Yes path;
  • if it doesn't, the workflow will run the No path.

In addition, using the same conditions, you can opt not to send your campaign on certain days.

Condition blocks in the eSputnik system

Any Questions?
We’re always happy to help!
Discount services
Schedule a Call
Fill in the form, and our specialists will call you back as soon as possible.
Discount services
Chat Support
We’re waiting for your questions!
Discount services
Email
Contact the support team