Salesforce Marketing Cloud integration with Commerce Cloud: Why & how?

US ecommerce reached $1.192 trillion in 2024, up 7.5% year over year, according to the US Census Bureau’s February 2025 quarterly report. During the 2025 holiday season, traffic from generative AI sources to retail sites increased 693.4% year over year, according to Adobe’s 2025 Holiday Shopping Report. For commerce and marketing teams running Salesforce platforms, both figures point to the same operational pressure: the signals that determine what a customer needs to hear next are sitting inside the commerce system, and most marketing platforms cannot read them in real time.

For organizations already running Marketing Cloud and Salesforce Commerce Cloud (SFCC), the integration question can be difficult. Marketing Cloud may already manage customer communications across email, SMS, web, and mobile. SFCC handles the storefront, cart, order management, and fulfillment. Connecting them without disrupting either requires architecture decisions that go beyond enabling a connector.

The practical question is which data needs to move, at what frequency, through which integration method, and how that shapes what marketing can actually do with it.

What the integration connects

Salesforce Commerce Cloud (SFCC), now also referred to as Agentforce Commerce, generates events that carry commercial intent: product views, cart additions, abandoned checkouts, purchases, order status changes, returns, and repeat purchase signals. Marketing Cloud, in its current configuration, does not receive these events automatically.

Data 360 (Salesforce’s current name for what was previously called Data Cloud) provides the integration layer most enterprise implementations now use. It ingests commerce events, resolves customer identity across records, builds unified customer profiles, applies consent, and makes segments available to Marketing Cloud Engagement, Marketing Cloud Next, Marketing Cloud Personalization, Real-Time Offer Management, and Agentforce agents.

The separation matters architecturally. Commerce and marketing remain distinct systems. Data 360 does not merge them; it makes commerce data available to the marketing and AI layer in the form each can use.

What is Salesforce Marketing Cloud?

Salesforce Marketing Cloud is Salesforce’s cross-channel communication platform, covering email, SMS, push notifications, web personalization, and advertising. It manages the when, what, and who of customer communications, but only as well as the data feeding into it.

Salesforce Commerce Cloud (SFCC) is Salesforce’s commerce platform for online storefronts, B2B buying portals, order management, and payments. In 2026, Salesforce rebranded it as Agentforce Commerce, reflecting a shift toward AI agents and real-time decisioning. The underlying platform capabilities remain; the name has changed.

When the two systems connect, SFCC’s commerce activity becomes available to Marketing Cloud as context for every communication it sends.

The role of Data 360 in this architecture

Data 360, Salesforce’s current name for what was previously called Data Cloud, sits between SFCC and Marketing Cloud in most enterprise implementations. It is not a connector in the traditional sense. It is the layer that resolves customer identity, builds unified profiles, manages consent, and makes calculated segments available to Marketing Cloud and Agentforce agents.

A typical data flow works as follows:

1. SFCC generates events across cart, order, fulfillment, return, and support activity
2. These events reach Data 360 through APIs or platform event integrations
3. Data 360 resolves customer identities and builds unified profiles and segments
4. Marketing Cloud Engagement or Marketing Cloud Next uses those profiles for scheduled and triggered communications
5. Personalization, Real-Time Offer Management, and Agentforce agents use live customer and commerce context for real-time decisions

The exact configuration depends on the Salesforce products, licenses, and data model in use. Confirm the current setup in the Salesforce org before planning any integration, as documentation may reflect earlier naming conventions.

Four architecture questions to answer before designing use cases

When use case design precedes architecture, the problems are predictable: cart abandonment journeys fire on yesterday’s data, post-purchase sequences trigger before fulfillment events have reached Marketing Cloud, and personalization defaults to generic content because session-level signals from SFCC are not yet available. The fix in each case is at the data layer, not the campaign layer.

Four questions determine whether the integration will support the use cases planned for it:

• Identity: How does the Contact Key or Subscriber Key in Marketing Cloud map to the customer record in SFCC? If they do not map cleanly, unified profiles in Data 360 cannot be built reliably.
• Consent: Where are opt-ins and opt-outs captured, and how do they propagate across Marketing Cloud, SFCC, and Data 360? A customer who unsubscribes must be suppressed across all channels before the next send.
• Trigger method: Which events require real-time API or platform event integration, and which can tolerate batch movement? Cart and order events generally need near-real-time triggers. Catalog data and purchase history can move in scheduled batches.
• Failure handling: What happens when a commerce event fails to reach Data 360 before a journey trigger fires? Retry logic, queues, and reconciliation need design before launch, not after the first production failure.

SFCC and Marketing Cloud integration: key use cases

1. Abandoned cart recovery

When a customer leaves without completing a purchase, SFCC holds that cart event. Marketing Cloud can trigger a recovery communication, but only after cart status has reached Data 360 and the relevant segment has been updated.

A context-aware sequence also checks whether the customer purchased the item on another device before the trigger sends. Without cross-channel identity resolution in Data 360, that check cannot happen.

What this requires technically: API or platform event integration for cart events; cross-channel identity resolution in Data 360; suppression logic for post-purchase states.

A mid-market UK-based retailer that connected Marketing Cloud with SFCC event triggers moved from a 24-hour batch cycle to near-real-time cart detection, reducing the window in which a competitor could reach the customer first.

