Overview
Transactional messages in Mapp Engage are emails triggered by external events, such as a purchase or registration, typically initiated by a contact. These messages differ from marketing emails in that they often convey important information that the customer expects, such as receipts or shipping confirmations. Each transactional message includes a unique identifier called a Transactional Message ID (TMID), which allows individual tracking.
Key Characteristics
Unique Tracking: Every transactional message includes a TMID, allowing per-message tracking.
Message Types: These can be sent as single or group messages, but they are typically used as single messages.
Sendout Flexibility: Can be triggered via API or automations.
Deliverability & Branding:
Full Mapp Engage deliverability features apply.
Supports personalizations and branded message templates.
Exclusion from List-Unsubscribe: Transactional messages can omit the list-unsubscribe header.
Important Note on Consent
Adding a TMID to a message technically classifies it as a transactional message in Mapp Engage. However, this does not override the legal or regulatory need for recipient consent:
Depending on your local legal requirements, you may send informational transactional messages (e.g., order confirmations) without marketing consent.
You must not use TMIDs to bypass consent for purely promotional content.
Always ensure your message content aligns with the contact’s permissions.
Note
If a transactional message is sent to a contact who is not already in the group, Mapp Engage automatically adds the contact to the group.
Sending Transactional Messages
To send a transactional message, first create a prepared message, then choose one of two methods:
API – trigger the message from an external system. See Sending Transactional Messages (API).
Whiteboard automation – trigger the message from contact activity without an external system. See Sending Transactional Messages (Whiteboards).
Both methods require a TMID pattern configured at group level. See Set Up a TMID for Transactional Messages.
Tracking and Export
Mapp Engage offers the following possibilities to track transactional messages.
Message History: View individual contact activity. See Message History (window).
Statistics: View message-level performance. See Single Message Statistics Overview.
Raw Data Export: Export data for CRM or BI tools. See Raw Data Exports.
API Polling: Retrieve response data via
asyncPoll. See Poll API Docs.