Goal​

To add a unique TMID to every message in a group.

This ID allows you to track every message individually and to confirm that the contact receives and opens the message.

Background Information​

A transactional 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.

This TMID is helpful if you want to track every interaction with a contact, such as in an external system. You can export data about transactional messages with a ​Raw Data Export​. You can then import this data into another system.

The TMID is generated based on a pattern you define in the group settings. This TMID applies only to sendouts in this group.


This procedure is not required for transactional messages that are sent with the Mapp Engage API and your external system generates unique IDs. For more information, see Send Transactional Messages (API)​.

Navigation Path​

  1. In the ​Main Navigation​, click Audience > ​Groups​.
    ⇒  The ​Group Overview​ window opens.
  2. In the ​Actions​ column, click the  symbol.
    ⇒  The ​General Settings​ tab opens.
  3. Open the ​Sendout Options​ tab.
  4. Expand the ​Transactional Messages​ area.

  5. From the ​Transactional Mode​ drop-down list, select the appropriate setting.

    ​On​

    Mapp Engage generates a TMID based on the pattern you define. The TMID is added to every sendout in this group.

    If messages that you send to Mapp Engage with the API contain 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 the messages you send to Mapp Engage with the API contain an externally generated ID, the external ID is not changed or replaced. In this case Mapp Engage does not generate a second 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.

  6. In the ​Pattern for the TMID​ input field, enter the expression for the TMID.
    To use attribute placeholders in the expression, click ​Personalisation​.
    The pattern that you enter here must generate a unique ID for every message. Otherwise, you cannot 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.

  7. Click Save.
    ⇒  The group settings are updated