2. Post-purchase communications

Order and fulfillment events from SFCC, covering confirmation, dispatch, delivery, and returns, can trigger precise moments in a post-purchase journey. A customer whose order shipped today receives a dispatch update. One who initiated a return receives a resolution sequence, not a cross-sell.

What this requires technically: Fulfillment event integration between SFCC and Data 360; journey design that branches on order status rather than elapsed time.

Post-purchase is one of the most direct personalization opportunities available: the customer’s intent is confirmed, the product is known, and the communication can branch on what actually happened to the order.

3. Replenishment and loyalty

Purchase history and product lifecycle data from SFCC give Marketing Cloud what it needs to estimate when a repeat purchase is due. For consumable products, reminders timed to individual cadence outperform fixed-schedule sends.

Loyalty tier data from SFCC flowing into Data 360 means tier-based communications reflect actual status at the moment of sending, not the previous week’s export. Tier upgrades can trigger on the commerce event itself.

What this requires technically: Historical purchase data in Data 360; calculated fields for purchase cadence; loyalty tier data synchronized from SFCC.

A Singapore-based multi-vendor health and wellness platform connected its SFCC commerce events to marketing journeys, enabling personalized benefit tracking and product communications for employees across multiple vendor offerings.

4. Real-time offer management

Real-Time Offer Management evaluates which offer suits a specific customer at a specific moment, using live SFCC commerce and profile data. A customer browsing premium sees a different offer from one browsing clearance. A loyalty member near their next tier threshold receives an offer calibrated to that status rather than a generic promotion.

The offer decision requires the customer’s current session context and live commerce state. Batch data cannot support it.

What this requires technically: Real-time behavioral signals from SFCC; offer decisioning rules in Real-Time Offer Management; API integration between the commerce session and the offer layer.

5. Consent management across platforms

Connecting SFCC and Marketing Cloud creates a shared view of customer activity, which makes consent management a core architecture requirement, not an afterthought. Opt-ins and opt-outs captured at any touchpoint, whether at checkout, on a preference centre, or through an unsubscribe link, must propagate across both platforms before the next communication sends.

Data 360 provides a central layer for managing identity and consent across systems. Without it, a customer who unsubscribes from email in Marketing Cloud may still be reachable from a SFCC-triggered journey that has not received the suppression update.

What this requires technically: Centralized consent records in Data 360; suppression logic applied before every send; propagation design that accounts for GDPR, PDPA, and CCPA requirements relevant to the business’s operating markets.

6. Agentforce in commerce conversations

The SFCC and Marketing Cloud integration now extends into agentic AI, a capability that was not available in earlier configurations. Agentforce agents use unified customer and commerce data to support shoppers and buyers in real time.

A Shopper Agent surfaces relevant products based on purchase history, current cart, and browsing session. A Buyer Agent in B2B contexts answers order status questions, recommends reorder quantities based on purchase cadence, and routes complex queries to human teams.

Einstein capabilities also support AI-assisted product discovery, using search and browsing history, previous purchases, device and session context, and campaign signals to surface relevant products and content. Both Agentforce and Einstein use cases depend on the same unified customer and commerce context that Data 360 provides.

What this requires technically: Agentforce agent configuration with access to unified customer profile and live SFCC order data through Data 360; Einstein product recommendations enabled on the commerce and marketing layer.

Integration Checklist for Existing SFCC and SFMC Customers

Businesses already using Salesforce Commerce Cloud (SFCC) and Salesforce Marketing Cloud (SFMC) can review the following areas when updating their integration approach.

1. Inventory Current Integrations

• Map existing APIs, SFTP jobs, connectors, and custom code.
• Identify the Marketing Cloud products currently in use, such as Marketing Cloud Engagement, Personalization, or Intelligence.
• Document which systems currently provide customer, product, order, and behavioral data.

2. Review Naming and Product Configuration

• Confirm whether the organization uses Data Cloud or Data 360 terminology in its current Salesforce setup.
• Review the Marketing Cloud products and licenses currently available.
• Confirm how the organization plans to refer to Commerce Cloud and Agentforce Commerce in internal and external communications.

3. Review Identity and Consent

• Check how Contact Key or Subscriber Key maps to Commerce customer IDs.
• Confirm that consent and communication preferences are transferred correctly between systems.
• Assess whether Data 360 identity resolution is required for the current architecture.

4. Evaluate the Architecture

• Identify integrations that depend only on scheduled batch transfers.
• Assess where APIs or event-based integrations could support more timely data movement.
• Determine whether Data 360 can replace or supplement existing customer data processes.
• Review whether Personalization or Real-Time Offer Management fits the planned use cases.

5. Prioritize AI and Agent Use Cases

Start with use cases that have clear business requirements and measurable outcomes.

Examples include:

• Abandoned cart campaigns
• Post-purchase communications
• Replenishment reminders
• Conversational commerce
• Shopper Agent or Buyer Agent pilots

Define metrics such as conversion rate, average order value, retention, and customer satisfaction before starting a pilot.

6. Review Governance and Security

• Review access controls and data retention requirements.
• Confirm how customer consent and data usage are managed.
• Document data flows between Commerce, Marketing Cloud, Data 360, CRM, and other connected systems.
• Maintain records of integration points for security reviews and future audits.
• Integration challenges and how to address them