- 3 Minutes to read
- Print
- DarkLight
Injection of Transactional Data into Mapp Engage
- 3 Minutes to read
- Print
- DarkLight
Integrating Transactional Data with Mapp Engage
Mapp Engage supports the injection of transactional data through various methods, including the use of Mapp Connect integration. This feature allows you to import order data from multiple e-commerce platforms and store it within Mapp Engage, facilitating a seamless marketing and customer engagement process.
Mapp Connect Integration
Currently, Mapp Connect supports the direct saving of transactional data from the following platforms:
WooCommerce (via Zapier)
Any other e-commerce platform that is integrated with Zapier using the "Order Event."
For detailed instructions on configuring Mapp Connect, please refer to Mapp Connect Documentation.
Custom Integration
If you are using a custom plugin, Mapp Engage also supports integration through custom setups.
For more information, see the relevant Custom Plugin Integration Guide.
Automated Imports
Transactional data can also be imported via automated jobs. You can schedule these imports directly within the Mapp Engage Whiteboard interface to streamline the process.
The "user_id" field must be an email address for all transactional data imports. Importing transactions does not trigger the "New Transaction Registered" event on Whiteboard.
Manual Import
Navigate to Administration > E-commerce > System Transactions
Use the provided sample file to import transactions manually.
For more information, consult the Manual Import Guide.
API Data injection
Storing Data Without Email Sendout
Transactional data can be stored in Mapp Engage without sending an email. All required fields must be provided to save the record.
Example API call:
POST /rest/transactional/createrecord
{
"userId": "user@example.com",
"transactionId": "1234567890",
"transactionDate": "2023-01-01T12:00:00Z",
"orderTotal": 150.00
}
For more information, please refer to the API documentation.
Storing Data with Email Sendout
Mapp Engage also allows you to send transactional emails (e.g., order confirmation emails) while storing the transaction data simultaneously. This is done through the sendTransactionalWithEventDetails REST call.
Example API call:
POST /rest/transactional/sendTransactionalWithEventDetails
{
"userId": "user@example.com",
"transactionId": "1234567890",
"transactionDate": "2023-01-01T12:00:00Z",
"orderTotal": 150.00,
"emailContent": "<h1>Order Confirmation</h1>"
}
Transactions are stored only for users who already exist in the designated Mapp Engage instance.
Example of a personalized prepared message
<transactionalEmail>
<recipient>
<email><%user.email%></email>
</recipient>
<content>
<html>
<![CDATA[
<html>
<body>
<h1>Order Confirmation</h1>
<p>Thank you for your order, <%user.firstName%>!</p>
<p>Order ID: <%order.orderId%></p>
<p>Order Date: <%order.orderDate%></p>
<table>
<tr>
<th>Product</th>
<th>Quantity</th>
<th>Price</th>
</tr>
<%order.items%>
<tr>
<td><%item.productName%></td>
<td><%item.quantity%></td>
<td><%item.price%></td>
</tr>
<%/order.items%>
</table>
<p><strong>Total:</strong> <%order.total%></p>
<p>Payment Method: <%paymentInfo.method%></p>
<p>Shipping Address:</p>
<p><%shippingInfo.address%></p>
<p>If you have any questions, feel free to contact us at <%support.email%>.</p>
<p>Thank you for shopping with us!</p>
</body>
</html>
]]>
</html>
</content>
<subject>Your Order Confirmation - Order <%order.orderId%></subject>
</transactionalEmail>
Mapp Acquire Transaction Event
Mapp Acquire enables the storage of order data in the Mapp Engage Transactional Related Data table. To set this up, ensure that you have properly configured the Google E-commerce Data Layer in your Google Tag Manager.
Storing data works only for users matched between Mapp Acquire and Mapp Engage. Other scripts might block standard setup and a custom script is required.