Keep these design considerations in mind when you manage vaccine communications with Marketing Cloud Engagement.
Account Configuration
- With SAP, the customer can save time by fully delegating their subdomain to the Engagement app. Hosting DNS takes longer.
- For SSL certificates, Engagement generates and controls both SSL certificates to prevent the lengthier forced redirection.
Messaging Use Cases
Identify the trigger moment for each message type and where it’s initiated. Base this moment on a CRM object change such as appointment record creation or on CRM logic in a process builder or flow. Two examples are 2 hours before an appointment and message initiation.
Core CRM Considerations
- The CRM object referenced in the Salesforce data Journey Builder entry source must relate back to ContactID, specifically Account.PersonContactID. Route people through journeys, not transactions.
- While most Marketing Cloud Connect traffic is excluded from CRM daily API limits, all current core APEX limits still apply.
- Watch for CPU CRM governor limits when using larger flows, more than 50 journeys, or setting up more than 50 journeys for the entry event referencing the same object.
- Together, Salesforce activities written back to CRM and Salesforce entry events injected into the journey contribute to governor limits.
Related Content
|
|
Review earlier steps in this solution. |
|
|
Take the next steps in this implementation. |
See Also
- Marketing Cloud Connect
- Install the Marketing Cloud Connect Managed Package
- Marketing Cloud Connect Frequently Asked Questions
- Manage Customer Journeys
- Multi-Step Journeys
- Transactional Send Journeys
- Entry Sources
- The Salesforce Data Event
- Synchronized Data Sources in Contact Builder
- Create Synchronized Data Sources in Contact Builder
- Synchronized Object Relationship Priority
- Synchronized Data Extensions: Limit of 250 Fields