First steps
User Data
- Responsive Email Editor Review
- Designing your email
- Creating Synchronized Modules
- Setting Up Responsive Email Design
- Setting Up Smart Containers
- Creating a Gmail Promotions Annotation
- Adding The Rollover Effect
- Adding Anchor Links
- Module Library
- Adding a Table to an Email
- Adding Custom Fonts
- Creating CTA Button
- Working with Images
- Creating Timer
- Using AI in the Email Editor
- Messenger Protocol Support in Email Clients and Platforms
Omnichannel
- Setting Up Widgets for Your Site
- Widgets Gamification
- Widget Calling
- Setting Up Locations for the Widget Calling Rules
- Storing data from widgets to contact fields
- Using Annoyance Safeguard
- Actions After Form Submission
- Replacing Double Opt-In System Workflow
- Creating Pop-ups via Google Tag Manager or WordPress
- Sending Yespo Widget Events to Google Analytics
- Using A/B Tests for Widgets
- Collecting Contact Information Using Request Forms
Automation
- Building and Editing Workflows
- Configuring Workflow Start/Stop Conditions
- Start Block
- Popular Blocks
- Message Blocks
- Using One from Many Message Block
- Contact Blocks
- Conditions Blocks
- Other Blocks
- Message to Segment Blocks
- Time Blocks
- Advanced Workflow Block Parameters
- Setting Up Allowed Send Time
- Using Workflow Launch History
- Webhook Workflows
- Workflow Troubleshooting
- Double Opt-In
- Welcome Сampaign
- Welcome Series Segmented by Category
- Launching a Workflow After a Contact Import
- Regular Workflow for a Segment
- Birthday Campaign
- Linking Workflow to the Button
- Using Variables from Order in Workflow
- Collecting Order Feedback
- Customer Reactivation
- Sending Extra Campaigns
- Sending Reminders at the Time Specified by the User
- Sending Campaign to Those Who Did Not Open the Previous One
- Using A/B Tests In Workflows
Personalization
Analytics
- Email Campaign Report
- Web Push Campaign Report
- Viber Campaign Report
- Mobile Push Campaign Report
- App Inbox Campaign Report
- Telegram Campaign Report
- In-App Report
- Widget Report
- Triggered Campaign Report
- AMP Campaign Report
- SMS Campaign Report
- Multilingual Campaign Report
- Setting up UTM Tags
- Revenue from Campaigns
- Tracking Campaign Performance in Google Analytics 4
- Message Analytics
Multilanguage Campaigns
Events and Behaviour Tracking
Recommendations
API
Security and Compliance
Conditions Blocks
Conditions blocks (except for the Split block) 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 eight conditions blocks in the system:
- Condition
- Split
- Sent?
- Delivered?
- Opened?
- Clicked?
- Included in Segment?
- Current day/time
Note
The following blocks cannot be attached to the Start block:
- Sent?
- Delivered?
- Opened?
- Clicked?
Condition
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.
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?
The block checks whether the message was sent.
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 5 minutes.
Delivered?
The block checks whether the message was delivered.
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.
Opened?
The block checks whether the recipient opened the message, and depending on the result (Yes/No) splits the workflow into two paths. 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.
Clicked?
With this block, you can check whether the contact clicked on the message and set alternative actions based on the results of the check. The block takes into account any click on any link except the unsubscribe link. Note that you can't choose to check a specific link.
In this workflow, the contacts 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
The Sent?, Delivered?, Opened? and Clicked? blocks check messages within one workflow and do not consider whether a similar action has been performed with a message in another workflow.
The Sent?, Delivered?, Opened? and Clicked? Blocks Parameters
The blocks contain two alternative parameters that take into account:
- Only the last message. The block checks only the last message before it. If the message is sent (delivered, opened, clicked), the workflow continues along one path; if it is not, it continues along the other.
- All messages. The block checks all messages before it. If all messages are sent (delivered, opened, clicked), the workflow continues along one path; if not all or none, the workflow continues along another path.
Note
We recommend to additionally use the block Timer- (Popular or Time 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.
Included in Segment?
The block checks whether the contact is included in a certain segment.
The block has one basic parameter — Segment. In the field, select the segment to check for the contact's membership in that segment.
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 also contains advanced parameters, which are detailed in a separate article.
Current Day/Time
The block checks whether the current path is triggered based on a certain date, weekday or time.
You can set up the following conditions for sending:
- certain day of the week;
- specific date;
- specific time;
- specific time on a specific date/day of the week.
Setting a specific date excludes the option to choose a day of the week. You can specify the date or day of the week and time either together or separately. By default, the time check option is inactive.
If you select a time without specifying a day, the specified time period will be checked every day.
If you choose both a day and time, the time will be checked on the specified day.
The time is checked according to the user's local time, eliminating inaccuracies associated with daylight saving time changes.
The specified boundary values are included in the check. For example, if you set the time from 08:00 to 12:00, and at the time of the check, it is 12:00, the script will follow the Yes branch.
Activating the Use contact’s time zone parameter will allow you to send a message at a specific time, taking into account the contact’s time zone.
Let's look at how the block works. For example, on April 5, 2023, at 7:00 PM, there is a webinar that you can register for until the beginning of the broadcast. Depending on the date and time of the user's registration, you want different versions of email messages to be sent to them:
- Email 1: Before the day of the event – "We look forward to seeing you at the webinar on April 5 at 7:00 PM."
- Email 2: On the day of the event until 5:00 PM – "Already today! See you at 7:00 PM."
- Email 3: On the day of the event after 5:00 PM – "Starting very soon! Don't miss the beginning at 7:00 PM."
The workflow operates as follows:
- The workflow proceeds to the 'Current Day/Time' block and checks today's date (Is it now 05/04/2023?);
- If the date does not match the one specified in the parameter, the workflow will follow the 'No' branch – sending Email 1;
- If today is 05/04/2023, the workflow will follow the 'Yes' branch and check the time of day;
- If it is not later than 17:00, it will send Email 2;
- If the current time does not match the specified time – it means it is later than 17:00, and in that case, it will send Email 3.
Also, using the same conditions, you can opt not to send your campaign:
- On specified days
- On specified time
- At certain times on certain days
- At a certain time and day