Multi-Store View support lets a single Adobe Commerce installation serve multiple markets through Mapp Engage, with localized transactional messaging and product data per Store View. It is available with version 1.5.2 and later of the Mapp Cloud Adobe Commerce (Magento) plugin. Version 1.5.4 or later is recommended, as it adds support for the full store hierarchy and resolves several synchronization issues in multi-market setups.
What it does
Store Views in Adobe Commerce typically represent the language or regional variants of one website. With Multi-Store View support, each Store View syncs its own localized data to Mapp Engage independently, so campaigns, recommendations, and transactional messages reach each shopper in the correct language and regional context – without duplicating your product catalogue.
What syncs per Store View
Localized product text: product names and descriptions are synced per Store View, so emails and automations use the correct language.
Currency-specific pricing: product prices are synced per ISO currency code.
Store View–specific groups and messages: each Store View maps to its own Engage groups and localized prepared messages.
Store hierarchy
As of plugin version 1.5.4, the plugin supports the Adobe Commerce store hierarchy down to Store View level (website > store > store view). Product updates made at Store View level are synchronized for the Store View they belong to.
Prerequisites
Version 1.5.2 or later of the Mapp Cloud Adobe Commerce (Magento) plugin.
Multiple Store Views configured in your Adobe Commerce installation.
An active Adobe Commerce integration in Mapp Engage.
Limitations
Adobe Commerce does not support back-in-stock campaigns for multi-view stores.
Warning
Product prices are stored per ISO currency code in the Mapp Engage product data model. Two Store Views that use the same currency, for example a French and a German Store View both using EUR, therefore share the same price for a given product. This is a limitation of the Engage data model rather than of the plugin, and it still applies in version 1.5.4. Localized text fields such as names and descriptions are not affected.
Set it up
For the full configuration procedure – creating per–Store View groups, preparing localized messages, and mapping data – see Set up a Store with Multiple Store Views