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
Time Blocks
The blocks delay the execution of workflow actions or execute actions at a specified time and contains two block types:
- Timer
- Start on date
Timer
The block is used to set a time gap before the next action or message sending. It is placed before a block you want to delay.
Contact confirmation triggers the workflow with a drip welcome series in the example. A new contact receives a welcome email after confirmation, a second email after two days, and a third after the next three days.
To set up Timer, configure one of 2 or both parameters:
- Wait time
- Wait until
You can configure all parameters or only one; at least one parameter should be configured to start a workflow.
Wait Time
Enter the time of delay, and select the parameter to which it will be applied:
- minutes
- hours
- days
- months
Important
If you delay for 1/2/3 days, the delayed action will start 24/48/72 hours after the workflow is triggered. If a person subscribes to you at 7 a.m., they will receive the first email at 7 a.m. the next day.
Wait Until
In the Wait until parameter, you can specify the time yourself, use data from an additional field of the contact card or from the context parameter (the event that launches the workflow).
Specifying the Time Manually
Here you can select the day of the week and the time for sending.
If you set the sending time at 8:45 a.m. and the workflow starts at 3:00 p.m., the subscriber will receive the message at 8:45 a.m. the next day.
Important
If today is Tuesday and you've chosen to send a message on Monday, the message will be sent next Monday. If it's Monday today, the subscriber will receive the message today.
Using the Time from an Additional Contact Field
For example, you can use this option to set up reminders if you collect data in additional fields about the time your subscribers perform specific actions: make purchases, exercise, study, etc.
Select the contact field containing the time you want to wait.
The time from the contact field is based on the contact's time zone and must be sent to the text field in the HH:MM or HH:MM:SS format. If the field of a contact participating in the workflow has a missing or written in an incorrect format value, the corresponding error will be displayed in the launch history of such a workflow.
Using the Time from a Context Parameter
You can use this option to set up reminders if the data about the time your subscribers perform specific actions is not tied to additional fields and you are focusing on actual data — for example, when the last event about the workout start was received.
Specify the event parameter containing the time to wait until.
The time from the event parameter is based on the contact's time zone and must be sent to the text field in the ISO 8601 format. If the value is missing or written in an incorrect format in the event that launches the workflow, the corresponding error will be displayed in the workflow's launch history.
Use Contact’s Time Zone Parameter
Activating this parameter will allow you to send a message at a specific time, taking into account the contact’s time zone.
Parameter Priority
For example, you've configured the following delay parameters:
- wait day;
- send on Monday.
- send time at 8:45 a.m.
The workflow starts on Sunday at 3 p.m. The system waits for 1 day (24 hours). Then it's Monday. The Wait 1 day parameter expires at 3 p.m. on Monday. The system checks the Send parameter. You have chosen Monday, today is Monday, so far everything is fine.
The system checks Send time. It’s set for 8:45 a.m., and the workflow is triggered at 3 p.m. The subscriber will receive the message not this Monday but only the next one at 8:45 a.m.
Start on Date
The block is used to send a message:
- before X days/hours/minutes before the date and time you send in the event;
- with the start time you send in the event or set manually;
- on date from an event parameter or specified in a block.
Note
- If the start time is taken from the event, the transferred time zone is applied.
- If the start time is set manually, the block will start in the time zone specified in your personal profile.
In the In field, specify when before the date to send the message: 1 hour, 3 days, 10 minutes, etc.
In Before date, you can take the required date from the sent event. In the box below insert the parameter name from the event, for example, ${starDate}.
Important
There are two supported formats for the date and time:
- UTC: 2011-12-03T10:15:30;
- UTC offset: 2011-12-03T10:15:30+02:00.
The UTC offset is the difference in hours and minutes from UTC for a particular place and date. UTC+02:00 is used in some countries of Central Africa Time, Eastern European Time, and South African Standard Time. See the full list here.
Activate the Use contact’s time zone parameter to send a message at a specific time, taking into account the contact’s time zone.