Data 360 and Marketing Cloud
How Data 360 feeds Marketing Cloud Engagement and Marketing Cloud Next, where they differ, and the mistakes that cause stale or non-compliant sends.
Data 360 and Marketing Cloud are designed to work together, but "Marketing Cloud" now means more than one product. Marketing Cloud Engagement (formerly ExactTarget) is a separate platform with its own data extensions, subscribers and Journey Builder. Marketing Cloud Next is built on the Salesforce Platform with Data 360 and Agentforce. Salesforce says Next "doesn't replace Marketing Cloud Engagement—it complements and extends it".
The connection to Data 360 works differently for each. This page explains both: how segments reach journeys, how profile data feeds personalisation, how consent is enforced, what latency to expect and which mistakes to avoid. For the step-by-step journey activation pattern, see activating Data 360 segments in journeys.
The business problem
Teams buy Data 360 to give marketing a single customer view, then find that audiences arrive late in Journey Builder, consent differs between systems, and personalisation still reads from old data extensions. The cause is usually design, not product: each Marketing Cloud product connects to Data 360 in its own way.
Proposed architecture
This is a reference design. We validate the activation targets, editions and permissions for each implementation. See also the Marketing Cloud and Marketing Cloud Next architectures.
Data 360 and Marketing Cloud 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 and Service Cloud | Salesforce product | Contacts, leads, accounts and cases, ingested through zero cost connectors. |
| Web and app eventsInteractions SDK | Channel or touchpoint | Behavioural events from the Salesforce Interactions SDK, sent only after consent. |
| Commerce and other dataB2C Commerce, files, warehouse | Data and analytics | Orders, products and external data by connector, file or zero copy. |
| Harmonised DMOsCustomer 360 Data Model | Data and analytics | Maps source DLOs to the Customer 360 Data Model. |
| Unified profilesidentity resolution | Data and analytics | Identity resolution output: Unified Individual and unified contact points. |
| Segments and insightssegments, CIs | Data and analytics | Audiences and calculated insights built on unified profiles. |
| Consent DMOschecked at send time | Identity, policy and governance | Communication Subscription Consent per contact point, subscription and channel. |
| MC EngagementJourney Builder, data extensions | Salesforce product | Separate platform for high-volume email, SMS and journeys, with its own subscriber and data extension model. |
| Marketing Cloud NextGrowth or Advanced Edition | Salesforce product | Marketing on the Salesforce Platform with Data 360; checks consent DMOs at send time. Confirm how segments reach it in your edition. |
| Email, SMS and pushper product | Channel or touchpoint | Messages sent by whichever Marketing Cloud product owns the journey. |
Data flows
- Salesforce CRM → Harmonised DMOs: CRM records. Zero cost connector streams; mapping errors stop records reaching DMOs.
- Web and app events → Harmonised DMOs: consented events. Standard path every 15 minutes for engagement data, or the real-time layer where configured.
- Commerce and other data → Harmonised DMOs: orders and products. Connector, file or zero copy. Check refresh timing per source.
- Harmonised DMOs → Unified profiles: identity resolution. Ruleset runs produce unified profiles. Source records are not altered.
- Unified profiles → Segments and insights: unified profiles. Segments built on the Unified Individual; stale runs mean stale audiences.
- Harmonised DMOs → Consent DMOs: consent records. Consent imports, preference pages and permitted flows write consent DMOs.
- Segments and insights → MC Engagement: activation. Segment members and attributes activated to MC Engagement for journeys. Reconcile counts on arrival.
- Segments and insights → Marketing Cloud Next: segments. Data 360 segments used on the same platform; confirm in Salesforce Help whether an activation step applies in your edition.
- Consent DMOs → Marketing Cloud Next: send-time check. Consent DMOs are checked at send time in Marketing Cloud Next.
- Consent DMOs → MC Engagement: suppression data. MC Engagement keeps its own subscription model, so pass consent as attributes or sync it by design.
- MC Engagement → Email, SMS and push: sends. Email, SMS and push from Journey Builder and Email Studio.
- Marketing Cloud Next → Email, SMS and push: sends. Email, SMS and other channels from Marketing Cloud Next.
- MC Engagement → Harmonised DMOs: engagement data. Sends, opens and clicks ingested back through the MC Engagement connector.
Component responsibilities
| Component | Responsibility |
|---|---|
| Data 360 | Ingests, unifies and segments customer data; holds consent DMOs for Next |
| MC Engagement | Runs journeys and sends from its own data extensions and subscriber model |
| Marketing Cloud Next | Runs on the Salesforce Platform with Data 360; checks consent DMOs at send time |
| MC Engagement connector | Brings Engagement data into Data 360 as a zero cost connector |
| Activation | Sends segments and attributes from Data 360 to MC Engagement |
Segments to journeys
Marketing Cloud Engagement: segments are activated from Data 360 to Engagement, then used as journey entry audiences. Activations support incremental refresh. Salesforce Help lists current target behaviour; our guide to activating segments to Marketing Cloud covers the practical detail.
Marketing Cloud Next: segments are built in Data 360 on the same platform, so there is no export to a separate account; check Salesforce Help for whether an activation step applies in your edition. The segment's publish timing still sets the audience's freshness. See journey orchestration patterns for Marketing Cloud Next.
Calculated insights can also trigger data actions to Marketing Cloud, which suits event-like triggers such as a score crossing a threshold.
Profile data in personalisation
In Engagement, personalisation reads activated attributes at send time, typically with AMPscript. In Next, personalisation reads Data 360 profile data on the platform. Salesforce Personalization adds two documented paths: for Marketing Cloud Advanced email, the recommender is a data source called server-side per recipient at send time; for MC Engagement, "Batch Personalizations" generate decisions in bulk for a Data 360 segment and activate them to Engagement.
Consent
In Marketing Cloud Next, consent is stored as DMOs in Data 360 and checked at send time. Engagement keeps its own subscription model, so consent captured in Data 360 or CRM does not reach it automatically. Decide which system is the source of truth and how changes flow; see consent in Marketing Cloud Next.
Latency
End-to-end timing is the sum of source ingestion (standard web and mobile engagement data every 15 minutes, profile data hourly), identity resolution, segment publish and, for Engagement, the activation landing. Do not assume a segment built at 9:00 is in a journey at 9:01. Measure it.
Common mistakes
| Mistake | Effect | Fix |
|---|---|---|
| Treating Engagement and Next as one product | Wrong integration design | Design each connection separately |
| Assuming Data 360 consent applies in Engagement | Sends to opted-out contacts | Sync consent or pass suppression attributes |
| Journeys entering before activation lands | Partial audiences | Schedule entry after the publish completes |
| Activating every attribute | Slow loads and wider exposure | Activate only what messages use |
| Using Contact Key and Unified Individual ID interchangeably | Duplicate or missed contacts | Agree the identifier at design |
Security boundaries
Engagement is a separate account with its own users and API credentials, so activation crosses a boundary. Next runs inside your org. Limit activated attributes and keep Engagement users' access to activated data under review.
Failure handling
Hold journeys when an activation fails or arrives with an unexpected count. Alert on consent sync failures before the next send window.
Deployment model
We build in sandboxes and Engagement test business units, working remotely from India, with release steps documented for both products.
Implementation stages
- 01
Decide the product split
Which journeys run in Engagement and which in Next.
- 02
Design identifiers
Agree how Contact Key maps to unified profiles.
- 03
Design consent
Choose the source of truth and the sync path.
- 04
Build activations
Configure segments, targets and attributes.
- 05
Test end to end
Reconcile counts and test opt-outs before launch.
Testing strategy
Use seed profiles to trace a contact from source to send. Test opt-out in each channel and confirm it blocks the send in the product that owns the journey. Our journey testing guide applies to both products.
Prerequisites and limitations
New customers start Marketing Cloud Next with Growth or Advanced Edition; existing customers can renew into "+" versions such as Engagement+. Data 360 must be provisioned. Feature availability varies by edition.
Related
Marketing Cloud Next implementation
Delivery for Next
→Engagement vs Next
How the two products compare
→Planning a move to Next
Moving journeys from Engagement
→Data 360 activation
All activation destinations
→Questions we hear
Does Marketing Cloud Next replace Engagement?
Do we need to export segments to Marketing Cloud Next?
Will Data 360 consent stop Engagement sends?
Can we run both products?
Sources
- https://trailhead.salesforce.com/content/learn/modules/marketing-cloud-next-for-marketing-cloud-engagement-foundations/get-to-know-marketing-cloud-next-with-marketing-cloud-engagement
- https://salesforce.com/blog/marketing-cloud-next-details/
- https://trailhead.salesforce.com/content/learn/modules/consent-management-fundamentals-for-marketing-cloud-next/explore-consent-tools-and-concepts
- https://trailhead.salesforce.com/content/learn/modules/salesforce-personalization-recommenders-with-agentforce-marketing/use-recommenders-to-deliver-personalized-experiences
- https://trailhead.salesforce.com/content/learn/modules/data-cloud-connect-and-unify/connect-and-transform-data
Connect Data 360 and Marketing Cloud
We can design the split between Engagement and Next, the identifiers and the consent flow.
