--- title: "Set up a Store with Multiple Store Views" slug: "adobe-commerce-setup-for-a-store-with-multiple-store-views" updated: 2026-06-04T08:26:07Z published: 2026-06-04T08:26:07Z canonical: "docs.mapp.com/adobe-commerce-setup-for-a-store-with-multiple-store-views" --- > ## 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. # Set up a Store with Multiple Store Views ## Goal Set up Mapp Engage and Adobe Commerce so one website can send localized transactional messages for multiple Store Views (for example, English, Italian, German). --- ## Background Information / Prerequisites - Store Views are typically used for languages or regional differences. - You will create dedicated Groups and Messages per Store View in Mapp Engage, then connect and map data via Mapp Connect, and finally assign groups and messages in Adobe Commerce. --- ## Procedure ### A) Create Groups in Mapp Engage 1. On Mapp Engage, navigate to *Create New > Group* and for each Store View, create 3 groups: Example for Italian: - For customers (e.g. `magento_customer_<LANG>`) - For subscribers (e.g. `magento_subscriber_<LANG>`) - For guests (e.g. `magento_guest_<LANG>`) - `magento_customer_IT` - `magento_subscriber_IT` - `magento_guest_IT` > [!TIP] > **Tip:** Use clear, language-based naming to avoid mixing up groups later. --- ### B) Prepare Messages in Mapp Engage 1. In *Create New > Message > Email Message > HTML Email*, create a separate set of transactional messages (prepared Email messages) per Store View (for example, English, Italian, German). 2. Save each email as a **Prepared Message** for later selection in Adobe Commerce. > [!TIP] > **Tip**: Keep message names organized by language. --- ### C) Create Integration in Mapp Connect 1. Go to *Data Management > Mapp Connect*. 2. Click **Add New Integration**. 3. Select **Magento** as the integration type. 4. Enter the name of the connection and click **Create**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/0a3e09f0-8223-42e0-9ef6-77f90592a04e.png) 5. In *Integration Settings > Overview*, optionally add a description. 6. (Optional) Enable the Whiteboard trigger for mapping attribute changes. 7. Copy the Secret Key and save it for later authentication. 8. Click **Save**. > [!NOTE] > **Note**: The secret key is only visible once. Save it immediately. --- ### D) Configure Mapping in Mapp Connect Default import types and standard attributes for Adobe Commerce are pre-added. For the full list of default mapping types and what each one does, see [Mapping](/v1/docs/version-120-mapping). Any custom mapping needs to be added to the configuration. This can be done via an import or manually: 1. Go to *Data Management > Mapp Connect*. 2. Open the Adobe Commerce integration of your choice. 3. Click the Mapping tab. 4. Import your mapping, or add custom mapping manually as needed. For more information, see [Mapping](/v1/docs/mapping). --- ### E) Configure general settings in Adobe Commerce 1. In Adobe Commerce Admin, go to *Store > Configuration* > *Mapp Cloud > Mapp Engage (Connect) - General*. This page opens with the Scope “Default Config”. 2. Configure general settings, such as choosing the environment or adding specific preferences. 3. Enable the module and **Save**. | Setting | Details | | --- | --- | | **Module Enable** | Enables or disables the module. | | **Mapp Connect API URL** | Sets the API endpoint used by MapConnect. - EU L3 cluster: https://jamie .**g**.shortest-route.com/charon/api/v1/ - EMC cluster: https://jamie .**h**.shortest-route.com/charon/api/v1/ - US L3 cluster: https://jamie .**a**.shortest-route.com/charon/api/v1/ - EMC-US cluster: https://jamie .**c**.shortest-route.com/charon/api/v1/ - Specified: This option opens the **Mapp Connect custom API URL** input field. For more information, see [Mapp Engage Clusters and Time Zones](/v1/docs/mapp-engage-clusters-and-time-zones). | | **Mapp Connect custom API URL** | Specifies a custom API endpoint for Mapp Connect, if needed. | **Example configuration** ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/52bf5d51-3ff8-47f4-840d-d552ec3143e6.png) --- ### F) Configure the integration in Adobe Commerce 1. Set **Integration Enable** to “Yes”. 2. Enter the Integration ID and Integration Secret. 3. Click **Save**. 4. Confirm Connection Status shows “Connection Successful“. 5. Click **Save Config**. | Setting | Details | | --- | --- | | **Integration Enable** | Activates the connection to Mapp Engage. | | **Integration ID** | Unique identifier of the integration created in Mapp Connect. | | **Integration Secret** | Secret key generated during integration setup in Mapp Connect. | | **Connection Status** | Displays the current connection status, for example, “Connection Successful”. | **Example configuration** ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/8c0c504b-58e6-4377-ae33-5a2605191726.png) --- ### G) Export Connection Configuration Configure synchronization for products, customers, transactions, and newsletters, as required for your setup. > [!NOTE] > **Note**: > > Adobe Commerce sends only real-time data to Mapp Engage. Historical data is not transferred automatically. > > To add historical data, export CSVs from Adobe Commerce, then import them to Engage via Mapp Connect (FTP/SFTP). | **Setting** | **Details** | | --- | --- | | **Synchronization Method** | - **DB Trigger**: Recommended option. Sends requests multiple times if a failure occurs (for example, connection issues). When selected, the *Max Newsletter Request Retry Count* option appears at the bottom of this section. The default retry count is 10, but you can enter a custom number. - **Legacy**: Default option. Failed requests are not resent. | | **Enable Product Synchronization** | Defines synchronization preferences for products. If enabled, products created in Adobe Commerce appear in the product catalog in Mapp Engage. | | **Add Cached Product URLs to Sync** | - **Yes**: Recommended. Prevents accidental syncing of large images. Adobe Commerce resizes catalog images and caches them, ensuring that only necessary sizes are loaded. If a resized image is missing, placeholders are used. - **No**: Disables cached image usage. If you change this option, run a full product sync with the `mapp:export:products` command to update all products. | | **Generate Resized Product Images during Sync** | Appears when *Add Cached Product URLs to Sync* is set to “Yes”. Ensures all cached images exist during synchronization. May reduce performance, as two resized files are generated per product if they do not already exist. | | **Enable Customer Synchronization** | Defines synchronization preferences for contacts. If enabled, contacts created in Adobe Commerce are mirrored in Mapp Engage. | | **Enable Sales Transaction Synchronization** | Defines synchronization preferences for transactions. If enabled, transactions registered in Adobe Commerce are mirrored in Mapp Engage. | | **Newsletter Synchronization** | Defines synchronization preferences for newsletters. If enabled, newsletter sign-ups are added to the defined Mapp Engage group. | | **Newsletter Double Opt-in** | Enables or disables double opt-in for newsletters. See [Set up Double Opt-in with the Email Channel](/v1/docs/set-up-double-opt-in-with-the-email-channel) for details. | | **Max Newsletter Request Retry Count** | Appears when *Synchronization Method* is set to “DB Trigger”. Defines how many times failed requests are retried. The default is 10, but you can uncheck *Use system value* and enter a custom number. | | **Use system value** | If checked, the plugin uses the Adobe Commerce system value, even if another option is selected. | **Example configuration** ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/5debaba1-5222-4f73-8652-c9b3cee93c0f.png) --- ### H) Set up store views and localized product attributes **Store Views** 1. Go to *Stores > Settings > All Stores*. 2. Create a **Store View** for each language. 3. Set the locale at *Stores > Settings > Configuration > General > Locale Options*. **Localized product attributes** 1. Go to *Catalog > Products* and open the product. 2. Use the **Store View** selector to switch to the desired view. 3. For attributes such as Name, Description, Short Description, Meta Title, Meta Description, and URL Key: - Clear **Use Default Value**. - Enter localized content. 4. Save the product. 5. In Engage, open *Administration > eCommerce > Product Catalog* to confirm localized data is updated. For details, see the following documentation: - [Product Catalog](/v1/docs/ecommerce-product-catalog)ecommerce-product-catalog - [API Endpoints](https://docs.mapp.com/apidocs/api-endpoints) --- ### I) Assign Groups in Adobe Commerce 1. In the configuration, select the **Mapp Engage Groups** created in Engage. These are the defaults for **Scope: Default Config** and appear only after the plugin is set up and the connection is active. **Example configuration** ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/b1df2816-7271-448a-91d7-0c0b97bfb9a6.png) 2. Click the **Save Config**. 3. To adjust groups for other Store Views, change the **Scope** and select the required group. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/240cbd78-591f-4bdc-a81b-78f19c9ab599.png) 4. Click **Save Config**. > [!NOTE] > Note: > > Only adjust the Customer Group per Store View. The Subscribers and Guests groups remain the same across all Store Views. --- ### J) Configure Messages in Adobe Commerce 1. Go to *Stores > Configuration >* *Mapp Cloud > Mapp Engage (Connect) - Emails.* 2. For each Store View, assign the localized prepared messages you created in Engage. 3. Save config. ## Related - [Managing Groups](/create-a-new-group.md) - [Create an Integration](/create-an-integration.md) - [Adobe Commerce Mapping](/version-120-mapping.md) - [eCommerce: Product Catalog](/ecommerce-product-catalog.md)