--- title: "Injection of Transactional Data into Mapp Engage" slug: "injection-of-transactional-data-into-mapp-engage" updated: 2026-01-23T15:27:06Z published: 2026-01-23T15:27:06Z canonical: "docs.mapp.com/injection-of-transactional-data-into-mapp-engage" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Injection of Transactional Data into Mapp Engage ## Overview Injection of transactional data allows you to store order and purchase information in Mapp Engage. The injected data is saved as **System Transactions** and can be used for segmentation, automations, and personalization. Transactional data can be stored independently or stored and sent together with a transactional email, for example, for order confirmations or shipping notifications. --- ## Navigation Path *Administration > E-commerce > System Transactions* --- ## Injection Behavior - **Multiple injection methods**: transactional data can be injected via Mapp Connect integrations, automated imports, manual uploads, or REST API calls. - **Optional email sendout**: data can be stored without sending a message or stored and sent together with a transactional email. - **Contact-based storage**: transactions are stored only for existing contacts, unless using Mapp Connect, which can automatically create contacts. - **Reusable data**: stored transactions remain available for segmentation, automations, and message personalization. --- ## Injection Methods ### Mapp Connect Integration Mapp Connect supports automatic injection of transactional data from connected e-commerce platforms, including: - Magento (Adobe Commerce) - Shopware - Shopify - WooCommerce (via Zapier) - Other platforms are integrated via Zapier using an order event When transactional data is injected via Mapp Connect, contacts that do not yet exist in the system are created automatically. For details, see [Mapp Connect Basics](/v1/docs/mapp-connect-basics). --- ### Automated Imports Transactional data can be imported using scheduled automated jobs. These jobs are configured in the Whiteboard interface and allow recurring imports without manual intervention. For details, see [Import/Export](/v1/docs/importexport). --- ### Manual Import Transactional data can also be imported manually. 1. Navigate to *Administration > E-commerce > System Transactions* 2. Use the provided sample file to upload transaction records For details, see [Manual Import & Search of eCommerce Data](/v1/docs/manual-import-search-of-ecommerce-data). --- ### API-Based Data Injection Transactional data can be injected via the REST API. Two different scenarios are supported. --- #### Storing Transactional Data Without Email Sendout Transactional data can be stored without sending a message. **Behavior** - All required fields must be provided - The `userId` must be an email address - Importing transactions does **not** trigger the **New Transaction Registered** event in Whiteboard **REST API reference** Endpoint: `POST /rest/transactional/createrecord` For details, see this endpoint in the [API documentation](https://docs.mapp.com/apidocs/relateddatacreaterecord). **Example request** ```json POST /rest/transactional/createrecord {  "userId": "user@example.com",  "transactionId": "1234567890",  "transactionDate": "2023-01-01T12:00:00Z",  "orderTotal": 150.00 } ``` This method is typically used when transactional data is required for segmentation or later automation, but no immediate message should be sent. --- #### Storing Transactional Data With Email Sendout Transactional data can be stored, and a transactional email can be sent in the same request. **REST API reference** Endpoint: `POST /rest/transactional/sendTransactionalWithEventDetails` For details, see this endpoint in the [API documentation](https://docs.mapp.com/apidocs/messagesendtransactionalwitheventdetails). **Example request** ```json POST /rest/transactional/sendTransactionalWithEventDetails {  "userId": "user@example.com",  "transactionId": "1234567890",  "transactionDate": "2023-01-01T12:00:00Z",  "orderTotal": 150.00,  "emailContent": "

Order Confirmation

" } ``` This approach is commonly used for order confirmations, shipping notifications, or payment confirmations. --- ## Transactional Email Usage When transactional data is injected alongside an email sendout, it becomes available in the email template. - Order-level data is accessed via parameters such as `parameter.orderTotal` - Product-level data is accessed via a loop over the transaction details - Conditional content can be rendered when optional values are present --- ## Example Transactional Email Template ```xml      

Dear <%user.firstname%> <%user.lastname%>,

   

Thank you for shopping with us! Please find your order details below:

                                   
         

Billing Information

         

<%parameter.billingAddress%>

       		          

Shipping Information

         

<%parameter.shippingAddress%>

       
   <%ForEach var="product" items="${transaction_details}"%>                                      
                                                 

<%${product['brand']}%>

           

<%${product['productName']}%>

           

             Quantity: <%${product['productQuantity']}%>,              Price: <%${product['productPrice']}%>            

         
   <%/ForEach%>    

Total: <%parameter.orderTotal%> <%parameter.currency%>

   

Best regards,
The [Your Company Name] Team

  ``` The recipient receives a personalized transactional email displaying billing and shipping information, a list of purchased products, and the total order value. ## Related - [Set Up Data Imports](/set-up-data-imports.md) - [Set Up a Mapp Connect Automation Event](/set-up-a-mapp-connect-automation-event.md) - [Getting Started with Mapp Connect and a Custom Plugin](/getting-started-with-mapp-connect-and-a-custom-plugin.md) - [Data Import](/data-import.md)