Integration20% of the exam
Marketing Cloud Connect viability, sync and troubleshooting
Whether a customer can run Marketing Cloud Connect (editions, Classic, Government Cloud, multi-org), how keys, users and tracking settings decide what reaches CRM records, and how to keep Synchronized Data Sources and Salesforce Data entry sources working through changes.
Given a customer use case, demonstrate knowledge of features, viability, and troubleshooting of Marketing Cloud Connect.
~8 min read · 24 practice questions ·
What the exam expects
- Judge whether a customer can run Marketing Cloud Connect: CRM edition, Lightning Experience, Government Cloud and multi-org prerequisites.
- Recommend keys, user licences and tracking settings so sends and tracking land on the right CRM records.
- Plan package upgrades, troubleshooting and a disconnect without breaking journeys or queries.
- Diagnose Synchronized Data Sources problems: missing objects or fields, shifted dates, stale formulas, schema changes.
- Explain what limits a Salesforce Data entry source.
- Key terms: Salesforce system user (the CRM-side API user of the connection); Marketing Cloud Connect API user (the Engagement-side API user); integrated user (licensed in both clouds, accounts linked); synchronized data extension (the Engagement copy of a synced CRM object); multi-org (business units connecting to orgs independently).
Key facts
CRM editions
- Detail
- Unlimited, Enterprise, Performance, Developer Edition Sandbox; not Professional
Lightning Experience
- Detail
- Users are redirected to Classic from Marketing Cloud Connect tabs
Multi-org prerequisites
- Detail
- Enterprise 2.0, Connected App Authentication, Custom Profile Centers; no Government Cloud
Business units per system user
- Detail
- Up to 5
Subscriber key for tracking
- Detail
- 18-digit Contact, Lead or User ID
Package upgrades
- Detail
- Sandboxes get the newest version; production follows a release later
Package API logging
- Detail
- Retired with the 234.0 package release
Synced dates
- Detail
- Stored in US Central Standard Time
Objects per refresh cycle
- Detail
- Six at a time
Pause limit
- Detail
- Longer than 15 days requires a refresh
Automatic refresh
- Detail
- More than 600,000 rows changed in a minute
Flow invocations
- Detail
- Less than 2,000 per save transaction
Sources for this section (8)
- Connect Cloudshelp.salesforce.com (opens in a new tab)
- Marketing Cloud Connecthelp.salesforce.com (opens in a new tab)
- Multi-Org Configurationhelp.salesforce.com (opens in a new tab)
- Subscriber Keyhelp.salesforce.com (opens in a new tab)
- Initiate Logginghelp.salesforce.com (opens in a new tab)
- SDS in Contact Builderhelp.salesforce.com (opens in a new tab)
- SDS Best Practiceshelp.salesforce.com (opens in a new tab)
- Salesforce Data Eventhelp.salesforce.com (opens in a new tab)
- Why might an admin be unable to edit a Salesforce entry source even in a draft journey?
- Why pause a CRM object in Engagement before deleting it in the CRM?
- When the connected CRM org changes, what should happen to existing journeys and Salesforce events?
- Which tracking frequency and tracking window does the troubleshooting guide recommend?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Marketing Cloud Engagement Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 20 lessons of the Marketing Cloud Engagement Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (24 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both