Alert Manager only supports one user as the notification recipient as a standard Marketing Cloud feature. However, for operational purposes, you may need to share alerts with multiple administrators or a team.
If this is the case, consider the following workarounds:
Use a Mailing List (ML): Create a mailing list that includes all required contacts. Set this ML's email address as the recipient in Alert Manager. Marketing Cloud will recognize the ML as a single address and send the notification.
Use Email Forwarding: Configure the single recipient's email client (e.g., Outlook, Gmail) or mail server to automatically forward the received alert email to other contacts.
When setting an ML as the recipient, you must pay attention to the following two points to ensure reliable delivery from Marketing Cloud.
These considerations apply not only to Alert Manager but also to all system notifications from Marketing Cloud (e.g., Trust, Automation Studio notifications) and general email sends from Email Studio.
1. Allowing Emails from External Domains
Depending on your ML's configuration, it may be set to reject emails from external domains by default. If MCE notifications are treated as external, you must configure the ML to allow them.
Therefore, before configuring the ML in Alert Manager, you should send a test email from a separate, external email address (e.g., a personal webmail account) to the ML. Verify that all members receive the email correctly. Please consult your organization's email administrator for details on how to configure this.
2. Regular Auditing of ML Members
If the ML includes inactive email addresses (e.g., from former employees), deliveries to those addresses will result in a Hard Bounce (a permanent delivery error).
When this bounce is returned to MCE, MCE's system may change the status of the entire ML address to Bounced or Held (based on specific criteria). This will stop all future notifications from being delivered.
If your ML address status becomes 'Held', consider the following actions:
Change the Mailing List (ML) Address: Change to a different ML email address to bypass the 'Held' status. Using an alias (e.g., address+0001@example.com) is also acceptable if your system supports it.
Log a Support Case: If changing the address is not feasible, log a support case. Include the affected email address, your MID, and specific details of the problem.
Note: Before requesting a status change, you must confirm that all inactive email addresses have been removed from the ML. If you do not remove them, the ML address will simply become 'Held' again, and the delivery failures will recur.
005228132

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.