Marketing Cloud reference architecture
How Contact Builder, data extensions, Journey Builder, Automation Studio, Marketing Cloud Connect, sending, deliverability and CloudPages fit together.
Marketing Cloud Engagement is Salesforce's platform for high-volume email, SMS and push messaging, built around Journey Builder, Content Builder and Automation Studio. Accounts often grow by accretion: a data extension for each campaign, an automation for each import, and journeys that nobody owns. This reference architecture shows how the parts should fit, from data arriving in Contact Builder to sends, tracking and the write-back to CRM.
This is a reference design. We validate the account type, business units, APIs and permissions for each implementation, and GeekMidst can design and implement it through Marketing Cloud implementation.
Business context
Marketing teams need three things from the account: trustworthy audience data, journeys that send the right message at the right time, and tracking that shows what happened. Salesforce describes Engagement as the "proven execution engine for high-volume email, SMS, and journey-based messaging". Marketing Cloud Next is built on the Salesforce Platform with Data 360, and Salesforce says it "doesn't replace Marketing Cloud Engagement—it complements and extends it". If you are weighing the two, see the Marketing Cloud Next architecture.
Marketing Cloud Engagement reference architecture
Reference architecture: a reusable pattern, not a live client integration
Select a component to see what it is responsible for and how data moves to and from it.
Components and data flows (text version)
| Component | Type | Responsibility |
|---|---|---|
| Salesforce CRMSales or Service Cloud | Salesforce product | System of record for contacts, leads and accounts. Its Contact or Lead ID becomes the subscriber key. |
| External filesSFTP drops | External or custom system | Batch extracts from ERP, e-commerce or other systems, delivered as files to Marketing Cloud SFTP. |
| Apps and websitesAPI events | External or custom system | Systems that trigger event-driven messages, such as order confirmations or password resets, through the APIs. |
| Marketing Cloud Connectmanaged package in CRM | Integration layer | Syncs chosen CRM objects into synchronized data extensions on a polling interval and writes tracking back. |
| Automation Studioimports, SQL, scripts | Engagement platform | Scheduled, file-drop or API-started automations that import files, run SQL Query activities and refresh audiences. |
| Journey and send APIsentry events, transactional | Integration layer | REST entry events and transactional send APIs for event-driven messages from other systems. |
| Contact BuilderData Designer, Contact Key | Data and analytics | Links data extensions to the contact record through the Contact Key, in attribute groups. |
| Data extensionssendable and relational | Data and analytics | Tables that hold audiences, preferences and reference data. Primary keys and retention are set per extension. |
| Content BuilderAMPscript, content blocks | Engagement platform | Templates and content blocks. AMPscript personalises content at send time. |
| Journey Buildermulti-step journeys | Engagement platform | Entry sources, waits, decision splits and activities. Owns when and how a contact moves through a programme. |
| Send managementprofiles, classifications | Engagement platform | Sender profiles, delivery profiles and send classifications that mark each send Commercial or Transactional. |
| Emailauthenticated domain | Channel or touchpoint | Commercial and transactional email from an authenticated sending domain with SPF, DKIM and DMARC. |
| SMSMobileConnect | Channel or touchpoint | SMS through MobileConnect using provisioned SMS codes, sent to numbers with a recorded opt-in. |
| PushMobilePush SDK | Channel or touchpoint | Push notifications to your app through the MobilePush SDK. |
| CloudPageslanding pages, forms | Channel or touchpoint | HTTPS-only landing pages and preference forms. A CloudPagesForm Submit Event can start a journey. |
| Tracking and data viewssends, opens, clicks, bounces | Data and analytics | Engagement tracking and system data views such as _Job, _Open and _Subscribers, queried with SQL for reporting. |
Data flows
- Salesforce CRM → Marketing Cloud Connect: object sync. Synchronized data sources poll selected objects and fields. A sync can be paused but not deleted.
- External files → Automation Studio: file drop. A file drop starts an import automation. Import errors appear in the Action Log.
- Apps and websites → Journey and send APIs: API events. Systems call REST entry or transactional send APIs. The caller retries failed calls but must first check whether the original request was accepted, so a retry does not send twice.
- Marketing Cloud Connect → Data extensions: synchronized DEs. Synced data extensions sit at the top (Enterprise) level of the account.
- Automation Studio → Data extensions: imports and SQL. Imports and SQL Query activities write to target data extensions. A query that fails 24 times in a row is deactivated.
- Journey and send APIs → Data extensions: entry event data. API entry events write event data to the journey's entry data extension and admit the contact to the journey.
- Data extensions → Contact Builder: linked attributes. Data extensions are linked to the contact in Data Designer through the Contact Key.
- Contact Builder → Journey Builder: audiences. Journeys read entry audiences and attributes from linked data extensions.
- Content Builder → Send management: templates. Content and AMPscript are rendered at send time; a missing attribute can fail the send for that contact.
- Journey Builder → Send management: email and SMS activities. Journey activities use a send classification, sender profile and delivery profile.
- Send management → Email: email sends. Mail goes out from the authenticated domain. Bounces and complaints are recorded in tracking.
- Journey Builder → SMS: SMS activities. SMS activities send through MobileConnect to subscribed numbers.
- Journey Builder → Push: push activities. Push activities send to app users through MobilePush.
- Email → Tracking and data views: engagement events. Opens, clicks, bounces and unsubscribes are recorded and exposed in data views.
- CloudPages → Journey Builder: form submit entry. A CloudPagesForm Submit Event can start a journey, for example a welcome series.
- Tracking and data views → Marketing Cloud Connect: tracking write-back. Marketing Cloud Connect writes email tracking back to CRM records.
Component responsibilities
| Component | Responsible for | Design note |
|---|---|---|
| Contact Builder | Linking data to the contact through the Contact Key | Salesforce advises no more than three populations per account |
| Data extensions | Audience, preference and reference data | Set primary keys, sendable fields and retention on day one |
| Marketing Cloud Connect | CRM sync, sends to CRM reports and campaigns, tracking write-back | Needs Enterprise, Unlimited or Performance CRM edition and the managed package |
| Automation Studio | Imports, SQL Query, file transfer, scripts | Starts on a schedule, a file drop or an API trigger |
| Journey Builder | Multi-step programmes and decision logic | One owner per journey |
| Send management | Sender and delivery profiles, send classifications | Commercial vs Transactional is a legal choice as well as a technical one |
| CloudPages | Landing pages, preference centres, forms | HTTPS connections only |
| Tracking and data views | Engagement reporting | Query data views into your own reporting extensions |
Data flow, step by step
- CRM data arrives. Marketing Cloud Connect syncs chosen objects and fields on a polling interval. The subscriber key is the CRM Contact or Lead ID, and every synced contact or lead counts as a contact.
- Other data arrives. Files land on SFTP and start Automation Studio imports. SQL Query activities join and filter data into audience extensions; queries time out after 30 minutes.
- Contacts are linked. In Contact Builder, data extensions are linked to the contact through the Contact Key so journeys can use their attributes.
- Journeys decide. Journey Builder admits contacts from an audience or an API entry event, waits, splits and sends. Choosing between journeys and automations is covered in Journey Builder vs Automation Studio.
- Messages are sent. Each send uses a sender profile, delivery profile and send classification. AMPscript personalises content at send time.
- Tracking flows back. Opens, clicks, bounces and unsubscribes are recorded, queried through data views, and written back to CRM by Marketing Cloud Connect.
Trust boundaries and authentication
The CRM boundary is crossed by Marketing Cloud Connect, which uses two system users: the MC Connect API user in Marketing Cloud and a dedicated CRM API user. Give each only the permissions the sync needs. The API boundary is crossed by installed packages with API integration components; scope each package to the minimum it needs and store its secrets server-side. The public boundary is CloudPages: forms are internet-facing, so validate inputs and never expose subscriber data in a URL. Business units separate teams and brands inside the account.
Deliverability
Gmail and Yahoo require bulk senders to use SPF and DKIM, publish a DMARC record (at least p=none) with alignment, and support one-click unsubscribe (RFC 8058) on marketing mail. Microsoft requires SPF, DKIM and DMARC for domains sending more than 5,000 emails a day. See SPF, DKIM and DMARC for Marketing Cloud.
Failure scenarios and how to handle them
| Failure | Effect | How to handle it |
|---|---|---|
| SQL Query fails repeatedly | Activity deactivated after 24 consecutive failures | Alert on Action Log errors; fix the query and reactivate |
| Query runs too long | Times out after 30 minutes | Split the query or move heavy processing upstream |
| Synced object changes in CRM | Sync errors or missing fields | Change-control CRM fields used by the sync |
| Import file late or malformed | Stale audience | Validate file, row count and date before the journey reads it |
| AMPscript references a missing field | Send errors for some contacts | Test with real data; use default values |
| Domain authentication fails | Mail rejected or filtered | Monitor DMARC reports and bounce codes |
Operational monitoring
- Review the Automation Studio Action Log daily for SQL, file transfer and import errors.
- Track journey entry counts against expected volumes, and alert when a journey admits nobody.
- Watch bounce, complaint and unsubscribe rates by domain; keep spam rates below the thresholds Gmail and Yahoo publish.
- Check Marketing Cloud Connect sync status and contact counts, since every synced record counts as a contact.
- Our deliverability checklist lists what to check.
Alternative approaches and trade-offs
Marketing Cloud Connect is the standard CRM path but syncs on a polling interval and counts every synced record as a contact. File-based integration through middleware gives more control over what is sent and when, at the cost of building and running the pipeline. Data 360 activation to Engagement suits teams that already unify profiles in Data 360. The Marketing Cloud Engagement MCP Server, GA since 2 June 2026, lets AI clients read and change data extensions, journeys (created in Draft) and automations under user OAuth; treat write tools as needing human review.
Implementation checklist
- 01
Confirm account and licences
Account type, business units, channels and CRM edition for Marketing Cloud Connect
- 02
Design Contact Builder
Contact Key strategy, attribute groups and data extension standards
- 03
Set up CRM sync
Objects, fields, polling interval and the two system users
- 04
Build automations
Imports, SQL and file transfers with error alerts
- 05
Configure send management
Sender profiles, delivery profiles and send classifications
- 06
Authenticate domains
SPF, DKIM, DMARC and one-click unsubscribe
- 07
Build and test journeys
Test entry, splits and content with real data before activation
- 08
Set up monitoring
Action Log review, entry counts, deliverability and sync status
Related services and solutions
Marketing Cloud implementation
Account setup, data model and journeys
→Marketing Cloud Connect implementation
CRM sync and tracking write-back
→Journey Builder consulting
Journey design and testing
→Email deliverability consulting
Authentication, reputation and monitoring
→CRM to Marketing Cloud synchronisation
Solution design for CRM data in Marketing Cloud
→Salesforce CRM architecture
The CRM side of the integration
→Questions we hear
Is this a design from a client account?
Should we use journeys or automations?
Does Marketing Cloud Next replace Engagement?
Can an AI assistant manage our journeys?
Sources
- https://www.salesforce.com/marketing/engagement/
- https://trailhead.salesforce.com/content/learn/modules/marketing-cloud-connect/get-started-with-mc-connect
- https://trailhead.salesforce.com/content/learn/modules/automation-studio-activities/automate-marketing-cloud-tasks
- https://help.salesforce.com/s/articleView?id=mktg.mc_as_sql_reference.htm&type=5
- https://support.google.com/mail/answer/14229414?rd=1
- https://developer.salesforce.com/blogs/2026/06/the-mcp-server-for-marketing-cloud-engagement-is-now-ga
Review your Marketing Cloud architecture
Tell us how data reaches your account and how journeys are run. We can review the design and propose a cleaner structure.
