Transactional Messages

  • 2 minute(s) read
Prev Next

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.

Available Sendout Methods

To send a transactional message, first create a prepared message in Mapp Engage. Then select one of the supported methods:

1. API

1.1. API: messageSendTransactional

  • Use case: Your external system generates the TMID.

  • Settings: Set Transactional Message Mode to Off in group settings to avoid duplicate TMID generation.

  • API Documentation: /messagesensndtraactional

1.2. API: messageSendSingle

  • Use case: Your external system does not generate TMIDs.

  • Settings: Set Transactional Message Mode to On. Define a pattern to auto-generate unique TMIDs.

  • API Documentation: /messagesendsingle

1.3. API: /message/sendTransactionalWithEventDetails

  • Use case: Sends a previously prepared message and includes transaction-specific data (e.g., purchase confirmation).

  • Benefit: Combines the delivery of a transactional message with dynamic content based on the event context.

  • API Documentation:  /messagesendtransactionalwitheventdetails

See Sending Transactional Messages (API) for details.

5. Whiteboard Automations

  • Use case: Trigger messages based on contact activity or external system events.

  • Settings: Set Transactional Message Mode to On and define a TMID generation pattern.

  • Automation Guide: Send Transactional Messages (Whiteboards)

For configuration steps, see: Add a TMID to Messages.

Tracking and Export

Mapp Engage offers the following possibilities to track transactional messages.

Related articles