Requirements for Distributed Marketing

Distributed Marketing requires these products:

• Salesforce Marketing Cloud Engagement with Journey Builder enabled. The documentation refers to this product as Marketing Cloud Engagement.
• Salesforce Sales, Service, Experience, or Industry Clouds with access to the appropriate objects, features, and capacities, including access to contacts, leads, accounts, campaigns, flows, and content. The documentation refers to this product as CRM.
• Salesforce Connect, with the ability to connect to one external data source. One license, including the ability to connect to one external data source, is included with Distributed Marketing. This license is used exclusively by the Distributed Marketing application.
  

  Note Any data submitted to the Salesforce Connect Service is cached on SFDC infrastructure temporarily and isn’t considered Customer Data as defined in the Agreement. However, (I) for that temporary period during which data is cached on the Salesforce infrastructure, such cached data is considered Customer Confidential Information, and the physical and logical protections for such data is the same as those protections applicable to Customer Data submitted to the Salesforce Services, and (II) in the event such data is electronically imported to and stored in the Salesforce Services (and to the extent such data isn’t Content or Non-SFDC Applications), such data is Customer Data.
• Optionally, Marketing Cloud Connect. Users need this product to view engagement metrics such as Email Open in CRM, and to enable more advanced Journey Builder features such as Sales and Service Cloud activities.
• Optionally, MobileConnect. Users need this product to send SMS messages through Distributed Marketing.
  

  Note SMS messages can be sent to individuals who opted into receiving mobile messages. Customers must manage opt-ins outside of the Distributed Marketing application. For example, with email, mobile, or web opt-in templates. Consult independent legal counsel for guidance on applicable legal and industry requirements for managing opt-in. The Mobile Messaging Product Special Terms (PST) apply to SMS messages sent through Distributed Marketing.
• Optionally, SSL. Customers using a private domain need SSL to use the Distributed Marketing Image Block, which supports HTTPS images exclusively.

Distributed Marketing uses an authenticated Marketing Cloud Engagement system user to make marketing content accessible and usable from Sales Cloud. The solution, which can expose content from up to 200 unique Marketing Cloud Engagement business units, requires one unique user per business unit. Also, the business unit must be the unique user’s default business unit. This user is referred to as the Marketing Cloud Engagement system user in this documentation. We recommend that this user is a dedicated system user, not a user shared by an employee.

Each unique Marketing Cloud Engagement system user requires these Marketing Cloud Engagement permissions.

Note

A Marketing Cloud Engagement license isn’t required for every Distributed Marketing user. Marketing Cloud Engagement licenses are only required for Distributed Marketing Cloud Engagement system users. Content Builder: Assets > Subscriber Preview is only for customers using SMS.

When authenticated with a Marketing Cloud Engagement business unit, Distributed Marketing uses named credentials to manage token access throughout the solution. Authenticated calls execute in the context of the authenticating user, which is found on the Execute As field on the named credential’s associated Auth. Provider. The authenticating user in CRM must be an active user and have these CRM permissions:

To configure account authentication:	DMAdministrator License permission set, Administrator permission (mcdm_15 namespace), Manage Auth Providers, Modify All Data, and Customize Application
To maintain an active integration:	Custom Application

Distributed Marketing is available in these Salesforce products and experiences.

Note

• Distributed Marketing requires SOAP APIs. To enable Distributed Marketing support in Sales or Service Cloud Professional Edition, purchase SOAP API separately.
• Distributed Marketing doesn’t support users with External Identity, External Apps (Commerce Portal/ Lightning External Apps), Experience Cloud, Authenticated Sites, and Service Cloud Portal licenses. Your org must have at least one Partner Experience or Partner Experience login license provisioned to install Distributed Marketing.
• Distributed Marketing supports Marketing Cloud Engagement environments using tokenized sending and Field Level Encryption (FLE) with some considerations and limitations.
• Distributed Marketing supports CRM environments using SHIELD with some considerations and limitations.

Note Distributed Marketing uses custom components.

Review these scale considerations for using Distributed Marketing. Because the efficiency and scalability of a customer’s org is mostly a function of their use cases, design decisions and implementation, scale considerations include “your mileage may vary.” Certain workflows can have workflow-specific scale limitations. If your org is heavily customized, testing in a Sandbox environment is recommended.

Governor Limits. Distributed Marketing is a managed package. The product is subject to governor limits. Learn more.

Journey Builder Limitations. Distributed Marketing sends through Journey Builder, and is subject to Journey Builder’s throughput and scale considerations. Learn more.

Users Per Org. Distributed Marketing doesn’t support more than 150,000 users with Distributed Marketing Standard or Admin permissions in a single organization.

Concurrent Users. In an environment with little to no customizations, Distributed Marketing doesn’t impact concurrent users. However, customers can experience concurrency issues when adding or removing members from a campaign. Customers can also encounter issues after customizing the platform using custom rollup summary fields and triggers, which update built-in rollup summary fields. For example, the campaign member status field on the campaign object. After a customer customizes the platform, we recommend that they perform their own performance testing to understand if their customizations imposed more limits outside of the use of Distributed Marketing.

Send Volume. We recommend that customers with custom roll-up summary fields send no more than 500 messages per campaign per minute. Roll-up summary fields lock the parent campaign record and can cause failures due to row-locking. This limit applies to all campaign send types.

Understand the total number of messages your users plan to send. If you think the number of sends could exceed 10,000 sends per minute, or 600,000 per hour, contact the account team to ensure that your account is provisioned for success. This volume is rarely seen. One send equates to an injection onto the journey. The number of messages on a campaign doesn’t have an impact.

Distributed Marketing supports these Journey Builder message activities.

Note

• All Distributed Marketing sending occurs through Journey Builder.
• If a message activity supports preview, users can view the activity and its message content through the Distributed Marketing experience.
• If a message activity supports collaboration, users can optionally interact with the message content through the Distributed Marketing experience.
• The SMS message activity requires MobileConnect.

Distributed Marketing supports sending to these CRM objects.

Distributed Marketing requires these CRM objects and features.

Note While all these objects and features are required to install the solution, individual features can be used at your discretion. Most features are enabled through Distributed Marketing Administration, a permission set, or a combination of both. Features are available in all supported Salesforce Products (Clouds) unless otherwise indicated.

Distributed Marketing supports these languages.