SAP Engagement Cloud (Formerly SAP Emarsys): What It Does, How It Works, and When You Need It

Most marketing platforms hand you tools and wish you luck. SAP Engagement Cloud (formerly SAP Emarsys) hands you tactics: ready-made campaign programmes with the timing, channel choice and personalisation logic already worked out. That difference decides how quickly a marketing team gets from “platform configured” to “campaigns earning money”.

TL;DR: SAP Engagement Cloud is SAP’s omnichannel engagement platform, known as SAP Emarsys until SAP renamed it on 19 February 2026. It runs email, SMS, mobile push and in-app, web personalisation, wallet and ad audiences from one customer profile, ships a library of pre-built tactics, and ties campaigns to real revenue. It pays off most for B2C and B2B2C companies that already run SAP Commerce Cloud, S/4HANA or SAP CDP, because that is where the customer data it acts on lives.

What is SAP Engagement Cloud?

SAP Engagement Cloud is the marketing execution layer of the SAP CX portfolio. SAP acquired Emarsys in 2020 and renamed the product SAP Engagement Cloud on 19 February 2026. The rename came with a second edition: the existing product continues as the Emarsys edition, and a new enterprise edition adds governance for organisations with many brands, regions and teams. SAP states that existing Emarsys capabilities remain available and customers adopt new ones at their own pace. We cover the rename in detail in SAP Emarsys is now SAP Engagement Cloud and the edition choice in our Emarsys edition vs enterprise edition comparison.

In the same announcement SAP noted that the platform is recognised in the 2026 Gartner Magic Quadrant for Personalization Engines, and positioned it around data from SAP Business Data Cloud. The product documentation lives on the SAP Help Portal.

What makes it different from other marketing platforms?

Three things, in our project experience.

Pre-built tactics. Instead of a blank canvas, Engagement Cloud offers a library of ready-to-activate programmes organised by objective (acquisition, retention, win-back, revenue). An abandoned-cart tactic is not an email template: it is a complete automation with trigger, channel sequence, timing and personalisation rules. You adapt the messaging, branding and incentives, then launch. The tactics library is also the most underused feature we see: teams spend weeks building flows that already exist.

One profile across channels. Every channel works from the same contact profile and the same segments. A customer who ignores push but reads email is reached by email, and a customer who has just bought does not get the abandoned-cart reminder.

Revenue attribution from real transactions. Engagement Cloud matches campaign touchpoints to purchase data from your commerce platform or ERP. You report revenue per campaign and channel, not only opens and clicks, which changes the conversation with finance.

What are the core capabilities?

Omnichannel campaigns

• Email for batch campaigns, triggered journeys and transactional messages
• SMS for promotional and service messages
• Mobile push and in-app for app users
• Web personalisation with dynamic content on your site
• Mobile wallet passes
• Ad audiences synchronised to Google, Meta and other ad platforms

Dynamic segmentation

Segments combine contact properties, email behaviour, purchase history, web behaviour, loyalty data and lifecycle stage, and they recalculate whenever a campaign runs. “Gold members who browsed winter coats twice but have not purchased in 30 days” is a single segment that maintains itself.

AI-supported personalisation

Engagement Cloud uses machine learning on your own customer data for product recommendations, individual send-time optimisation and predictive segments such as purchase probability or churn risk. These models improve as behavioural and transaction data accumulates, so data quality matters more than any single feature.

Revenue analytics

Every campaign reports its attributed revenue alongside deliverability and engagement metrics. That is what lets marketing argue with numbers from the order system rather than with proxy metrics.

How do you build a campaign in SAP Engagement Cloud?

The biggest mistake we see is jumping straight to campaign creation before the segmentation and data are right. The workflow that works has four steps.

1. Build the segments. Start from the data you trust: purchase history, lifecycle stage, consent status. Dynamic segments stay current without manual exports.
2. Choose the campaign type. Batch campaigns go to a segment at a scheduled time (launches, seasonal promotions, newsletters) and support A/B tests. Triggered campaigns fire on an event: abandoned cart, first purchase, loyalty milestone, 60 days of silence. They consistently outperform batch sends because they arrive at the relevant moment. Transactional messages (order confirmations, shipping notices) use the same personalisation engine.
3. Personalise the content. The visual editor needs no code, and conditional content blocks show different content to different segments in one template. With SAP data connected, content can use the points balance from SAP Loyalty, recently viewed products from Commerce Cloud or order status from S/4HANA.
4. Set timing and channel order. Send-time optimisation picks each contact’s best time. For omnichannel journeys you define the cascade: no email open within 24 hours, then SMS, then push.

For the full implementation sequence, see our 8-step SAP Emarsys setup guide.

Which tactics should you activate first?

• Acquisition: welcome series, first-purchase incentive for browsers who do not buy, referral activation
• Retention: post-purchase follow-up, birthday and anniversary messages, loyalty tier nudges (“200 points to Gold”), re-engagement at 30, 60 and 90 days of inactivity
• Win-back: graduated offers for lapsed customers, expiring points reminders
• Revenue: abandoned cart, browse abandonment, replenishment reminders for consumables, price-drop alerts for wish-listed items

Our usual order: welcome series, abandoned cart and post-purchase first, because they rely on data every shop has and show results within weeks.

How do you measure success?

Look at four layers, in this order:

