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 within one workflow, 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.

šŸ“˜

Note

By default, you prepare and tag a pool of messages in advance. The One from many block selects and sends one variant from that pool based on performance. With auto-optimization enabled, the block can also generate new message variants for moderation.

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. 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.

Mobile Push message editor with the Tags field highlighted, showing an empty Add tag dropdown

Setting Up Workflow with One From Many Block

The One from many block participates in workflows like any other sending block.

  1. Open or create a workflow in the Automation → Workflows section.
Automation section navigation with the Workflows tab highlighted, showing the workflows list including One from many (7day_challenge)
  1. Drag the One from many block from the left sidebar into the workflow.
Animated workflow editor demonstrating dragging the One from many block from the left sidebar into the canvas, shown before the block is placed between the Start and End blocks
  1. Configure the block parameters:
  • Send via — messages’ media channel.
  • Application — the name of a Mobile Push app (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).
One from many block settings with Send via set to Mobile Push and Application set to MyApp, both highlighted, with no variants selected yet
  • 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.
One from many block settings with Include variants with any of tags set to 7day_challenge and Exclude variants with any of tags set to Underperformed, both highlighted
šŸ“˜

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.
  • Get AI suggestions based on message variants: Generate additional versions of messages and their translations based on existing ones.
One from many block settings with the Get AI suggestions on the message's variants section and Generate now button highlighted
šŸ‘

Recommendation

Use the AI generation feature wherever Mobile Push messages are used in the One from many block. Consistent application across campaigns ensures you capture every opportunity to engage contacts with the highest-performing copy.

Learn more about generation >

  • 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.
One from many block settings with the Send only in specified hours toggle highlighted, currently disabled

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.

Animated One from many block settings demonstrating clicking the preview icon next to the number of variants selected to view the message options
  1. Configure the launching workflow conditions and activate it.
šŸ“˜

Note

To keep messages fresh, this block avoids re-sending the same message variant:

  • Regular workflows (e.g., Reminders): The block won’t send any variant that was sent to the contact in the last 4 days, across launches. Recommendation: add at least 8 variants.
  • Workflows with multiple One from many blocks (e.g., Abandoned subscription): The system doesn’t repeat variants from any One from many block within a specific workflow launch. Recommendation: Add at least 2Ɨ as many variants as the number of One from many blocks in the workflow.

If all eligible variants for this contact are exhausted, the block sends the highest-CTR variant.

Auto-Optimize Variants

After saving the workflow, you can enable the Auto-optimize variants option for the One from many block.

Proactive Optimization

This option lets the system generate new message variants during optimization and keep the message pool updated with stronger-performing variants.

When auto-optimization is enabled:

  • The system generates new message variants separately for each segment based on existing examples from that segment.
  • Users must moderate generated messages before the next optimization iteration starts.
  • Consecutive iterations run with a cooldown period, so new variants are not generated continuously.
  • Underperforming messages are removed from the pool according to the existing Underperformed tag logic.
  • Manual message generation is unavailable for the block until auto-optimization is stopped.

You can stop auto-optimization at any time.

When the system generates new messages, users receive email and App Inbox notifications during business hours. Blocks with generated messages awaiting moderation are highlighted in the workflow editor.

Underperformed Tag

Underperformed is a system tag that is automatically assigned to message variants in the One from many block when their click-through rate is significantly lower than that of other variants in the pool. Variants with this tag are excluded from further automatic selection.

One from many block settings with the Underperformed tag highlighted under Exclude variants with any of tags

Tag Assignment Rules

The system analyzes all message variants in the pool and identifies low-performing variants based on the following criteria:

  1. The variant has more than 100 sends within a single workflow.
  2. Its selection probability is below 2%.

If both conditions are met, the system assigns the underperformed tag to the variant.

šŸ“˜

Note

  • If the pool contains fewer than 4 messages, the system does not assign the underperformed tag and does not exclude any variants.
  • If a campaign is sent to multiple segments, the algorithm evaluates low-performing messages separately for each segment.

Analytics

The aggregated CTR trend for all messages in the block is displayed in the block settings (Performance report). The system selects the Last month period by default.

Animated workflow diagram with a One from many block settings panel showing 4 variants selected and Performance report CTR 14.0%, demonstrating opening the performance report

The Performance report includes the following tabs:

  • General — summarized information about the performance of all message variants.
Performance report window with the General tab selected, showing a CTR over time line chart for the last month
  • By variants — shows detailed statistics for each message variant.
Performance report window with the By variants tab selected, showing a table of 3 message variants with traffic share, sends, clicks, and CTR data

The table shows the following metrics:

  • Traffic share — the percentage of the audience that received the variant;
  • Sends — the number of messages sent;
  • Clicks — the number of clicks;
  • CTR — the click-through rate of the variant.
By variants performance table with the Traffic share column header highlighted, showing Sends, Clicks, and CTR data for 3 message variants

You can sort the data by each of these metrics:

By variants performance table with the sort dropdown open, highlighted, showing CTR selected among Traffic share, Sends, and Clicks options

To analyze the performance of individual messages, go to the Campaigns → Reports section and enter the tag in the search field or click on it in the report list.

To analyze the performance of individual messages, go to the Campaigns → Reports section and enter the tag in the search field or click on it in the report list.

Campaigns Reports page with the 7day_challenge tag entered in the search field and highlighted on each campaign in the results list

To manually stop a message with low performance, add a tag specified in the block's exclusions (for example, Excluded or Stopped).

Routing Different Segments to Different Message Pools

The One from many block itself does not support routing by segment — it only selects a variant from messages matching the tags configured in the block. If contacts from different segments should receive messages from different pools (for example, segment A gets one of three pool-A messages, segment B gets one of three pool-B messages), add a Branch block before the One from many block: create one branch per segment, and place a separate One from many block (with its own Include variants with tags) on each branch.

šŸ“˜

Note

Keep the number of segment checks in a single Branch chain reasonable (up to ~10). Checking a contact against dozens of segments at once in one workflow step adds unnecessary load — if you need to route across many segments, split the logic into multiple sequential Branch checks instead.

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.


Did this page help you?