- 9 Minutes to read
- Print
- DarkLight
Sendout Options (tab)
- 9 Minutes to read
- Print
- DarkLight
Navigation Path
Audience > Groups >Change Settings > Sendout Options
Purpose
The Sendout Options tab defines settings for message sendouts in this group.
Sendout Options
Setting | Description |
---|---|
Message Moderation | Defines the approvals list for message moderation. The list includes system users who can approve messages to start a sendout. The process begins when an author lacks the "Messaging: Send Email Messages 601" permission. If the "four-eyes principle required" button is selected, the author cannot approve messages themselves even if they have permission. Another member of the list must approve the message. |
Sendout Speed | Defines the sendout speed of email messages in the group. It does not affect SMS or push notifications. External factors like the load on the receiving email server or cellular network quality can affect sendout speed. Slowing the sendout speed can ensure smooth delivery, especially for new address lists.
|
Time Frame | Limits message sendout to a certain time frame, e.g., between 9:00 and 12:00 daily. If the sendout isn't complete within this frame, it pauses and resumes at the start of the next time frame. This does not apply to single messages and SuperMessages.
|
Message Limitation | This limit considers all sendouts in the system and determines the number of messages Mapp Engage sends to a contact in a specified period.
|
Password Protection | When sending externally prepared messages, a Mapp Engage password is required. The password is added in square brackets in the subject line and removed before sendout. |
Subject Prefix | Enter text to be added to the subject line of every email in this group within square brackets. Maximum length is 40 characters. |
Mandatory Fields for Sendout
Defines mandatory fields or settings before a message can be sent to this group. This applies to both group sendouts and split sendouts but not to group sendouts initiated with automation.
Setting | Description |
---|---|
Selection | On/Off |
Message Category | On/Off |
External Message ID | On/Off |
List-unsubscribe Header
Defines the type of unsubscribe header to improve sender reputation and deliverability. 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 this feature.
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 |
---|---|
Header with standard value | Mapp Engage handles subscriptions. 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 | Customized for use with an external contact management system. Enter the values that the external system uses 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. Values for email-based (mailto) and web-based headers can be entered:
|
Include Transactional Messages | Inserts the list-unsubscribe header into transactional messages. If the checkbox is not visible, the header is included automatically. Contact 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. This helps email clients apply rules and filters.
Setting | Description |
---|---|
List-ID | Customizes the default mailing list ID associated with this group.
|
Customized Email Headers
Adds additional information to the email header. Most header information is added automatically or through other tabs. Input fields here create non-standard header information. 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).
Header Name: Defines the characteristic or parameter to modify.
Header Value: Identifies the value for the parameter.
Header Name | Header Value | Modification |
---|---|---|
| Email address | Sends replies to a defined address. |
| The display name in quotes and the email address in angled brackets Example: "Joe Sample" <example@mywebsite.com> | Shows a specific “from” address. Most email clients display the sender's email address by default if no value is specified. |
| Email address | Sends a copy of the message.
|
| Email address | Sends a blind copy of the message.
|
Preferred Sendout Channel
Defines the channel that Mapp Engage uses to contact someone. These settings are only valid for recipients without a read mode stored in their attributes.
These settings are only relevant for multichannel messages. This option is being removed from Mapp Engage.
Setting | Description |
---|---|
No Preference | No preferred channel. |
Email | Preferred channel is email. Group messages are emailed to recipients without a personal channel preference. |
SMS | Preferred channel is SMS. Group messages are sent via SMS to recipients without a personal channel preference. |
Mobile Push | Preferred channel is Mobile Push. |
Transactional Messages
Configures transactional message like purchase receipts or shipping notifications. Each message includes a unique ID for tracking - the
Setting | Description |
---|---|
Transactional Message Mode: Off | Mapp Engage does not generate or apply a TMID to sendouts in this group.
|
Transactional Message Mode: On | Mapp Engage generates a TMID based on your pattern. |
Transactional Message Mode: Optional | Mapp Engage generates a TMID based on the pattern you define. |
Pattern for the TMID | Defines the expression that generates the TMID, ensuring uniqueness. Each TMID consists of the message ID, the user ID, and a timestamp. This field accepts a maximum of 1000 characters. Example:
|
Personalization | Click the Personalization button to use attribute placeholders in the expression. |
Engage Variables | Click the Engage Variables button to automatically insert content into a message or landing page. |
Leading Content and Closing Content for Email
Defines content added to every email in text or HTML format.
Setting | Description |
---|---|
Leading Content (Text/HTML) | Added at the beginning of emails. |
Closing Content (Text/HTML) | Added at the end of emails. |
Leading Content for Forwarded Messages
Defines standard content inserted when the recipient forwards the message. The content is added during the forwarding process and can include personalization placeholders. For example: <%forwarder.firstname%>
or <%forwarder.lastname%>
Setting | Description |
---|---|
Leading Content (Text) | Input field for the leading text added to every forwarded text message in this group. |
Leading Content (HTML) | Input field for the leading content added to every forwarded HTML message in this group. |