SAP Engagement Cloud (Emarsys) Setup: An 8-Step Implementation Guide

Setting up SAP Engagement Cloud (formerly SAP Emarsys) takes eight steps and, for email plus one SAP system, six to ten weeks. None of the steps is complicated, but the order matters: if you skip the domain configuration or the data mapping, you spend weeks chasing deliverability problems or broken personalisation tokens afterwards.

SAP renamed Emarsys to SAP Engagement Cloud in February 2026; the existing product continues as the Emarsys edition, and the setup described here applies to it. Many component names (Web Extend, Smart Insight, the Emarsys SDK) still carry the old label. We have run this process in SAP Commerce and S/4HANA projects for customers of different sizes.

TL;DR: An Engagement Cloud implementation runs through 8 steps in 6 to 10 weeks: tenant configuration, sending domain, link tracking, web tracking and identification, currency and web domains, channel activation, sales data provisioning and the first campaigns. The critical path runs through the sending domain (SPF, DKIM, DMARC, IP warm-up) and the data integration. Start with email and add SMS and push once the core is stable.

What does the setup look like end to end?

SAP’s integration guide for Engagement Cloud lists the connectors and APIs; the prebuilt SAP integrations save a lot of custom work, but the groundwork below still has to be done properly. Here are the eight steps.

Step 1: Tenant configuration

Everything starts with provisioning your tenant: the isolated environment where your account, data and campaigns live. You provide:

• Company details and billing information
• A primary contact for the account
• The preferred data centre region (for Swiss and EU companies, the EU)
• Initial channel requirements (email is standard; SMS and push are add-ons)

The handover form from SAP is submitted through your implementation partner or the SAP for Me customer portal. Plan a few business days.

Step 2: Email and sending domain

This step decides whether your launch works. Poor domain configuration is the most common cause of deliverability problems we see.

What you need:

• A dedicated sending subdomain (for example mail.yourcompany.com), not your primary domain
• An SPF record that includes the Engagement Cloud sending infrastructure
• DKIM keys generated in Engagement Cloud and published in your DNS
• A DMARC policy, starting with p=none and tightened to p=quarantine after warm-up
• MX records for bounce handling

Why the subdomain matters: if anything goes wrong during IP warm-up, only the subdomain takes the hit and the reputation of your main domain stays clean. Companies that skip this can damage the sender reputation of the domain their whole business mails from, and repairing that takes months.

IP warm-up: Engagement Cloud guides you through a structured warm-up, increasing send volumes over two to four weeks. This builds reputation with inbox providers (Gmail, Outlook, Yahoo) and decides whether you land in the inbox or the spam folder.

Step 3: Link tracking and unsubscription

Set up tracking parameters so campaign data flows cleanly into your analytics:

• UTM parameters: add utm_source, utm_medium, utm_campaign and utm_content to all campaign links for visibility in Google Analytics
• Custom tracking domains: branded link domains (for example track.yourcompany.com) instead of generic tracking URLs
• List-Unsubscribe headers: required for compliance, and Google’s sender guidelines require one-click unsubscribe for bulk senders

If you manage unsubscriptions outside Engagement Cloud in your own preference centre, configure a custom List-Unsubscribe URL with contact and campaign identification parameters.

Step 4: Web Extend and user identification

Web Extend is the platform’s web tracking script, built for segmentation rather than for general web analytics. Install it on all pages of your website to track:

• Page views and product browsing
• Cart additions and abandonments
• Search queries
• Custom events

Decide how visitors are identified: by email address (hashed) or by a custom identifier from your system. The right choice depends on your login flow. If most visitors are logged in, use your CRM ID. If most browse anonymously, use email with a cookie-based fallback.

Step 5: Currency and web channel domains

Two settings that are routinely overlooked:

• Currency: select the primary currency for purchase tracking. There is one primary currency per account, so if you sell in CHF and EUR, decide which one becomes your reporting baseline.
• Web domains: register all domains and subdomains that use the Web Channel (personalised website content). The Web Extend script must be on each of them.

Step 6: Channel activation

Email is active by default. Every other channel needs its own setup:

• SMS: provide your preferred SMS gateway or use the built-in capability. It needs opt-in data and compliance with local SMS rules, which are stricter than for email in most countries.
• Push notifications: configure your app’s push certificate (iOS) and Firebase key (Android). This requires the Emarsys mobile SDK in your app.
• Web push: browser-based push needs the web push SDK and a service worker on your site.