• Deliverability: delivered, soft and hard bounces, blocks. If messages do not reach the inbox, nothing else matters. Plan domain authentication (SPF, DKIM, DMARC) and IP warm-up before the first large send.
• Engagement: opens, clicks, unsubscribes, and their pattern by time of day.
• Revenue: attributed revenue per campaign and channel from real transactions.
• Lifecycle impact: did the win-back programme reactivate lapsed customers, did the post-purchase series raise repeat purchases?

How does SAP Engagement Cloud build customer loyalty?

Loyalty that makes a customer choose you over a cheaper alternative comes from relevance, not from discount codes. Engagement Cloud makes relevance operational in three ways.

Lifecycle stages. Every contact is placed automatically in a stage (lead, first-time buyer, active, at risk, churned) based on purchase frequency, recency and engagement. A first-time buyer gets a proper welcome, a customer who has been quiet for 90 days gets a reason to come back, and nobody has to maintain the lists.

Predictive signals. Purchase probability, churn risk and preferred channel let you act before a customer leaves rather than after. That shift from reactive win-back to proactive retention changes how a marketing team plans.

Connection to SAP Loyalty. With SAP Loyalty and SAP CDP connected, tier upgrades, reward thresholds and expiring points trigger the right campaign automatically, and every message can carry the live points balance and the distance to the next tier. A points programme stops being a cost centre and becomes a retention engine. Engagement Cloud also works without a formal loyalty programme: purchase history and lifecycle stage are enough to run retention.

The retention tactics we deploy most: a post-purchase series (confirmation, delivery, care tips, cross-sell, review request), milestone messages, a re-engagement cascade in which each step fires only if the previous one did not convert, replenishment reminders based on average repurchase cycles, and win-back offers built from the customer’s own purchase and browsing history.

How does it fit into the SAP landscape?

Engagement Cloud acts on data that lives elsewhere, so its value depends on the connections:

• SAP Commerce Cloud: product catalogue, cart and order events feed abandoned-cart triggers, recommendations and revenue attribution. This is the pattern we implement most often and the one that pays off fastest.
• S/4HANA: order history, delivery status and customer master data make campaigns reflect what actually happened. We describe the pattern in feeding Engagement Cloud with sales data from S/4HANA Public Cloud.
• SAP Customer Data Platform: unified profiles and audiences from sources outside marketing (service, offline purchases, web). See when you actually need SAP CDP.
• SAP Customer Data Cloud: consent captured at registration applies to every campaign, so compliance with GDPR and the Swiss nFADP is built in rather than audited afterwards. More in our Customer Data Cloud guide.

None of these connections is free. Plan the data mapping, consent model, error handling and monitoring for each one before you compare total cost with a standalone tool. At Miltenyi Biotec we integrated marketing with Commerce Cloud, Customer Data Cloud, S/4HANA and Service Cloud V2 into one landscape, and the integration work, not the campaign tooling, set the pace.

Who is SAP Engagement Cloud built for?

A good fit:

• B2C and B2B2C brands running SAP Commerce Cloud, S/4HANA or SAP CDP
• Companies with large contact bases active across several channels
• Marketing teams that want proven tactics instead of building everything from zero
• Businesses that need revenue attribution tied to ERP transactions

Probably not the right fit:

• Small teams with email-only needs, where a simpler tool is cheaper
• Non-SAP companies with no plans for SAP, because the integration advantage disappears
• Mobile-app-first brands whose engagement is almost entirely push and in-app

For the comparison with standalone tools, read SAP Emarsys vs standalone marketing automation; for budgets, our SAP Engagement Cloud pricing guide. If you are choosing an implementation partner, our overview of SAP Engagement Cloud partners in Switzerland and DACH lists the criteria that matter. Spadoom connects Engagement Cloud to the commerce and ERP data it depends on, with one team for both sides; see our SAP Engagement Cloud solution page or talk to us.

For Swiss companies, our page on SAP CX consulting in Switzerland shows how SAP Engagement Cloud fits into a CX landscape we deliver with one team.

FAQ

Is SAP Engagement Cloud the same as SAP Emarsys?

Yes. SAP renamed SAP Emarsys to SAP Engagement Cloud on 19 February 2026. The existing product continues as the Emarsys edition with the same features and integrations, and a new enterprise edition adds governance for multi-brand, multi-region organisations.

How does it differ from a standard email marketing tool?

An email tool covers one channel. SAP Engagement Cloud runs email, SMS, push, in-app, web, wallet and ad audiences from one customer profile, ships pre-built tactics rather than templates, adds AI-supported recommendations and send-time optimisation, and attributes revenue from real commerce or ERP transactions.

Does SAP Engagement Cloud require SAP Commerce Cloud?

No. It works with other e-commerce platforms through APIs and connectors. Its strongest advantages (catalogue sync, real-time order events, ERP-linked revenue attribution) come from SAP data, so without SAP the case rests on the marketing features alone.

What types of campaigns can I run?

Batch campaigns to a segment at a scheduled time, triggered campaigns that react to events such as cart abandonment or a tier change, and transactional messages such as order confirmations. Triggered campaigns usually perform best because they arrive at the moment they are relevant.

Can it improve retention without a loyalty programme?

Yes. Lifecycle stages, purchase history, browsing behaviour and churn prediction drive retention campaigns on their own. Connecting SAP Loyalty adds points, tiers and rewards as extra triggers and personalisation data.

How long does an implementation take?

A standard setup with account configuration, data integration, first tactics and training typically takes 6 to 10 weeks. Projects that integrate SAP Commerce Cloud, S/4HANA and several channels take longer, typically 10 to 16 weeks, depending mainly on data quality and the number of integrations.