Marketing Cloud Connect with MCE: Best Practices

Marketing Cloud Connect links Salesforce Sales or Service Cloud with Marketing Cloud Engagement, allowing teams to use CRM data for segmentation, personalization, campaign execution, and engagement tracking. A successful integration requires more than simply installing the connector – it needs clear ownership, controlled data, and consistent governance.

Set up synchronized data extensions as non sendable

Define Your Data and Lead-Management Strategy

Marketing Cloud Connect can support different data flows, so decide where a person should first become known to your business.

Marketing Cloud Engagement first

A form can write data directly to Marketing Cloud Engagement, usually into a data extension. Marketing Cloud Engagement can then nurture the person through a journey using email engagement, form submissions, website behavior, and scoring. Once the person reaches a defined qualification threshold, the qualified data can be sent to Salesforce as a Lead or Contact.

This model is useful when marketing wants to:

• Start nurturing prospects before creating CRM records
• Keep Salesforce free from unqualified or incomplete leads
• Test campaigns and forms quickly
• Let marketing manage early-stage communication independently

However, the process must include clear rules for consent, duplicate prevention, identity matching, and when a prospect is transferred to Salesforce.

Salesforce or Data 360 first

A form can also create or update a Salesforce record first. The data can then be synchronized to Marketing Cloud Engagement for segmentation, personalization, and nurturing.

This model is useful when the business needs to:

• Give Sales immediate visibility of new inquiries
• Apply Salesforce assignment rules and lead routing
• Match the person to an existing Account, Contact, or Lead
• Use CRM validation, deduplication, and compliance processes
• Combine form data with sales, service, and customer history
• Maintain Salesforce as the central customer and consent record

If Data 360 is part of the architecture, incoming data can also be unified with information from multiple sources before it is activated in Marketing Cloud. This supports more complete profiles, better segmentation, and more accurate personalization. Salesforce describes Data 360 as a platform for unifying and activating customer data from multiple sources. Salesforce Data 360 overview

Where do Salesforce Prospects fit?

Salesforce Marketing Cloud Next introduces a Prospect record for people who are not yet qualified as Leads. Prospects can be imported, nurtured, scored, and converted to Leads or Contacts when they meet defined engagement or qualification criteria. Working with Prospects

This is different from a standard Marketing Cloud Engagement data extension record. If the organization uses Marketing Cloud Next and Data 360, the Prospect object can support a formal pre-lead lifecycle. If it uses Marketing Cloud Engagement with Marketing Cloud Connect, the same business process may instead be implemented with data extensions, scoring rules, and a controlled handoff to Salesforce Leads.

The important principle is to define one clear lifecycle:

Form submission → Prospect or marketing record → Nurture → Qualification → Salesforce Lead or Contact

Document which system owns each field, how consent is synchronized, what qualifies a person for sales follow-up, and how engagement history is transferred between platforms.

Synchronize Only the Data You Need

A principle often repeated by marketing automation consultants is: bring only the data you need into the marketing platform.

This is important because Marketing Cloud Engagement does not count only people who receive emails. The current licensing metric is generally based on the Total Distinct Contacts Count, which is calculated using unique Contact Keys. The official number should be checked in the Contacts Counts report in Analytics Builder. Salesforce contact-count guidance

Marketing Cloud Connect can automatically register Salesforce Leads, Contacts, and Users as Marketing Cloud contacts when their records are synchronized. They can be added to All Contacts even if they do not have an email address, phone number, or active subscription. These records can therefore contribute to contact usage before any message is sent. Salesforce contact definition

The following can contribute to the billable contact count:

• Records in All Contacts
• Contacts in populations
• Contacts stored in triggered-send hidden lists
• Salesforce Leads, Contacts, and Users synchronized through Marketing Cloud Connect
• Contacts added through imports, APIs, message sends, or Journey Builder
• Contacts without a channel address, such as an email address or mobile number

Contacts are deduplicated by Contact Key. However, the same person can be counted more than once if different Contact Keys are used, for example, if the same email address exists under separate Salesforce IDs or subscriber keys.

It is also important to distinguish Subscribers from Contacts. All email subscribers are contacts, but not all contacts are subscribers. All Subscribers represents the email channel, while All Contacts can include email, SMS, MobilePush, synchronized CRM records, and contacts that have not yet been assigned to a channel.

