Navigation Path​

  1. In the ​Main Navigation​, click ​Groups​.
    ⇒ The ​Groups​ window opens to the ​Group​ tab.
  2. In the ​Actions​ column, clickChange Settings​ or the symbol.
    ⇒ The ​General Settings​ window opens.
  3. Click ​Sendout Options​.
    ⇒ The ​Sendout Options​ window opens.

Purpose​

The ​Sendout Options​ tab defines settings that affect your message sendouts in this group.

Sendout Options​

Setting

Description

​Approvals List​

Defines the approvals list that is contacted for message moderation. The approvals list contains a list of system users who can approve messages to start a sendout. The process starts whenever an author lacks the permission ​Messaging: Send Email Messages 601​. 

If the button "four-eyes principle required" is selected, the author will not be able to approve messages themselves even if they have permission. The message will need to be approved by another member of the list. 

​Sendout Speed​

Defines the sendout speed of email messages in the group. These settings do not affect SMS or push notification sendouts.

External factors can affect the sendout speed. These factors include the current load on the receiving email server or the quality of the cellular network connection. For smooth message delivery, it can be beneficial to slow down the sendout speed. We recommend a slower sendout speed for new address lists to proof the validity of email addresses.

  • ​Maximum Sendout Speed:​ Sends email messages with the fastest possible processing and sendout speed.

  • ​Distributed Evenly Over Time Frame:​ Sends email messages at an even rate over the course of the time frame. In the ​Time Frame​ area, you must enter the ​Start Time​, ​End Time​, and ​Time Zone​.

  • ​Defined Speed:​ Sends emails at a defined speed. The sendout speed is calculated as a set number of emails per hour. The emails will be sent over the course of the hour, not all at the same time on the hour. Select the number of emails per hour from the drop-down list.

​Time Frame​

Limits message sendout to a certain time frame. For example, you can limit message sendout to to happen between 9:00 and 12:00 every day.

If Mapp Engage does not complete the entire sendout in the time frame, it pauses sendout at the end of the time frame. Mapp Engage resumes sendout at the beginning on the time frame on the following day.

The time frame does not apply to single messages and SuperMessages.

To remove the time frame and send messages at any time, reset the time frame to ​--:--​.

  • ​Start Time:​ Defines the hour and minute when sendout starts.

  • ​End Time:​ Defines the hour and minute when sendout ends.

  • ​Time Zone:​ Defines the time zone. The sendout can be adjusted to the time zone of the contacts in the group.

​Message Limitation​

Limits the number of messages that Mapp Engage sends to a contact in a certain time. The setting applies to the group and considers all sendouts in the system.

  • ​Consider Message Limitations:​ Mapp Engage only sends messages when the message limit of the contact has not yet been reached. Once either of these limits has been reached, Mapp Engage stops sending messages to this contact. Both system-wide and contact-specific limitations are considered.
    Message limitations apply to email, SMS, and mobile push. Message limitations do not apply to system messages or single messages.

  • ​Ignore Message Limitations:​ Messages in this group are not limited by either system-wide or user-specific limitations.

​Password Protection​

Requests a Mapp Engage password when sending externally prepared messages to Mapp Engage. The password is identical to the password used to log in to the Mapp Engage web interface. You add the password in square brackets in the subject line. Before sendout to the group, Mapp Engage removes the password from the subject line.

​Robinson List​

Adds a Robinson list to the sendout.

  • ​On:​ The Robinson list applies to email and SMS sendouts in this group.

  • ​Off:​ The Robinson list does not apply to any sendouts in this group.

The Robinson list is managed outside of Mapp Engage and contains all the addresses that you do not want to contact. Mapp Engage checks the list before sendout and does not send messages to these addresses. One Robinson list can be used for multiple Mapp Engage systems.

​Subject Prefix​

This input field is used to enter text that is added to the subject line of every email in this group in square brackets. The maximum length of the prefix is 40 characters.

Mandatory Fields for Sendout​

Defines whether certain fields or settings are necessary before a message can be sent to this group.

The configuration applies to both group sendouts and split sendouts. It does not apply to group sendouts initiated with an automation.

Setting

Description

