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:

  • Email
  • SMS
  • Viber
  • Web Push
  • Mobile Push
  • App Inbox
Message to segment blocks



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. Select the necessary message from the drop-down list or use dynamic variable ${emailMessageId}.

After selecting the message, you can proceed to its preview or copy the ID. Click on the three dots in the block of parameters and select the option.

Message preview
  • Segment: required parameter. Select the segment in the drop-down menu or use dynamic variable ${segmentId}.



Each segment in the eSputnik 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.
Common block parameters: Message, Segment, Send only in specified hours

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.
Web Push to segment parameter: Site
  • 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.