Using EXM in multisite environments

Current version: 10.4

When you use the Email Experience Manager in a multisite environment, it is important to have separate Email manager roots for each site. A manager root contains all the settings that control the user experience for a specific site. While the initial Email manager root is added to the Sitecore content tree when you open the Email Experience Manager from the Sitecore Launchpad, you can create additional manager roots manually.

The Email manager root serves as an email "domain" thus enabling you to have separate email campaign opt-out lists, templates, or analytics for each site. To create a new manager root, in the Content Editor, navigate to sitecore/Content/<tenant>/<site>, right-click <site>, and select Insert, Insert from template. On the Browse tab, in the Template field, navigate to Templates/Branches/System/Email and select Manager Root. In the example below, Habitat Home and Habitat Home Basic each have their own email manager root.

Content Editor showing multiple email manager roots.

Manager roots that relate to different sites can be located in different places in the Content tree. Furthermore, a user can have access to several manager roots. Use standard Sitecore security applications to grant permissions to specific manager roots. By default, EXM searches for the manager root under the item defined in the Default Root Parent setting of the /sitecore/System/Settings/Email item. For this reason, email manager roots for each site are often created in a folder beneath the tenant.

Global settings Default Root Parent item for the email campaign.

The location of manager roots is defined in the /sitecore/System/Settings/Email/System/Root List item, which is updated automatically.

When multiple email manager roots are defined, you access them from the dashboard and can select the specific manager root for which you want to view reports.

Email Experience Manager dashboard showing how to switch between multiple manager roots.

Do you have some feedback for us?

If you have suggestions for improving this article,