SAP Emarsys Setup: An 8-Step Implementation Guide

Setting up Emarsys isn’t complicated, but it’s methodical. Skip a step — especially domain configuration or data mapping — and you’ll spend weeks troubleshooting deliverability issues or broken personalisation tokens.

This guide walks through the 8-step process from account creation to first campaign. It’s based on what we’ve learned implementing Emarsys for SAP Commerce and S/4HANA clients.

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 that the average enterprise spends 33% of its marketing technology budget on integration and maintenance (Gartner, 2024). Emarsys reduces that burden through native SAP connectors — but the initial setup still needs to be done right. Here are the 8 steps.

Step 1: Tenant configuration

Your Emarsys journey starts with provisioning your tenant — the isolated environment where your account, data, and campaigns live. You’ll provide:

• 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 optional add-ons)

You’ll complete a handover form provided by SAP and submit it to your implementation partner or through the SAP for Me customer portal. This typically takes 2–3 business days to process.

Step 2: Email and domain setup

This is the most critical technical step. Poor domain configuration is the single biggest cause of deliverability problems.

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 deliverability issues occur during IP warm-up, they affect only the subdomain — your primary domain reputation stays clean. We’ve seen companies skip this step and damage their main domain’s sender reputation.

IP warm-up: Emarsys guides 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 essential for reaching inbox rather than spam.

Step 3: Link tracking and unsubscription

Configure tracking parameters so campaign data flows correctly to your analytics tools:

• 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 — similar to Google Analytics, but purpose-built 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: Choose how Emarsys identifies visitors. Options are email address (hashed for privacy) or a custom identifier from your system. The right choice depends on your login flow — if most visitors are authenticated, use your CRM ID. If most browse anonymously, use email with cookie-based fallback.

Step 5: Currency and web channel domains

Two configuration items that are easy to overlook:

• Currency: Select your primary currency for purchase tracking. Emarsys supports one primary currency per account. If you operate in multiple currencies, decide which one serves as the reporting baseline.
• Web domains: Register all domains and subdomains that use the Emarsys Web Channel (personalised website content). The Web Extend script must be installed on each.

Step 6: Channel activation

Email activates by default. Additional channels require separate configuration:

• SMS: Provide your preferred SMS gateway or use Emarsys’s built-in SMS capability. Requires opt-in data and compliance with local SMS regulations (stricter than email in most jurisdictions).
• Push notifications: Configure your mobile app’s push certificate (iOS) and Firebase key (Android). Requires the Emarsys Mobile SDK integrated into your app.
• Web push: Browser-based push notifications require Web Push SDK setup and a service worker on your website.

Start with email. Add SMS and push after the email channel is stable and producing results. Trying to launch all channels simultaneously increases complexity without proportional benefit.

Step 7: Sales data provisioning

This step connects your transaction data to 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 of sales data on a scheduled basis (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.

Step 8: First campaign launch

With infrastructure in place, launch your first campaign. We recommend starting with:

1. A welcome email — triggers when a new contact registers. Simple, low risk, immediately validates your data flow.
2. An abandoned cart email — triggers when a customer 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). Conversely, poor data quality is the biggest setup blocker. Here’s what to avoid:

Skipping IP warm-up. Sending 100,000 emails on day one from a new IP guarantees spam folder placement. Follow the warm-up schedule — it takes 2–4 weeks but protects your long-term deliverability.

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

Importing dirty data. Duplicate contacts, invalid emails, and contacts without consent records create immediate problems — high bounce rates, low engagement, and compliance risk. Clean your data before importing it into Emarsys.

Launching all channels simultaneously. Get email working first. Validate your data flows, test personalisation, confirm deliverability. Then add SMS, push, and web. Parallel launch multiplies complexity and makes troubleshooting difficult.

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 immediately.

FAQ

How long does a standard Emarsys implementation take?

A standard implementation takes 6–10 weeks for email with one SAP system integration (typically Commerce Cloud). Adding SMS extends by 1–2 weeks. Push notifications require 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 minimises custom development. 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 quickly you can launch personalised campaigns. Remove duplicates and invalid emails before import.

Can I start with email only and add channels later?

Yes — and we recommend it. Email is the foundation. Get deliverability right, validate data integration, test personalisation tokens, and launch your first automated campaigns. Add SMS after 4–6 weeks once email is stable. Push notifications can come later and require 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. This eliminates weeks of custom API development. For non-SAP commerce platforms, you’d build these data flows manually via the Emarsys API.