Marketing Cloud integration is the work of deciding which data reaches the platform, by which mechanism, how often, and who is accountable when it stops. Twopir Consulting builds those connections — Marketing Cloud Connect, the REST and SOAP APIs, Data 360 activation and middleware — with field mapping, sync cadence and error handling designed rather than left at default.
"Integrate Marketing Cloud" is five different pieces of work depending on the mechanism. Choosing between them is an architecture decision with cost, latency and governance consequences — and it is the decision most often made by whoever gets there first rather than deliberately.
| Pattern | What it does | Direction & cadence | Use it when | Watch for |
|---|---|---|---|---|
| Marketing Cloud Connect | Pulls selected Salesforce CRM objects into data extensions via synchronized data sources in Contact Builder, carrying across the schema and relationships already defined in CRM. | CRM into Marketing Cloud, on a configurable poll schedule | Sales Cloud or Service Cloud is your system of record and marketing needs to segment on it | Field count and contact count — see the next section. Both have direct cost consequences. |
| REST API | Broad programmatic access across Marketing Cloud Engagement — data extension rows, triggered sends, journey entry, asset and contact operations. | Bidirectional, on demand or event-driven | A non-Salesforce system needs to push an event or pull a result in near real time | Credential scope and rate limits. An integration built with broader permissions than it needs is a standing risk. |
| SOAP API | Comprehensive access to most email functionality, including operations the REST surface does not expose. | Bidirectional, on demand | You need subscriber and send operations the REST API does not cover, or you are maintaining an existing integration | Verbosity and maintenance cost. New builds should default to REST and use SOAP where it is genuinely required. |
| Data 360 activation | Unifies data across sources into resolved profiles, then activates segments and calculated insights into Marketing Cloud as an activation target. | Data 360 into Marketing Cloud, on activation schedule | Audience definition should live once, above the channel, and be shared with sales and service | This is a platform program, not a marketing task. See Data 360 consulting. |
| Middleware | An integration platform (MuleSoft, Celigo or similar) brokers between Marketing Cloud and systems that should not be point-to-point coupled to it. | Bidirectional, orchestrated, with retry and monitoring built in | Several systems, transformation logic, or an enterprise integration standard already in place | A layer nobody owns. Middleware moves the governance problem; it does not remove it. |
Scroll the table sideways to see every column
Capabilities verified against Salesforce documentation Last reviewed 18 September 2026
Marketing Cloud Connect is how Salesforce CRM data reaches Marketing Cloud Engagement. You select objects, select fields, and set a poll schedule; the records land in data extensions that carry across the schema and relationships already defined in Sales Cloud or Service Cloud.
It is straightforward to switch on, which is exactly why it is so often switched on without a design. Four consequences follow directly from the configuration choices, and all four are easier to get right at the start than to unpick two years later.
If you are choosing between this and Data 360 as the route into Marketing Cloud, that decision belongs in the architecture phase, not in build.
Salesforce is explicit that every contact or lead synchronized through a synchronized data source counts as a contact in Contact Builder — whether or not you ever send that person a message. This is the origin of most unexplained contact-count growth, and therefore of unexplained cost. The fix is to filter at the source rather than synchronizing an object wholesale and segmenting afterwards.
Salesforce recommends no more than 20 fields per object on a synchronized data source for optimum performance, with 250 as the hard maximum. Teams routinely synchronize every field "in case we need it", and then wonder why the sync is slow. Selecting the fields marketing actually segments or personalizes on is a half-day exercise that pays back permanently.
The schedule determines how stale marketing's view of a customer can be. A journey that triggers on a CRM status change is only as timely as the poll that detects it — so a retention journey reacting to a cancellation needs a different cadence from a quarterly newsletter audience. This is a per-object decision, not one global setting.
By default, data extensions holding synchronized data sit at the top level of an Enterprise tenant and cannot be moved into a shared folder. In a multi-business-unit estate that constrains how data is shared between units, so it belongs in the business unit design conversation at the start rather than being discovered when the second brand is onboarded.
A journey is only as good as the signal that starts it. Most marketing teams are limited not by Journey Builder but by the fact that the events worth reacting to — an order, a failed payment, a support escalation, a renewal date — live in systems Marketing Cloud has never been connected to.
Each integration below states what moves, in which direction, and which team consumes it. That is the level at which an integration is actually specified; anything less is a logo on a slide.
Leads, contacts, opportunities and campaign membership flow into data extensions through Marketing Cloud Connect, so marketing can segment on pipeline state rather than on last-email-opened. Send and engagement data returns as CRM activity, which is what lets a rep see the nurture a prospect has actually received before they call.
Case status, entitlement and service history reach marketing so a customer with an open escalation is suppressed from the upsell campaign. Direction matters here: this is primarily a suppression and sensitivity signal moving into marketing, not a marketing signal moving out.
Data 360 (formerly Data Cloud) resolves identity across web, app, commerce and CRM sources into unified profiles, then activates segments and calculated insights into Marketing Cloud as an activation target. Audience definition moves up above the channel, so the same segment can serve marketing, sales and service instead of being rebuilt in each.
Orders, subscriptions, entitlements and payment status move into Marketing Cloud through the REST API or middleware, turning transactional reality into journey triggers — a failed payment starts a recovery journey before the renewal lapses, rather than after the churn is recorded.
Product usage, propensity scores and model outputs are pushed into data extensions for segmentation, while tracking data is extracted out of Marketing Cloud for analysis alongside everything else the business measures. Both directions matter, and they are usually built by different teams — which is precisely why ownership has to be written down.
Marketing Cloud Engagement offers two APIs — REST and SOAP — that share a common OAuth 2.0 authentication mechanism. Credentials come from an installed package created in Setup, and how those packages are scoped is the difference between a governed estate and one where a single leaked credential can do anything.
For most buyers the decision that matters here is simply whether an integration should be API-driven at all, which the table above answers. The engineering depth beneath it — integration types, permission scopes, rate-limit handling, retry behaviour and custom Journey Builder activity contracts — has its own page: Marketing Cloud API integrations.
Integrations rarely fail loudly. They degrade — a field stops mapping, a poll slips, a credential expires — and the symptom shows up somewhere else entirely, usually as a marketing team that has quietly stopped trusting the data. These are the five signals worth acting on.
The practice page: edition selection, contact model design, and where integration sits in an implementation.
Every integration pointing at the platform you are leaving has to be re-pointed. The inventory phase is where they are found.
Getting engagement data back out — data views, tracking extracts and reconciling Marketing Cloud against CRM campaign numbers.
Integrations degrade quietly. This is who watches them between campaigns.
A worked example of the architecture-first approach on a real client engagement.
Marketing Cloud sits inside a wider Salesforce, HubSpot and revenue operations practice.
They answer different questions, and larger estates usually end up using all three. Marketing Cloud Connect is the right default when Salesforce CRM is your system of record and marketing needs to segment on it. The REST API is for events that cannot wait for a poll, and for systems outside Salesforce. Data 360 is for when audience definition should live once, above the channel, and be shared across marketing, sales and service.
The question that actually decides it is where identity should be resolved. If the answer is "in CRM", Connect is sufficient. If the answer is "across web, app, commerce and CRM together", you are describing Data 360 whether or not you have bought it yet.
Usually because of the integration, not the marketing. Every contact or lead brought across by a synchronized data source counts as a contact in Contact Builder whether or not you ever message them — so synchronizing an entire CRM object wholesale imports its whole history into your contact count.
The remedy is to filter at the source so only records marketing can actually address are synchronized, and to review what the existing synchronized data sources are pulling. It is a common finding in a Marketing Cloud audit, and one of the few with a directly quantifiable saving attached.
Yes. The REST API lets an external system fire a journey entry event or a triggered send directly, so a failed payment in your billing platform or a shipment update in your ERP can start a journey in near real time rather than waiting for the next scheduled load.
The engineering is the easy part. The decisions that take longer are which events genuinely warrant a message, what happens when the same customer triggers three events in an hour, and which system is authoritative when two of them disagree. Those get designed before anything is built.
Salesforce recommends no more than 20 fields per object on a synchronized data source for optimum performance, with 250 as the maximum if more are genuinely required. In practice the useful question is narrower: which fields does marketing segment on, personalize with, or use to trigger a journey? Everything else is weight.
"Synchronize it in case we need it later" is the instinct that produces slow syncs. Adding a field later is a small change; unpicking a synchronization that was never designed is not.
Direct integration is simpler and perfectly appropriate for one or two well-understood connections. Middleware earns its place when several systems are involved, when meaningful transformation happens between them, when orchestration and retry logic need to live somewhere central, or when your organization already has an integration standard that Marketing Cloud should not sit outside of.
The honest caveat is that middleware relocates the governance problem rather than solving it. An unowned integration platform is no better than an unowned point-to-point integration — it is just harder to see.
Three routes, depending on what you need. The APIs retrieve data on demand for another system. Automation Studio extracts and transfers engagement data on a schedule to a warehouse or SFTP destination. And send and engagement data can flow back into CRM as activity, so a rep sees the marketing history on the record they are working.
Which one you need depends on who is consuming it and how fresh it has to be. Reporting is covered in more depth on the reporting and analytics page.
Tell us which systems need to reach Marketing Cloud, what has to happen when they do, and how fast. That is enough to say which pattern fits and roughly what it involves.
Serving: US | Canada | UK | UAE | Australia | New Zealand
