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
Start Block
The Start block is required to create a workflow. It automatically appears in a new workflow by default. There can only be one Start block in the workflow.
Note
Start block cannot be deleted
Early Workflow Stop Configuration
You can enable automatic checking of contacts participating in the workflow:
- whether they participated in a certain event (for example, they signed up for a course and already received tutorial series);
- whether they are in a certain segment (for example, it is necessary to cover newcomers with a campaign and not launch it on active buyers);
- whether they made an order (for example, 7 days before the start of the workflow).
Note
Workflow stops earlier if a condition is met. The check takes place at the workflow's start and after each Timer block.
- Activate the Stop configuration switcher.
- Select one of the check types using the radio button.
- Event-based;
- Included in a segment;
- Order-based.
Event-based Workflow Stop
In the Event drop-down list, select the event that will stop the workflow for the corresponding contact. The workflow stops if the event happens within the selected period before the workflow starts or any time after it starts. In the Period field, you can set the time before the start of the workflow, during which the event must be checked. By default, the block checks for events since the activation of the workflow.
${key} is the universal variable for the event unique key specified in the block by default. When the system starts a workflow, it checks the selected event: if it finds the event unique key, the workflow ends for this contact.
You can see the event unique key in the Automation → Event History section.
Important
The event unique key (email, contact ID, etc.) must match in the event that started the workflow and the event that should end the workflow.
Included in a Segment Workflow Stop
Select a segment from the drop-down list in the Segment field. If the system detects that a contact enters a specified segment, it will stop the workflow for them. The system identifies contacts by one of the parameters:
- Phone;
- Email;
- Contact ID in Yespo.
Order-based Workflow Stop
The workflow stops if the contact has placed an order within the selected period before the workflow starts or any time after it starts. Set the time to check in the Period field.
The system searches contacts by one of the parameters:
- Phone;
- Email;
- Contact ID;
First, the system uses Contact ID, if it’s not specified, then by externalCustomerId to search for a contact, if this is present in the event parameters.
