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 Subscription
- 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
Using One from Many Message Block
The One from many block sends the best one from all messages with specific tags. The main purpose of the block is to understand what option is the best. At first, the block sends specified messages randomly to gather performance data. After a few thousand messages are sent, the algorithm starts to prefer the messages with higher click-through rate (CTR). At the same time, the block considers the message's previous performance and the last messages sent to the contact to select the best option.
This block can be considered a continuous A/B test that improves performance with every message sent, providing the best possible CTR for the given set of messages.
We encourage you to add messages to One from many block at any time. If you have any idea about a better version of the message, just mark it with the tag, and the One from many block will give it a try.
Adding Tags to Messages
Open the message in the editor, find the Tags field, and add the necessary ones: Cart, Browsing, Reminder, etc.
Setting Up Workflow with One From Many Block
The One from many block participates in workflows like any other message.
1. Open or create a workflow in the Automation → Workflows section.
2. Drag the One from many block from the left sidebar into the workflow.
3. Configure the block parameters:
- Send via — messages’ media channel.
- Application — the name of a Mobile Push app or Telegram bot (there is no option to select an application if there is only one app or bot registered in the account — the corresponding parameter will be applied automatically).
- Include variants with tags with which messages will be triggered.
- Exclude variants with tags so that the block does not trigger them. We recommend implementing a persistent tag like Excluded or Stopped and then adding it to low-performing messages to stop their sending. The check for sending or excluding messages occurs every time the message is sent.
Note
- The numbers next to the tags indicate the number of messages with those tags. “0” means the tag exists but must be added to the appropriate messages.
- Create a tag in the message editor in advance because it cannot be created while editing a workflow.
- Send only in specified hours — by default, daytime hours are set for all organizations from 8:00 a.m. to 8:00 p.m. to avoid bothering contacts with messages at the unsuitable time and postponing the campaign until the allowed period.
4. To quickly preview or edit the messages included in the block, click the preview icon in the field with the number of options filtered by tags.
5. Configure the launching workflow conditions and activate it.
Note
To diversify communication, the system avoids sending messages that have been used and sends one of the unused ones. The system checks which messages have already been sent to a contact
- within four days;
- as part of a workflow (for example, when several One from many blocks are used).
If all variants have already been sent, the message selection is random.
Analytics
To investigate the messages’ effectiveness, go to the Campaigns → Reports section and enter the tag in the search field or click on it in the report list.
To manually stop a message with low performance, add a tag specified in the block's exclusions (for example, Excluded or Stopped).
Using Block
The One from many block helps to A/B test different messages in your workflows.
Use this block to
- Simplify the A/B testing process: There is no need to create separate workflow branches for each message or channel option, which significantly reduces the time for preparation and subsequent workflow adjustments and the probability of making a mistake when changing the message.
- Diversify communication in trigger campaigns: If one workflow launches several times for the user, we recommend diversifying the messages so that one customer doesn’t get the same content for training or lesson reminders, abandoned carts and views.
- Test hypotheses: If you have ideas for improving messages, just add a new option to the block settings with a few clicks and watch the result — there is no need to edit the workflow and run A/B tests separately.
- Continuously optimize campaigns: We recommend regularly adding new messages to achieve better results. Remove or add the appropriate tag to replace, upgrade, or discontinue an option with lower performance.