What is Salesforce Marketing Cloud Engagement?
Salesforce Marketing Cloud Engagement is a platform for sending and automating customer messages through email, SMS, and mobile app notifications. It uses customer data to choose who receives a message, what it contains, and when it is sent. Businesses use it for newsletters, welcome campaigns, reminders, and messages triggered by customer actions.
The main tools and what they do
Marketing Cloud Engagement separates content, data, sending, and automation into different tools.
| Tool | What it does |
|---|---|
| Content Builder | Creates and stores emails, templates, images, and reusable content blocks. |
| Email Studio | Manages email subscribers, sends, and email tracking. |
| Journey Builder | Builds message sequences with entry rules, waits, and different paths. |
| Automation Studio | Runs tasks such as file imports, SQL queries, data extracts, and scheduled email sends. |
| Contact Builder | Manages contact data and relationships between Data Extensions. |
| Mobile Studio | Handles mobile messaging through tools such as MobileConnect and MobilePush. |
| CloudPages | Creates landing pages and forms, e.g. signup and preference pages. |
The features available in your account depend on your purchased edition and enabled services.
How a customer journey works
Journey Builder sends messages through a sequence you define. Contacts enter through an entry source, then move through activities such as messages, waits, and decision splits.
For example, a welcome journey can:
- Accept a new subscriber from a signup form.
- Send a welcome email.
- Wait before the next step.
- Check whether the subscriber meets a condition.
- Send a different follow-up message based on the result.
Journey Builder uses the content and customer data prepared elsewhere in the platform. The entry settings control which contacts enter and whether they can enter again.
Automation Studio handles the data preparation behind these campaigns. It can import a customer file, run a query, and update the audience before the journey checks for new contacts.
How customer data is stored
A Data Extension is a table with rows and columns. It can hold customer details, orders, preferences, or a campaign audience.
Keep data organized around what each row represents. A customer profile table can contain one row per customer, while an orders table contains one row per order. Both can include a customer identifier to connect the records.
Contact Key identifies a contact across Marketing Cloud Engagement. In Email Studio, the same value is called Subscriber Key.
Use a stable customer ID and keep the key consistent across channels. Different keys for the same person create separate contact records, and Engagement does not automatically merge them.
SQL Query Activities select audiences and combine data from different tables. For example, a query can match customer profiles with recent orders and save the selected customers into a campaign Data Extension.
How personalization works
Personalization uses customer data to change a message. You can insert a first name, show content in the customer’s language, or choose an offer based on their purchase history.
Basic personalization uses fields and dynamic content rules. AMPscript adds lookups, conditions, and formatting when the message needs more control.
Missing data needs a fallback. For example, read the first name with AttributeValue() and use “there” when the value is empty. This produces “Hi there” instead of an incomplete greeting.
Prepare complex calculations before sending where possible. If an email needs the latest order or an assigned offer, an automation can prepare those values in a Data Extension.
Content Builder also lets you reuse headers, footers, and other blocks across emails, reducing repeated content work.
How it connects to websites, apps, and Salesforce CRM
Marketing Cloud Engagement has its own data storage. CRM records become available through a configured connection or data transfer.
Customer data can enter through file imports, APIs, or Marketing Cloud Connect, which connects Engagement with Sales Cloud and Service Cloud.
A website or app can send a transactional email through the API after a customer completes an action, e.g. placing an order.
Engagement supports REST and SOAP APIs. Choose the API based on the operation you need and the endpoints it supports.
What to configure before sending
Set up user access, sender details, customer identifiers, and subscription handling before launching campaigns.
Business Units organize marketing work across teams, brands, or regions. Plan which users can access each unit and which data or content should be shared.
Define how often customer data updates. A journey that needs a recent purchase cannot use it until that purchase reaches Marketing Cloud Engagement. Schedule imports and queries before the activities that depend on them.
Before activating a campaign, check that:
- The audience contains the intended contacts.
- Contact Keys match across the tables used by the campaign.
- Subscription and exclusion rules are applied correctly.
- Personalization works with both complete and missing data.
- Journey entry and re-entry settings match the intended behavior.
- Messages use the correct sender details and working links.
