--- title: "Mapping" slug: "connect-mapping" updated: 2026-01-20T12:47:52Z published: 2026-01-20T12:47:52Z --- > ## 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. # Mapping ## General Information Mapping is matching data from API calls to Mapp Engage data. For example, you can save contact attributes, email parameters, order history, etc., from your external app to the selected destination in Mapp Engage. **What can I do in this tab?** - View existing mappings - activate and deactivate mappings - Add and edit mappings - Import and export mappings ## Mapping Subtypes Each mapping contains a list of relevant default destinations. You can add user data mapping to every mapping type. For example, when you send an email, you can add user attributes to the user profile within the same API call. > [!NOTE] > The Generic integration only supports **import**. | **Mapping Subtype** | **Integration type** | | --- | --- | | **Generic** | **Magento (Adobe Commerce)** | **Shopify** | **Shopware** | **Zapier** | | **User** Maps source data into a user profile using these attribute types: Core, Addon, Custom, Member, Related Data, or None. | Predefined | Predefined | Predefined | Predefined | Predefined | | **Email** This allows you to send an email (prepared message) and optionally map source data as an email parameter used in the prepared message template. | Optional | Predefined | Predefined | Predefined | Predefined | | **Product** Maps product catalog items in Mapp Engage. For more information, see [Product Catalog](https://docs.mapp.com/docs/ecommerce-product-catalog). | Optional | Predefined | Predefined | Optional | unsupported | | **Transaction** Maps transactions, e.g. order details, with the default structure of [System Transactions](https://docs.mapp.com/docs/system-transactions). | Optional | Predefined | Predefined | Predefined | Predefined | | **Transaction bulk** Imports a file with multiple transactions/orders. | Optional | Predefined | Predefined | unsupported | unsupported | | **Abandoned Cart** This function maps source data to the default structure of the Abandoned Cart eCommerce table. For more information, see [Product Catalog](https://docs.mapp.com/docs/ecommerce-product-catalog). | Optional | Predefined | Predefined | unsupported | unsupported | | **Abandoned Browse** This function maps source data to the default structure of the Abandoned Browse eCommerce table. For more information, see [Product Catalog](https://docs.mapp.com/docs/ecommerce-product-catalog). | Optional | Predefined | Predefined | Unsupported | Unsupported | | **Wishlist** This function maps source data to the default structure of the Wishlist eCommerce table. For more information, see [Product Catalog](https://docs.mapp.com/docs/ecommerce-product-catalog). | Optional | Predefined | Optional | unsupported | unsupported | | **Location** This option allows you to map source location data to the default location structure in the metadata service for geofence functionality. For more information about geofence functionality, see [Location Management](https://docs.mapp.com/docs/location-management). | Optional | unsupported | Predefined | unsupported | unsupported | | **Automation** This mapping is used to trigger whiteboard automation in Mapp Engage. See [Whiteboards](https://docs.mapp.com/docs/whiteboards). | Optional | unsupported | Predefined | Optional | unsupported | | **Coupon** For more information, see [Coupon Manager](https://docs.mapp.com/docs/content-coupon-manager) | Optional | Predefined | Optional | unsupported | Predefined | | **Related Data** This is based on the related data tables and allows for very flexible data use. For instance, in an Abandoned Cart scenario, this mapping allows for storing product information per cart instead of per product in an eCommerce table. Mapping for the Related Data subtype is optional. You can add the Related Data subtype as a Source and choose the Related Data table you want to map to as a destination. | Optional | Predefined | Optional | Optional | Predefined | | **Recommended product** For more information, see [Product Recommendations in Mapp Engage](https://docs.mapp.com/docs/how-to-set-up-product-recommendations-in-mapp-engage) | Optional | Predefined | Optional | Optional | Predefined | | **SMS** It allows you to send an SMS (prepared message) to a contact using their email or mobile number as an identifier. | Optional | unsupported | Predefined | unsupported | unsupported | | **Push** This allows you to send a push notification (prepared message) to the contact using email as an identifier. It requires adding the mobile app ID in the API call. | Optional | unsupported | Predefined | unsupported | unsupported | | **Web Push** Web Push browser notifications. | Optional | unsupported | Optional | unsupported | Predefined | | **Custom** Use for custom mappings that are unsupported within the system. | Optional | unsupported | Optional | Optional | unsupported | | **Newsletter** | unsupported | Predefined | unsupported | Predefined | unsupported | > [!NOTE] > GroupPK Mapping > > If want to use **group**in your user mapping, for example when adding contacts to a newsletter subscription, you can either use **group**which is already mapped to **groupPK**(primary key, or ID) or you can use **groupPK**but must map it to **group**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/Screenshot 2024-09-17 at 12.27.21.png) ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/image (1)(1).png) ### Example ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/image(536).png)