--- title: "Basics" slug: "mapp-connect-basics" tags: ["Tutorial"] status: "update" updated: 2026-08-05T09:32:31Z published: 2026-08-05T09:36:09Z canonical: "docs.mapp.com/mapp-connect-basics" --- > ## 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. # Basics This article covers basic information about Mapp Connect and its integration possibilities. ## Overview **Navigation Path** *Data Management > Mapp Connect* **What can I do in this window?** - Create a new integration - View all your existing integrations and their statuses - Copy and Edit integrations ## Configuration **Navigation path:** *Data Management > Mapp Connect > Add New Integration* **Available Integrations:** - Generic - use this option for all custom plugins - Third-party integrations: - [Adobe Commerce (Magento)](/v1/docs/adobe-commerce-magento) - [Shopify](/v1/docs/integrations-shopify) - [Shopware](/v1/docs/shopware) - [Zapier](/v1/docs/zapier) ### Overview tab This tab shows all the basic information about the integration. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/image(535).png) **Information & actions on the Overview tab** | Settings | Description | | --- | --- | | **Status** | Connected / Disconnected | | **Disable / Enable** | Disables or enables the integration. | | **Copy** | Creates a copy of the integration | | **Remove** | Removes the integration. | | **Save** | Saves the basic settings of your integration. | | **Basic Information** | - **Integration type**: shows whether the integration is a generic one or a 3rd-party one - **Name**: displays the name of the integration. You can edit the name anytime. - **Description**: This field is optional - **Integration ID** | | **Automation (Whiteboard) settings** | - **Trigger Whiteboard automations** when user mapping attributes change - enable this if you use Whiteboards that react to any attribute changes. This attribute can be changed in the system via your Mapp Connect integration. - **Add incoming (external) event names**. If you use the **Mapp Connect External Event**, this is where you define the events that will be included in the automation. | | **Invalid Mappings** | Displays information on whether all mappings within the integration are valid and a warning if any mapping is invalid. In this case, the main page will display an error as well. Example: ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/30278127-ebba-46c0-b248-e9fbb315596a.png) | | **Add monitoring users** | Adds a Mapp Engage user who will receive notifications and logs related to the mapping. Select the user email address from the drop-down list or perform a search, then click **Add**. | | **Feedback mode** | It lets you choose between **None**, [**Response Queue, and Callback URL**](/v1/docs/enable-feedback-via-response-queue-or-callback-url) for the feedback mode. | ### Mapping tab 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**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/image(536).png) #### Identifiers Mapp Connect supports various user identifiers to facilitate user event processing across different integration types and subtypes. The unique identifiers are available across all supported mapping subtypes, while the non-unique identifier is available exclusively within the “User” subtype. - **Unique Identifiers**: - `userID`: The Contact ID that every Mapp Engage contact gets assigned in the system upon creation. - `email`: The user’s address. - `mobileNumber`: The mobile phone number used as an identifier. - Non-Unique Identifiers (available only for “User” subtype events): - `externalID`: An identifier generated within an external system. In Mapp Engage, it is referred to as `user.identifier`. - Additionally, we offer the possibility of matching users by leveraging custom attributes, which enables flexible targeting and user management. Please visit [User Identifiers in Mapp Connect](/v1/docs/user-identifiers-in-mapp-connect) for more details on how to operate with user identifiers and how to leverage custom attributes for user matching. #### Mapping subtypes | **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 | #### Attribute Types These types of attributes can be assigned to the profile. - **Core** or standard attributes like Email (always required), first name, etc. - **Addon:** An attribute where one profile can have a different value assigned depending on the integration. - **Custom:** Attributes created by the Mapp Engage system user on one system. - **Member:** One attribute can vary for the same user depending on the group (optimal for agencies). - **Related Data:** Attributes pulled from your related data tables. - **None** > [!NOTE] > skipUnsubscribers > > From Fall 2024, you can use the User attribute skipUnsibscribers to check the subscription status of contacts when adding them to a group. When this BOOLEAN parameter is set to TRUE, the check will be run and contacts who have unsubscribed won’t be added back to the group. #### Data Transformations During data import, you can transform the data into a unified format (for example converting to upper or lower case, rounding numbers, or formatting timestamps). For the full list of transformation types and how to apply them, see [Edit Data Transformations](/v1/docs/edit-data-transformations). ### Data Import tab **What can I do in this window?** - Create automated imports that let you sync your contact data from external sources into your Mapp Engage system. - View all your configured imports and monitor the import status **Examples of imports:** - Add contacts to Mapp Engage - Update contact attributes in Mapp Engage - Remove users from Mapp Engage - Send an email (prepared message) with parameters to contacts - Add data to your custom Related Data tables - Add data to predefined Related Data: Transactions, Wishlist, and Abandoned Cart See [Set Up Data Imports](/v1/docs/set-up-data-imports) for more information. ### Import Configuration tab This tab allows you to configure the details of your imports. For details, see our [how-to article](/v1/docs/set-up-data-imports). ## API You can find more details about our API endpoints [here.](/v1/docs/mapp-connect) A unique identifier automatically assigned by Mapp Engage when a new contact is added to the system. - The **Contact ID** cannot be changed or edited. - In some parts of Mapp Cloud, this identifier may also be referred to as **User ID**, but both terms describe the same concept. - You can find the Contact ID by going to *Audience > Contact Management > All Contacts* and checking the ID column. In Mapp Engage, a mobile number serves as a **unique user identifier**, essential for managing contact profiles across various communication channels. Mobile numbers in Mapp Engage must follow the international format, starting with a "+" symbol followed by the country code and the number (e.g., +49 123 455 679). ## Related - [How-Tos](/mapp-connect-how-tos.md)