Marketing Cloud Connect Components and Engagement Checklist

After six posts on Marketing Cloud Connect mechanics, here's the consolidated reference we hand to engineers starting a new MC Connect engagement - component cheat sheet + kickoff checklist.

Components we use most

ComponentPurposeSynchronized Data ExtensionCRM object data synced into SFMC as a DE; read-only in SFMCSalesforce Entry SourceTriggers a Journey when a CRM record meets a filterSalesforce ActivityInside Journey Builder, updates or creates CRM recordsMarketing Cloud Connect PackageThe app installed in Salesforce CRM that enables the integrationIntegration UserA Salesforce user account the API runs through; needs appropriate permissionsDistributed MarketingLets CRM users (agents, reps) send from SFMC templates via Salesforce UI

Each plays a specific role. Knowing which to reach for saves time during design.

Kickoff checklist for MC Connect engagements

Common engagement flow

Week 1: Discovery + permissions

• Confirm CRM / SFMC licenses cover MC Connect
• Map the CRM objects and fields in scope
• Get the Integration User created with correct permissions
• Confirm all environments (production, sandbox) are accessible

Week 2: Sync setup + verification

• Configure Synchronized DE for each object
• Set sync frequency per object
• Wait for initial sync to populate
• Validate row counts and sample records
• Document the schema (field names, data types) for developers

Week 3-4: Build Journeys + Activities

• Build Salesforce Entry Source Journeys for the triggered campaigns
• Add Salesforce Activity writes-backs where needed
• Test end-to-end in sandbox with synthetic records

Week 5-6: UAT + production cutover

• Run UAT with the client using real-looking data in sandbox
• Verify timing - how quickly do CRM events trigger Journeys?
• Move to production with a phased rollout if possible
• Monitor the first week closely

Reference: things that don't belong in MC Connect

Some use cases look like they need MC Connect but don't:

• Non-Salesforce CRM (HubSpot, Dynamics) - use REST API or middleware.
• Non-real-time CRM snapshots delivered as files - regular Import Activity is cheaper than configuring a full MC Connect sync.
• Computed fields that need to be derived from multiple CRM objects - do the computation in Salesforce first (formula field, Flow), then sync the computed field, not raw fields.
• Complex data joins across many CRM objects - pre-compute a flat view in Salesforce (reports or APEX) and sync that view, rather than syncing many objects and joining in SFMC.

When the integration breaks

Most MC Connect issues come from one of four causes:

1. Integration User permissions - audit first.
2. Sync cycle delays - what you expected to be immediate is actually 30 minutes.
3. Field mappings - a field renamed on the CRM side wasn't updated in the sync config.
4. Sandbox/production drift - sandbox MC Connect points at sandbox CRM, production MC Connect points at production CRM; configs can drift.

First-response playbook: check the Integration User first, then sync status in Contact Builder, then mapping, then sandbox/production alignment.

Takeaway

MC Connect is a set of maybe six components you'll use repeatedly on Salesforce + SFMC engagements. Knowing what each does and running through the kickoff checklist saves the mid-project surprises. Pin this reference in the team wiki and revisit it on every new engagement.

---

Running an SFMC + CRM integration project? Our Salesforce team ships end-to-end MC Connect builds - discovery, permissions, sync config, and Journey setup - on production engagements. Get in touch ->

See our full platform services for the stack we cover.