---
title: "Setup Guides"
slug: "setup-guides-adobe-commerce-magento"
status: "update"
updated: 2026-06-04T08:25:41Z
published: 2026-06-04T08:25:41Z
canonical: "docs.mapp.com/setup-guides-adobe-commerce-magento"
---

> ## 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.

# Setup Guides

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](/v1/docs/adobe-commerce-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](/v1/docs/adobe-commerce-setup-for-a-store-with-multiple-store-views)

[Multi-Store View Support](/v1/docs/multi-store-view-support) – what syncs per Store View and current limitations

---

### 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.

To set up each integration, follow the guide that matches each store's configuration: [one store view](/v1/docs/adobe-commerce-setup-for-a-store-with-one-store-view) or [multiple store views](/v1/docs/adobe-commerce-setup-for-a-store-with-multiple-store-views).

> [!NOTE]
> 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.

[Learn more about mapping](/v1/docs/version-120-mapping)

> To use the Mapp Cloud plugin for Adobe Commerce with Mapp Intelligence, please refer to these pages [Adobe Commerce (Magento) for Mapp Intelligence](/v1/docs/cms-extensions-adobe-commerce-magento).