Our advice: start with email and get it stable. Add SMS and push once email runs reliably and produces results. Launching all channels at once multiplies the complexity without a proportional payoff, and when something breaks, nobody can tell which channel caused it.

Step 7: Sales data provisioning

This step brings your transaction data into Engagement Cloud for revenue attribution and purchase-based segmentation.

Recommended method: the Sales Data API. It uploads your sales data file over HTTPS and validates it during the upload, so errors surface immediately. SAP asks for a daily upload of the most recent contact, purchase and product data. Each line carries a customer identifier, product ID, quantity, value and date.

Alternative: SFTP upload. It is a legacy option: simpler to set up, but without validation during upload, and according to SAP, sales data uploaded via SFTP does not feed product recommendations.

If you run SAP Commerce Cloud, the prebuilt connector sends order events to Engagement Cloud in near real time without custom development. If your orders come from an ERP, typically S/4HANA, the same sales data upload is fed from the ERP; we describe that pattern in marketing on real revenue.

Step 8: First campaign launch

The infrastructure is in place, so it is time to go live. We recommend starting with:

1. A welcome email. It triggers on new contact registration, is low risk and proves immediately that your data flow works.
2. An abandoned-cart email. It triggers when someone adds products but does not complete the purchase, and validates the commerce integration and personalisation tokens.
3. A post-purchase follow-up. It triggers after the order confirmation and validates the transaction data flow and timing logic.

All three use pre-built tactics, so you configure proven programmes rather than building them from scratch.

What are the most common setup mistakes?

Most delayed launches we see come down to data quality and sequencing, not to the platform. These are the five mistakes we keep running into.

Skipping IP warm-up. Sending 100’000 emails on day one from a fresh IP sends you straight to the spam folder. Follow the warm-up schedule. It takes two to four weeks, and that is the price of long-term deliverability.

Sending from your primary domain. If warm-up goes wrong, your main domain’s reputation takes the hit. Always use a dedicated subdomain.

Importing dirty data. Duplicate contacts, invalid email addresses and contacts without consent records all cause immediate problems: high bounce rates, low engagement and compliance risk. Clean your data before the import. Of all the causes of delayed launches, this is the one we see most often.

Launching all channels at once. Get email working first: validate the data flows, test personalisation, confirm deliverability. Then add SMS, push and web. A parallel launch multiplies complexity and makes troubleshooting slow.

Postponing Web Extend. Without web tracking, Engagement Cloud cannot build behaviour-based segments or trigger browse-abandonment programmes. Install it early, even if you will not use those features right away.

If you are still deciding whether Engagement Cloud is the right platform at all, our comparison with standalone marketing automation tools and the pricing and cost guide cover that decision. For choosing an implementation partner, see our guide to Engagement Cloud partners in Switzerland and DACH.

FAQ

How long does a standard Engagement Cloud implementation take?

Six to ten weeks for email with one SAP system integration (typically Commerce Cloud). SMS adds one to two weeks. Push notifications need mobile SDK integration, which adds two to four weeks depending on the app. The critical path usually runs through the domain configuration and IP warm-up.

Do I need a technical team for the setup?

You need someone who can change DNS records (SPF, DKIM, DMARC) and install JavaScript tracking scripts. With SAP Commerce Cloud, the prebuilt connector keeps custom development to a minimum. Non-SAP systems need API integration work. An implementation partner handles the configuration on the Engagement Cloud side.

What data should I prepare before starting?

At minimum: clean contact data (email, name, consent status), the product catalogue (brand, category, price) and historical sales data (orders with customer IDs, product IDs and revenue). The quality of this data determines how fast personalised campaigns can run. Remove duplicates and invalid addresses before the import.

Can I start with email only and add channels later?

Yes, and we recommend exactly that. Email is the foundation: get deliverability right, validate the data integration, test personalisation tokens and launch the first automations. Add SMS after four to six weeks once email is stable. Push notifications can follow and need the mobile SDK in your app.

What is different when implementing Engagement Cloud for SAP Commerce customers?

The prebuilt SAP Commerce connector covers the product catalogue sync, order event triggers, customer registration and cart abandonment detection. That saves weeks of custom API work. For non-SAP commerce platforms, you build those data flows yourself through the Engagement Cloud API.