For this reason, use Marketing Cloud Connect synchronization filters to bring in only records that are required. Many organizations create a Salesforce field such as Sync_to_MCE__c, which is set to true only when the record meets the agreed business rules—for example:

• The record has a valid email address or mobile number
• The record has the required marketing consent – HasOptedOutEmail, HasOptedOutPhone fields
• The Lead is active and has not been converted
• The record belongs to the relevant market or business unit
• Test, internal, deleted, or inactive records are excluded
• Salesforce Users are synchronized only when they are genuinely needed

Filtering must happen before records enter Marketing Cloud Engagement. For example, a Journey Builder entry filter is not enough to prevent contact creation: Salesforce states that a person can be counted as a contact as soon as they reach the journey entry source, before the entry filter is evaluated.

Synchronize only eligible records, use a consistent Contact Key, and monitor the Total Distinct Contacts Count, not only the All Subscribers number.

Create a Master Audience Data Extension

Create a reusable Master Audience Data Extension that combines eligible Leads, Contacts, and other approved audience records into one standardized structure. Include fields such as ContactKey, 18-digit Salesforce ID, record type, email address, mobile number, consent status, lifecycle stage, language, region, and business unit.

This data extension can be used to build reusable segments and send one email to a combined audience instead of creating separate sends for Leads and Contacts. Use a consistent Contact Key and apply deduplication rules before loading records. Do not include Salesforce Users unless they are genuinely part of the marketing audience, because synchronized CRM Users can also contribute to Marketing Cloud contact usage.

The Master Audience Data Extension should support segmentation and ad hoc sends. It should not normally be used directly as the entry source for every Journey.

Use Separate Data Extensions for Journeys

For each Journey, create a separate journey-specific Data Extension that contains the final audience snapshot and the fields required by that Journey. Populate it from the master audience using a scheduled query or automation.

This approach has several benefits:

1. View As Web Page reliability
   The Journey Data Extension remains available after the segment is refreshed. This helps preserve the data needed to render View As Web Page links. Salesforce notes that a View As Web Page link can break if the original send Data Extension is cleared or deleted.
2. Journey history
   The Data Extension provides a record of exactly which people entered the Journey at that time. This is more reliable than depending on a segment that changes later.
3. Template preview and testing
   A stable send Data Extension makes it easier to preview personalization, test email rendering, and validate that the required fields are available before activation.

A common setup is to refresh the master audience or segment twice per day, then copy the eligible records into separate Journey Data Extensions. Apply a suitable retention policy so the Journey audience history remains available for the required reporting period. Salesforce recommends configuring retention policies for Data Extensions according to the business need.

Clean Up Contacts That Are No Longer Eligible

Changing a Salesforce synchronization filter does not automatically delete records that were previously synchronized to Marketing Cloud Engagement.

Create a regular cleanup process for contacts whose Salesforce record is:

• Deactivated or deleted
• Converted from a Lead
• No longer covered by the Sync_to_MCE__c rule
• Missing the required consent or contact details
• No longer relevant to the marketing audience

Before deleting a contact, check that it is not active in a Journey, used in a current send, or required for reporting, consent, or compliance. Then remove it according to the organization’s retention policy.

Contact deletion in Marketing Cloud Engagement is irreversible and can remove associated tracking history and preferences. Also, if the Salesforce synchronization remains active, deleted contacts can be added back during the next synchronization cycle. Salesforce recommends reviewing synchronization filters and the Contacts Counts report when contact totals increase unexpectedly. Salesforce contact-count guidance

Excluding a record from synchronization prevents future updates, but it does not remove the existing Marketing Cloud contact.

Data Cleanup: Pause Synchronization for Contacts, Leads, and Users

Before deleting contacts from Marketing Cloud Engagement, pause the relevant Marketing Cloud Connect synchronization and review the synchronization filters. Updating a filter does not remove records that were already synchronized, and deleting contacts while synchronization remains active may cause them to be recreated during the next sync cycle. To prevent duplicate or unnecessary records, confirm that the contacts are no longer needed for active journeys, sends, reporting, consent, or compliance before completing the cleanup.

Consent Synchronization

Share With Others