Salesforce Marketing Cloud
Salesforce Marketing Cloud is the digital marketing platform Salesforce acquired from ExactTarget in 2013 and now markets as Marketing Cloud Engagement.
Definition
Salesforce Marketing Cloud is the digital marketing platform Salesforce acquired from ExactTarget in 2013 and now markets as Marketing Cloud Engagement. It runs as a separate tenant from the core Sales and Service Cloud org, with its own data model, its own user accounts, its own API endpoints, and its own subdomain (mc.exacttarget.com). Marketing Cloud handles email, SMS, push notifications, ads, and journey-based multichannel orchestration. It targets the marketer persona rather than the salesperson or service agent who lives in core Salesforce.
Marketing Cloud Engagement is one of three products in the broader Marketing Cloud family: Engagement (the original ExactTarget platform), Account Engagement (the rebranded Pardot for B2B), and Personalization (the rebranded Interaction Studio for real-time site personalization). The three products share branding but are technically distinct, with separate billing, separate UIs, and separate data models. Most enterprise Salesforce customers run at least two of them, often without realizing they are not the same product.
How Salesforce Marketing Cloud works as a multichannel marketing platform
Why Marketing Cloud is a separate tenant
Marketing Cloud was acquired, not built. ExactTarget had its own infrastructure: AMPscript, Data Extensions, Subscriber Keys, send classifications, IP warm-up pools. Salesforce kept all of it. The decision to run Marketing Cloud on a separate tenant is a direct consequence. Sales Cloud and Service Cloud share a single org metadata model. Marketing Cloud has its own org concept called a Business Unit, its own permissions model, and its own API. Integrations between core Salesforce and Marketing Cloud go through Marketing Cloud Connect, a managed package installed in the core org that synchronizes Contacts, Leads, Campaigns, and Send activity.
Data Extensions: the Marketing Cloud database
Where Sales Cloud has objects, Marketing Cloud has Data Extensions: flat tables with named fields that hold subscriber and audience data. Data Extensions are flexible. A campaign manager can create a new one in minutes, no metadata deployment required. They are also disconnected from the rest of the platform. Without Marketing Cloud Connect or a custom integration, a Lead in Sales Cloud and a Subscriber in Marketing Cloud are completely separate records. The Data Extension model is what makes Marketing Cloud fast for marketers and slow to align with the rest of the customer record.
Subscriber Keys, Email Addresses, and the deduplication problem
Marketing Cloud has two ways to identify a contact: Subscriber Key (an ID you control) and Email Address (the contact information). Subscriber Key is the source of truth. Email Address is metadata that can change. Orgs that never set Subscriber Key explicitly end up with the Email Address as the implicit key, which means a subscriber who updates their email becomes a new record. The fix is to set Subscriber Key to the Sales Cloud Contact Id at integration time. The mistake is universal in older Marketing Cloud deployments and painful to fix retroactively.
AMPscript, SSJS, and the templating layer
Email content in Marketing Cloud uses AMPscript, an inline scripting language, and Server-Side JavaScript (SSJS) for more complex logic. AMPscript handles personalization tokens: %%FirstName%%, %%Lookup(DE, "Field", "Key", value)%%. SSJS handles loops, conditionals, and API calls. The two coexist in the same template. AMPscript is the legacy default. SSJS is the path forward for any logic that exceeds simple field substitution. Both run server-side at send time, so the email a subscriber receives is the rendered output, not the template.
Journey Builder vs Automation Studio
Marketing Cloud has two orchestration tools, often confused. Journey Builder is the subscriber-facing canvas: drag-and-drop nodes for sends, decisions, waits, and joins, with a Contact entering the journey based on an event or schedule. Automation Studio is the data-facing pipeline: scheduled or triggered workflows that import files, run SQL queries, segment data extensions, and feed Journey Builder. The pattern most teams use is Automation Studio for the ETL and Journey Builder for the customer experience. Mixing the two leads to journeys that try to do data prep mid-canvas, which is fragile.
Business Units, sharing, and multi-brand orgs
Marketing Cloud organizes large customers into Business Units (BUs). Each BU has its own Data Extensions, sends, and reporting, but shares the parent account, billing, and IP warmup pool. Multi-brand companies use BUs to separate the consumer brand from the B2B brand, or to give regional teams their own workspace. Cross-BU sharing is opt-in. A Data Extension marked Shareable can be referenced from child BUs. Without sharing, every BU is an island. The BU design choice is the single biggest lock-in decision in a Marketing Cloud rollout.
Email deliverability and IP warming
Marketing Cloud uses shared and dedicated IP pools for outbound sending. New customers usually start on shared IPs, where reputation is maintained across many senders. Enterprise customers move to dedicated IPs, which require a warm-up plan: gradually ramp the daily send volume to build reputation with Gmail, Yahoo, and Outlook. Cold-launching a dedicated IP at full volume guarantees the first send lands in spam. Marketing Cloud provides Sender Authentication Package (SAP) to configure DKIM and DMARC for the brand domain. Without SAP, emails sign with exacttarget.com, which kills brand trust.
Launching a Marketing Cloud Engagement campaign
Setting up a campaign in Marketing Cloud means provisioning the audience as a Data Extension, designing the email content with AMPscript, building a journey or send, and configuring the sender profile for deliverability.
- Provision the audience as a Data Extension
Open Email Studio, Subscribers, Data Extensions, Create. Define the fields (SubscriberKey, EmailAddress, FirstName, custom segmentation fields). Mark SubscriberKey as the primary key. Mark the DE as Sendable and pick EmailAddress as the relationship field.
- Design the email content
In Content Builder, create a new email, pick a template, drag content blocks (text, image, button) into place. Use AMPscript tokens %%FirstName%% for simple personalization and AMPscript blocks for conditional content. Preview against a Data Extension row to validate the rendering.
- Configure the sender profile and send classification
Open Email Studio, Admin, Send Management, and confirm the sender profile (from name, from email, reply-to). Pick a send classification that maps to a delivery profile (commercial vs transactional). Wrong classification routes the email through the wrong IP pool.
- Build the journey or guided send
For a one-time campaign, use Email Studio's Send Wizard with the Data Extension as the audience. For an ongoing nurture or trigger, use Journey Builder: drag the Data Extension entry source, add email activities, decision splits, and waits.
- Set up tracking and reporting
Confirm the email tracking parameters are appended (clicks tracked through SafeHouse redirects). Pin the tracking report to the Analytics Builder dashboard. For sends that feed Sales Cloud, configure Marketing Cloud Connect to write engagement back to Lead and Contact records.
The flat table that holds audience and segmentation data. Marked Sendable for use as an email audience, Testable for content preview rows.
The identifier that uniquely binds a subscriber across sends. Should be the Sales Cloud Contact Id when integrated with core Salesforce.
Sub-tenant within a Marketing Cloud account, with its own Data Extensions, sends, and reporting. Used for multi-brand or regional separation.
Add-on configuration that signs outbound email with DKIM and DMARC under the brand domain instead of exacttarget.com.
The managed package installed in core Salesforce that synchronizes Contacts, Leads, Campaigns, and tracking data between the two platforms.
- Subscriber Key defaults to Email Address if not set explicitly. Always populate Subscriber Key with the Sales Cloud Contact Id at integration time.
- Data Extensions are not the same as Sales Cloud objects. There is no schema connection by default. Marketing Cloud Connect or a custom integration is required to keep them aligned.
- AMPscript runs server-side at send time. Errors do not surface in a preview, only in the rendered email or the Tracking report. Test against multiple Data Extension rows before scheduling a send.
- Dedicated IPs need a warm-up schedule. Sending full volume on day one of a new IP burns the reputation and triggers spam filters at Gmail and Outlook for months.
- Journey Builder and Automation Studio look similar but have different strengths. Use Automation Studio for data prep and Journey Builder for customer-facing orchestration.
Trust & references
Cross-checked against the following references.
- Marketing Cloud Engagement OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Salesforce Marketing Cloud.
- Marketing Cloud Engagement OverviewSalesforce Help
- Data ExtensionsSalesforce Help
Hands-on resources to go deeper on Salesforce Marketing Cloud.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Salesforce Marketing Cloud?
Q2. What studios does it include?
Q3. Who should use Marketing Cloud vs Pardot?
Discussion
Loading discussion…