The integration of Adobe Commerce with Mapp Engage depends on the architecture of your shop. Choose the scenario that matches your setup:
Choose Your Setup Scenario
Single Store View
You run one website, one store, and exactly one store view.
One integration in Mapp Engage is sufficient.
By default, three groups are created (e.g. magento_customer, magento_subscriber, magento_guest).
Mapping, synchronization, and message setup are handled in a single instance.
Setup for a store with one store view
Multiple Store Views
You run one website with multiple store views – for example, different language versions of the same shop.
One integration in Mapp Engage is sufficient.
Separate groups are created in Engage for each store view (e.g. IT, DE).
Templates and messages are managed per store view.
Setup for a store with multiple store views
Multiple Stores
You run several independent stores (e.g., with different domains or product catalogs).
If the stores share the same product catalog and attributes, one integration is sufficient.
If the stores use different catalogs or attributes, create a separate integration in Engage for each store.
There are no limitations on the number of Adobe Commerce plugin integrations within one Mapp Engage instance.
Mapping
Mapping data (e.g. products, transactions, customer attributes) is a central part of all setups.
To use the Mapp Cloud plugin for Adobe Commerce with Mapp Intelligence, please refer to these pages Adobe Commerce (Magento) for Mapp Intelligence.