Send Transactional Messages (Automations)

Scenario

Use this to send an automated message to a contact after a contact activity. Each message has a unique, trackable transactional message ID (TMID). This TMID allows you to track whether the contact opens or clicks the message.

This scenario uses automations to set up simple transactional messages in response to various contact interactions.

If you have an online shop system or CRM system, send transactional messages with the Mapp Engage API.

For more information, see ​Send Transactional Messages (API)​.

Advantages

• Respond immediately and automatically to almost any type of contact activity.

• Add a unique TMID to every sendout for contact messages that are individually identifiable.

• Analyze the success of transactional messages in​ Statistics​.

• Export raw data about transactional messages and analyze this data in an external tool.

• Automatically insert information from the event or conversion into the transactional message.

Background Information​

You can use ​Automations​ to send single messages in response to any type of contact activity. Add a TMID to these sendouts to make every message individually trackable. This TMID turns any automated sendout into a transactional message.

Prerequisites 

1. ​​Set the ​Transactional Message Mode​ in the group settings to ​On​.

2. Create a pattern that generates a unique TMID for every sendout.
   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)}%>

   For instructions, see ​Add a TMID to Messages​.

3. Create the transactional message. Save the message as a prepared message.
   For instructions, see ​Save Draft as Prepared Message​.
   You can automatically insert information from the event or conversion into the transactional message. To do so, you add a placeholder to the message. The placeholder can be inserted in the message body or subject line. For more information, see ​Add Event Data to a Prepared Message​.

Procedure​

1. In the ​Automation​ area, create a whiteboard.

2. Drag one ​Event​ module and one ​Event-based job​ module onto the whiteboard.

3. Drag and drop between the  symbols to connect the modules.

4. Define the module settings. Refer to the following tables:
   Tab. : Event Module

   Field	Entry
   Event	This event triggers the sendout of transactional messages. For example, this event could be one of the following. ​Conversion Registered (C)​ ​Profile Data Changed (New) (C)​ ​Subscribed to Group (C)​ ​Unsubscribed From Group (C)​ For a complete list of events, see ​All Available Events​.

   
   Tab. : Event-based Job Module

   Field	Entry
   Job	​Send Prepared Message to Contact (C)​
   Message	Select the prepared message that you want to use for transactional messages.
   Contact	Select the ​Use Event Parameter​ check box.
   Parameter	You can use ​Parameters​ to add information from the conversion to the transactional message. For more information, see ​Add Event Data to a Prepared Message​.

5. Click Next.
   ⇒  The ​Whiteboard​ wizard opens to step two.

6. Define the desired time frame and notifications.

7. Click ​Activate​ to immediately activate the whiteboard. The system only executes active whiteboards.
   ⇒  The whiteboard is saved and activated. The automation has the status ​Running​ when the start date is immediate and the status ​Scheduled​ when the start date is in the future.

Track Transactional Messages​

Mapp Engage offers the following possibilities to track transactional messages.

• View whether an individual contact received and opened a transactional message in the ​Message History​ window. For more information, see ​Message History (window)​.

• View a summary of the statistics for all sendouts of the prepared message in the ​Statistics​ area. For more information, see ​Single Message Statistics Overview (window)​.

• Export data about transactional messages with a ​Raw Data Export​. For more information, see ​Raw Data Exports​. You can upload this data in your CRM or BI tool for further analysis.

• Retrieve information from the Mapp Engage result queue with the API call asynPoll (see http://developers.mapp.com/#async). Putting response data into the response queue needs to be set up for your Mapp Engage system by a Mapp administrator. It option is not active by default for Mapp Engage standalone systems. It is active by default for CIM/Mapp Engage integrated systems.

Related Topics​

​Transactional Messages​
​Add a TMID to Messages