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
Omnichannel
- Setting Up Widgets for Your Site
- 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
- Using Yespo Extension for Google Chrome
- Creating Pop-ups via Google Tag Manager or WordPress
- Sending Yespo Widget Events to Google Analytics
- Using A/B Tests for Widgets
Automation
- Building and Editing Workflows
- Configuring Workflow Start/Stop Conditions
- Start Block
- Popular Blocks
- Message Blocks
- Contact Blocks
- Conditions Blocks
- Other Blocks
- Message to Segment Blocks
- Time Blocks
- 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 Campaign to Those Who Did Not Open the Previous One
Personalization
Analytics
- Email Campaign Report
- Web Push Campaign Report
- Viber Campaign Report
- Mobile Push Campaign Report
- App Inbox 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
Integration
Message to Segment Blocks
The block sends one message to a segment. It’s used in a workflow after contact import or to launch a series of messages. For example, send a message to a segment, and then either resend it or send another message to those who have not read it or clicked the link.
Typically, one workflow includes either the block with one message to one contact (Contact blocks) or the block with the Message to segment.
There are six block types:
- SMS
- Viber
- Web Push
- Mobile Push
- App Inbox
Important
Do not use these blocks for triggered messages. If the event passes the token or contact ID, use one of the Message blocks (one message to one contact).
The blocks Message to segment are only used for events that pass the segment ID, or for workflows that are launched for a selected segment (for example, dynamic).
Even if you set Regular in Trigger configuration and select a segment, you still need to use the block with one message to one contact, because this trigger type doesn’t pass a segment group ID to the workflow. Instead, it launches the workflow separately for each segment contact and passes the email and contact ID at each launch.
Common Block Parameters
Each Message to segment block contains several parameters:
- Message: required parameter. You can select the necessary message from the drop-down list or use dynamic variable ${emailMessageId}.
- Segment: required parameter. Select the segment in the drop-down menu or use dynamic variable ${segmentId}.
Important
Each segment in the Yespo system has its own ID. For example, if you send an event and with an ID value pass the GroupId parameter
"name":"segmentId", "value":167039898
167039898 will be substituted into the workflow instead of segmentId, and the workflow will be launched to this segment. You need to know what the ID corresponds to so as to control the campaign, indicating what to send to which segment.
- Send only in specified hours: Enable this parameter to send messages only within a specified time gap.
Individual Block Parameters
- Site (Web Push to segment parameter): required parameter. The website that collects tokens is specified by default. If you have several websites, choose one from the drop-down menu.
- Application (Mobile Push to segment parameter): required parameter. An app identifier for accounts with more than one app. You can select the app to send notifications from the dropdown list or specify dynamic parameter ${appId}. The system extracts the app ID from the event that has triggered the workflow. When sending events through the SDK, this parameter is passed automatically.
