- 2 Minutes to read
- Print
- DarkLight
Single vs. Group Sendouts of Prepared Messages
- 2 Minutes to read
- Print
- DarkLight
A prepared message is a saved message that you have assigned to a group. Mapp Engage assigns a message ID (MID) to each prepared message.
You can use one prepared message for multiple sendouts. You can send a prepared message either as a single message or as a group message.
Sendout Method | Single Message | Group Message |
---|---|---|
Sendout in the Message area | N/A | You can manually send a group message in the Prepared Message Overview window with the action Copy & Send. |
Time-based automation | Example: birthday emails | |
Event-based automation | Example: transactional messages | |
System Messages | System messages are always single messages. |
How Mapp Engage Handles Group and Single Messages
Mapp Engage has a different way of sending a tracking a single message versus a group message.
The following table provides an overview of how Mapp Engage handles single and group sendouts of prepared messages.
Mapp Engage Handling of Single and Group Messages
Single Message | Group Message | |
---|---|---|
Message ID | All single sendouts of a prepared message share one MID. Every message sendout retains the same MID as the prepared message. | Mapp Engage assigns a new, unique MID to each group sendout of the prepared message. In the background, Mapp Engage records the original MID of the prepared message. This information enables Mapp Engage to recognize related sendouts of the prepared message. |
Statistics | All single sendouts are evaluated together in the Statistics. One set of statistics is generated for all single messages that are sent of one prepared message. | All group sendouts of a prepared are evaluated separately in the Statistics. Each sendout has a separate set of statistics. |
Outbox | Only one sendout appears in the Outbox. If you change the content of a prepared message you only use for single sendouts, the previous sendout content is lost. You can store previous versions of single messages outside of Mapp Engage. | Each group sendout is stored separately. Each sendout is visible in the Outbox. No message content is deleted. This method ensures that you still have a record of every group sendout. |
Message Limitation | Not considered in message limitation. | Considered in message limitation. |
Example: Birthday Email (Single) vs. Holiday Series (Group)
Daily Birthday Email (Single Message Sendout) | Series of 5 Holiday Emails Sent with an Automation (Group Message Sendout) | |
---|---|---|
Message ID Handling | All birthday emails share one message ID 12345. | The holiday emails have the message IDs 54321, 54322, 54323, 54324, 54245. |
Statistics | The statistics shows a combined set of statistics for all the birthday emails. No statistics are available each birthday message separately. | Statistics are calculated separately for each of the 5 holiday emails. No statistics are calculated for the series as a whole. |
Outbox | Only one birthday sendout appears in the Outbox. If you change the content of the birthday message, Mapp Engage does not save a copy of the old content. | Each of the 5 holiday emails appears separately in the outbox. You can still view the content of all 5 emails as they were sent. |