​Selection​

  • ​On:​ Makes a selection mandatory for all sendouts in this group.

  • ​Off:​ Does not request for a mandatory a selection.

​Message Category​

  • ​On:​ Makes a message category mandatory for all sendouts in this group.

  • ​Off:​ Does not request for a mandatory message category.

​External Message ID​

  • ​On:​ Makes an external message ID mandatory for all sendouts in this group.

  • ​Off:​ Does not request for a mandatory external message ID.

List-unsubscribe Header​

A list-unsubscribe header inserts an unsubscribe button into a message. The recipient clicks this button to unsubscribe from the group.

Most ISPs and email clients support list-unsubscribe headers. A list-unsubscribe header improves sender reputation with ISPs and has a direct effect on the deliverability of a message.

If your messages contain links that manage unsubscribe requests outside Mapp Engage, add custom list-unsubscribe headers. The custom values ensure that a recipient can click either the unsubscribe link or the unsubscribe button to unsubscribe.

Setting

Description

​Setting​

Defines the type of unsubscribe header.

  • ​Header with standard value (Mapp Engage handles unsubscribes):​ The list-unsubscribe header contains standard values. Mapp Engage unsubscribes a recipient who clicks the unsubscribe button from the group. Both email-based and web-based headers are added automatically.

  • ​Header with custom values:​ The list-unsubscribe header is customized for use with an external contact management system. Enter the values that are used by the external system for a successful unsubscription. Mapp Engage does not manage the subscription status. Use the ​Personalization​ button to add placeholders such as Mapp Engage Variables or system information.
    When you use headers with custom values, you can enter values for email-based (mailto) and web-based (HTTP) headers.

    • In the ​Email​ input field, enter the list-unsubscribe header as a tag.
      Email example: <mailto:listunsubscribe-listName-externalMessageID-externalUserID@externalDomain.com>

    • In the ​Web​ input field, enter the list-unsubscribe header as a tag. The web header supports both HTTP and HTTPS.
      Example: <http://externalDomain.com/member/unsubscribe/?listName=listname@externalDomain.com&mid=externalMessageID&id=externalUserID>

  • ​Include Transactional Messages​: Inserts the list-unsubscribe header into transactional messages that are sent to this group. The setting does not affect single messages. If this checkbox does not appear, the list-unsubscribe header is automatically included. Please speak to your Account Manager or Customer Success Manager if you would like to make this optional.


List-ID Header​

Assigns a list-ID header to the group. The List ID is used by email client applications to apply rules and filters to the incoming message.

Setting

Description

​List-ID​

Customizes the default mailing list-ID that is associated with this group.

  • ​Revert to Default:​ Reverts the list-ID to the default setting. The default uses the group ID and group message domain.

  • ​Personalization:​ This button allows you to select and insert a personalisation at the location of the cursor in the ​List-ID​ input field.

Customized Email Headers​

In this area, you can add additional information to the header of the email. The system adds most of the header information automatically. For example, the sendout time.

Some header information is also added elsewhere. For example, the reply handling on the specific ​Reply Handling​ tab.

The input fields here are used to create non-standard header information and less commonly used entries.

For technical information, see http://tools.ietf.org/html/rfc2076.

You can also define email header values in the ​Compose Message​ window. The header settings that you create for a specific message override the header values defined in the group settings.

Any email header values that are defined for a group system message override the header values defined in the group settings. For more information, see ​Edit System Message (window)​.

The first input field defines the characteristic or parameter to modify. The second input field identifies the value to use for the parameter.

Enter the header name exactly as written here.

Modification

Header Name

Header Value

Sends replies to a defined address.

reply-to

Enter the email address.

Shows a specific from address in the email client.

If no value is specified, most email clients display the sender email address by default.

from

Enter the display name in quotes followed by the email address in angled brackets.

Example:

​"Joe Sample" <example@mywebsite.com>​

Sends a copy of the message to a specific address.

Use the configuration to track single (transactional) messages like order confirmations.

Hint: Do not use the configuration for group messages. Each address in the group is handled as a single message and starts the sendout of the message.

X-eC-messenger-CC

Enter the email address.

Sends a blind copy of the message to a specific address.

Use the configuration to track single (transactional) messages like order confirmations.

