SAP Emarsys Setup: An 8-Step Implementation Guide

Setting up Emarsys isn’t complicated. But it is methodical, and if you skip a step (especially domain config or data mapping), you’ll spend weeks chasing deliverability problems or broken personalisation tokens. I’ve seen it happen enough to know exactly where things go sideways.

We’ve done this across SAP Commerce and S/4HANA projects for clients of different sizes. This is the 8-step process from account creation to your first live campaign.

TL;DR: Emarsys implementation takes 6–10 weeks across 8 steps: tenant configuration, domain setup, tracking configuration, web identification, currency/domain settings, channel activation, data provisioning, and first campaign launch. The critical path runs through domain configuration (SPF/DKIM/DMARC) and data integration — getting these wrong delays everything downstream. Start with email, add SMS and push after the core is stable.

What Does Emarsys Setup Look Like End to End?

Gartner estimates the average enterprise spends 33% of its marketing technology budget on integration and maintenance (Gartner, 2024). Emarsys cuts that with native SAP connectors, but the initial setup still needs doing properly. Here are the 8 steps.

Step 1: Tenant configuration

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

• Company details and billing information
• Primary contact for the account
• Preferred data centre region (EU or US)
• Initial channel requirements (email is standard; SMS and push are add-ons)

You fill out a handover form from SAP and submit it through your implementation partner or the SAP for Me customer portal. Expect 2-3 business days.

Step 2: Email and domain setup

This step makes or breaks your launch. Poor domain configuration is the single biggest cause of deliverability problems. Full stop.

What you need:

• A dedicated sending subdomain (e.g., mail.yourcompany.com). Don’t use your primary domain.
• SPF record pointing to Emarsys sending infrastructure
• DKIM keys generated by Emarsys and published in your DNS
• DMARC policy set to at least p=none initially, tightening to p=quarantine after warm-up
• MX records for bounce handling

Why a subdomain matters: if anything goes wrong during IP warm-up, only the subdomain takes the hit. Your primary domain reputation stays clean. I’ve seen companies skip this and torch their main domain’s sender reputation. Not a fun conversation to have with the CTO.

IP warm-up: Emarsys walks you through a structured warm-up programme, gradually increasing send volumes over 2-4 weeks. This builds reputation with inbox providers (Gmail, Outlook, Yahoo) and is the difference between landing in the inbox versus the spam folder.

Step 3: Link tracking and unsubscription

Get your tracking parameters right so campaign data flows cleanly into analytics:

• UTM parameters: attach utm_source, utm_medium, utm_campaign, and utm_content to all campaign links for Google Analytics visibility
• Custom tracking domains: branded link domains (e.g., track.yourcompany.com) instead of generic Emarsys tracking URLs
• List-Unsubscribe headers: required for compliance and increasingly enforced by inbox providers (Google now requires it for bulk senders)

If you manage unsubscriptions outside Emarsys through your own preference centre, configure a custom List-Unsubscribe URL with user and campaign identification parameters.

Step 4: Web Extend and user identification

Web Extend is Emarsys’s web tracking script. Think of it as Google Analytics’ purpose-built cousin for Emarsys segmentation. Install it on all your website pages to track:

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

User identification matters. Pick how Emarsys identifies visitors: email address (hashed for privacy) or a custom identifier from your system. The right pick depends on your login flow. If most visitors are authenticated, use your CRM ID. If most browse anonymously, go with email plus a cookie-based fallback.

Step 5: Currency and web channel domains

Two config items people routinely overlook:

• Currency: select your primary currency for purchase tracking. Emarsys supports one primary currency per account. If you sell in multiple currencies, decide which one becomes your reporting baseline.
• Web domains: register all domains and subdomains that use the Emarsys Web Channel (personalised website content). The Web Extend script needs to be on each one.

Step 6: Channel activation

Email activates by default. Everything else needs its own setup:

• SMS: provide your preferred SMS gateway or use Emarsys’s built-in capability. Needs opt-in data and compliance with local SMS regulations (stricter than email in most countries).
• Push notifications: configure your mobile app’s push certificate (iOS) and Firebase key (Android). Requires the Emarsys Mobile SDK in your app.
• Web push: browser-based push needs Web Push SDK setup and a service worker on your site.

My advice: start with email. Get it solid. Add SMS and push once email is stable and producing results. Launching all channels at once multiplies complexity without a proportional payoff. I’ve watched teams drown trying to do it all simultaneously.

Step 7: Sales data provisioning

This wires your transaction data into Emarsys for revenue attribution and purchase-based segmentation.

Recommended method: Sales Data API. Sends real-time transaction data to Emarsys with immediate validation and privacy compliance. Each order includes customer identifier, product IDs, quantities, and revenue.

Alternative: SFTP file upload. Batch uploads on a schedule (hourly or daily). Simpler to set up but introduces lag between purchase and data availability.

If you’re on SAP Commerce Cloud: the native connector handles this automatically. Order events flow to Emarsys in real time without custom development. Neat.

Step 8: First campaign launch

Infrastructure is in place. Time to go live. We recommend starting with:

1. A welcome email. Triggers on new contact registration. Simple, low risk, and it immediately proves your data flow works.
2. An abandoned cart email. Triggers when someone adds products but doesn’t complete purchase. Validates commerce integration and personalisation tokens.
3. A post-purchase follow-up. Triggers after order confirmation. Validates transaction data flow and timing logic.

Each of these uses Emarsys’s pre-built tactics, so you’re configuring proven strategies rather than building from scratch.

What Are the Most Common Setup Mistakes?

Gartner found that organisations with clean, well-governed customer data achieve 70% faster time-to-value on marketing technology investments (Gartner, 2024). The flip side: dodgy data quality is the biggest setup blocker. Here’s what we keep running into.

Skipping IP warm-up. Sending 100,000 emails on day one from a fresh IP is a guaranteed trip to the spam folder. Follow the warm-up schedule. Yes, it takes 2-4 weeks. That’s the price of long-term deliverability.

Using your primary domain for sending. If warm-up goes sideways, your main domain’s reputation takes the hit. Always use a dedicated subdomain. Always.

Importing dirty data. Duplicate contacts, invalid emails, contacts without consent records. They all create immediate problems. High bounce rates, low engagement, compliance risk. Clean your data before importing into Emarsys. I reckon this one mistake accounts for more delayed launches than anything else we see.

Launching all channels at once. Get email working first. Validate data flows, test personalisation, confirm deliverability. Then bring in SMS, push, and web. Parallel launch multiplies complexity and makes troubleshooting a nightmare.

Ignoring Web Extend installation. Without web tracking, Emarsys can’t build behaviour-based segments or trigger browse abandonment campaigns. Install it early, even if you’re not using those features right away.

FAQ

How long does a standard Emarsys implementation take?

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

Do I need a technical team for setup?

You need someone who can modify DNS records (SPF, DKIM, DMARC) and install JavaScript tracking scripts. If you’re integrating with SAP Commerce Cloud, the native connector keeps custom dev to a minimum. For non-SAP systems, you’ll need API integration work. An implementation partner handles the Emarsys-side configuration.

What data should I prepare before starting?

At minimum: clean contact data (email, name, consent status), product catalogue (brand, category, price), and historical sales data (orders with customer IDs, product IDs, revenue). The quality of your data directly determines how fast you can get personalised campaigns running. Remove duplicates and invalid emails before 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 data integration, test personalisation tokens, launch your first automations. Add SMS after 4-6 weeks once email is solid. Push notifications can follow and need mobile app SDK integration.

What’s different about implementing Emarsys for SAP Commerce clients?

The native SAP Commerce connector pre-builds the product catalogue sync, order event triggers, customer registration flow, and cart abandonment detection. That cuts out weeks of custom API work. For non-SAP commerce platforms, you’d build those data flows manually through the Emarsys API.