Marketing Cloud Connect: When You Need It, When You Don't

On new engagements where the client runs both Salesforce CRM and Marketing Cloud, one of the first architecture decisions is: install Marketing Cloud Connect (MC Connect) or build a custom integration?

MC Connect is the official bridge - data flows from CRM to SFMC as Synchronized Data Extensions, actions in SFMC can update CRM records. It's the "correct" path for most cases, but not all. Here's how we decide.

What MC Connect actually does

Once installed in the Salesforce CRM and configured in SFMC:

• CRM data flows into SFMC as Synchronized Data Extensions - readable by Journey Builder, Automation Studio, and AMPscript.
• SFMC actions can update CRM records - a Salesforce Activity in a Journey can flip a Contact field, create a Task, or log an event.
• Journeys can be triggered from CRM events - "Opportunity closed won" kicks off an onboarding sequence.
• Distributed Marketing lets sales reps send SFMC templates from within the CRM UI.

No custom code, no webhooks, no external integration layer.

When MC Connect is the right call

RequirementMC Connect?Client uses Salesforce CRM and wants Contact/Lead data in email personalizationYesTrigger Journey from CRM events (Opportunity stage change, Case created)YesUpdate CRM records when a subscriber takes action in emailYesSales reps sending branded templates from within the CRMYes

If any of these are in scope, MC Connect is almost always cheaper than building a custom integration.

When you don't need MC Connect

ScenarioMC Connect?Client uses SFMC standalone, no Salesforce CRMNoClient has a CRM but syncs data via existing file drops or a custom APINo - don't replace a working integrationClient wants only one-way data flow with real-time requirements beyond MC Connect's sync cyclesNo - API pattern is betterClient uses a non-Salesforce CRM (HubSpot, Dynamics)No - MC Connect is Salesforce-CRM-specific

For clients on other CRMs, the integration is either custom (REST API against SFMC's Fuel REST API), file-based (nightly exports from the CRM, SFTP to SFMC), or through a middleware platform (MuleSoft, Boomi, Workato).

Discovery questions to ask

Before deciding, we ask the client:

Answers determine both whether to use MC Connect and how to configure it.

What MC Connect doesn't solve

• Real-time requirements below the sync cycle. Synchronized DEs typically refresh every 15 minutes to a few hours. If the email needs current-account-balance data that can't be stale by 10 minutes, use a direct API lookup at send time, not Synchronized DE.
• Non-Salesforce data. If the client's loyalty data lives in a third-party loyalty platform, MC Connect doesn't help. That data arrives via file or API, not through the MC Connect bridge.
• Complex transformations. MC Connect maps CRM object fields 1:1 into Synchronized DEs. Complex joins or reshaping happen downstream via SQL Query Activity on SFMC's side.

Cost consideration

MC Connect itself is a feature of Marketing Cloud licensing - no separate cost for most editions. The cost is time:

• Install the MC Connect package in Salesforce CRM (straightforward).
• Configure the Integration User with the right permissions (most setup time).
• Set up the Object and Field syncs for each CRM object in scope.
• Test the sync in a sandbox before production.

Typical setup: 1-3 days of configuration + testing for a straightforward case (Contact + Lead sync). More if there are many custom objects or permissions take multiple iterations to get right.

Takeaway

MC Connect is the default choice when Salesforce CRM is in the picture and any of the integration use cases apply. Skip it only when the client's CRM isn't Salesforce, when an existing integration is working fine, or when requirements exceed what MC Connect can do. Answer the discovery questions early so this decision doesn't get remade mid-build.

---

Scoping an SFMC + Salesforce CRM integration? Our Salesforce team sets up MC Connect, Synchronized Data Extensions, and hybrid integrations on production engagements. Get in touch ->

See our full platform services for the stack we cover.