Hint: Do not use the configuration for group messages. Each address in the group is handled as a single message and starts the sendout of the message.

X-eC-messenger-BCC

Enter the email address.

Preferred Sendout Channel​

Defines the channel that Mapp Engage uses to contact somebody. These settings are only valid for recipients who lack a read mode that is stored in their attributes.

These settings are only relevant for multichannel messages. This option is being removed from Mapp Engage.

Setting

Description

​No Preference​

Defines that the preferred channel is not set.

​Email​

Defines that preferred channel is email. Group messages are sent via email to recipients who have not indicated a personal channel preference.

​Mobile​

Defines that preferred channel is mobile. Group messages are sent via mobile to recipients who have not indicated a personal channel preference.

​Mobile Push​

Defines that preferred channel is email. Group messages are sent via fax to recipients who have not indicated a personal channel preference.

Transactional Messages​

Configures transactional messages such as a purchase receipt or a shipping notification.

A transactional message is an automated response to an external event. The message includes a unique ID for every contact. This ID is called a transactional message ID (TMID). This ID allows you to track every message individually and to confirm that the contact receives and opens the message.

Mapp Engage considers any message with a TMID to be a transactional message. A transactional message can be a group message or a single message. However, most systems are set up to send transactional messages as single messages.

Setting

Description

​Transactional Message Mode​

Sets the transactional message mode.

  • ​On:​ Mapp Engage generates a TMID based on your pattern. The TMID is added to every sendout in this group.
    If you send messages to Mapp Engage with the API that contains an externally generated ID, Mapp Engage overwrites the external ID with the Mapp Engage TMID.

  • ​Optional:​ Mapp Engage generates a TMID based on the pattern you define. Mapp Engage adds the TMID to all message sendouts in this group that do not already have a TMID.
    If you send messages to Mapp Engage with the API that contain an externally generated ID, the external ID is not changed or replaced. In this case Mapp Engage does not generate a TMID.

  • ​Off:​ Mapp Engage does not generate or apply a TMID to sendouts in this group.

    • Use this setting if you send transactional messages with the Mapp Engage API and your external system generates its own unique IDs.

    • Use this setting if you do not send any transactional messages in Mapp Engage.

​Pattern for the TMID​

Defines the expression that generates the transactional message ID. This field accepts a maximum of 1000 characters.

The pattern that you enter here must generate a unique ID for every message. The unique ID enables the system to track the messages individually.

Example: u=<%{user['PK']}%>m=<%${message['PK']}%>t=<%${ecx:formatDate(ecm:addInterval(date.today, '-0d'),'yyyy-MM-dd\'T\'HH:mm:ss.SSS\'Z\'', ecm:timeZone('UTC'),'', false)}%>

This code generates a unique TMID for each recipient. Each TMID consists of the message ID, the user ID, and a timestamp.

Click the ​Personalization​ button to use attribute placeholders in the expression.

Leading Content and Closing Content for Email​

Defines content that is added in every email.

Setting

Description

​Leading Content (Text)​

Defines text that is added at the beginning of every text-only email message in this group.

​Leading Content (HTML)​

Defines HTML code that is added at the beginning of every HTML email message in this group.

​Closing Content (Text)​

Defines text that is added at the end of every text-only email message in this group.

​Closing Content (HTML)​

Defines HTML code that is added at the end of every HTML email message in this group.

Leading Content for Forwarded Messages​

Defines standard content that is inserted in the body of the email when the recipient forwards the message with the forward function in Mapp Engage. The message does not display the content. The leading content is added during the forwarding process.

You can use personalisation placeholders to insert the first or the last name of the recipient who forwards the message.

Examples

<%forwarder.firstname%>

<%forwarder.lastname%>

Setting

Description

​Leading Content (Text)​

Input field for the leading text that is added to every forwarded text message in this group.

​Leading Content (HTML)​

Input field for the leading content that is added to every forwarded HTML message in this group.

Related Topics​

​Message Moderation​
​Message Limitation​
​Robinson Lists​
​Transactional Messages​
​Add Custom List-Unsubscribe Headers​
​Add Standard List-Unsubscribe Headers​
​List-ID Headers​