SAP Emarsys Customer Engagement Implementation Consultant cheat sheet

SAP Emarsys Customer Engagement Implementation

• Implementation works in a fixed order: account provisioning, database and field setup, contact import and deduplication, channel configuration (email, SMS, mobile push), automation and lifecycle programs, then reporting and integrations.

• The contact database is the system of record: every implementation decision about field types, opt-in status, and unique identifiers (email, external ID) propagates to segmentation, personalization, and automation, so define them before any import.

• Contact fields are typed (text, number, date, single/multi-select); custom fields must be created before importing data that references them, and field changes after import require a re-mapping of segments and personalization tokens.

• Opt-in is stored per channel and per contact; consent status must be captured at import and enforced by the send engine, and the implementation must define the opt-in source, timestamp, and withdrawal handling.

• Email sender configuration requires domain authentication (SPF, DKIM, DMARC alignment) and a verified sending domain; link tracking and image hosting use branded tracking domains that must be CNAME-configured before launch.

• Segmentation combines contact criteria, behavioral filters (opens, clicks, purchases), and relational data; segment definitions should be documented with their field dependencies so schema changes can be impact-assessed.

• Automation programs are node-based: entry criteria, wait nodes, decision nodes, and actions; each program must have a defined re-entry policy and an exit condition to prevent duplicate or runaway sends.

• Integrations (webshop, CRM, product catalog, SAP systems) typically use REST APIs or file-based feeds; the implementation must define sync frequency, idempotency keys, and error handling for failed contact or event updates.

• Testing and go-live: seed-list testing, rendering checks across clients, deliverability warm-up of new sending domains, and a rollback plan for automation and data feeds are part of the implementation checklist.