Emarsys

SAP Emarsys is an omnichannel customer engagement platform for email, SMS, push, web, and direct mail with AI-driven personalisation.

Why route Emarsys through Datafly Signal

Profiles are updated from the server, not the browser. Events reach Emarsys even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Token lifecycle is handled for you. Signal obtains and refreshes the OAuth credentials Emarsys requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination. Emarsys is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Complete these steps in Emarsys before configuring Signal.

Access your Emarsys account

Create API credentials

Navigate to Admin > Security Settings > API Users. Click Create API User and configure:

Give it a username (e.g. datafly_signal).
Generate a password — store it securely.
Assign the Contact Management and External Events permissions at minimum.
Save.

Both the username (Wsse-Username) and password (used to compute Wsse-PasswordDigest) are required by Signal — the Wsse digest is computed automatically for each request.

Find your Customer ID

Your Emarsys Customer ID is shown in Admin > Account Settings. Copy it.

Identify your Contact Field IDs

Emarsys identifies contact fields by numeric IDs (not names). Common IDs:

Field	Standard ID
Email	`3`
First name	`1`
Last name	`2`
Customer ID (external)	`1234` (custom field — varies)

Navigate to Admin > Field Editor to confirm the IDs for your account.

Configuration

Field	Type	Required	Description
`api_username`	string	Yes	Emarsys API username (Wsse-Username).
`api_password`	secret	Yes	Emarsys API password (used in Wsse-PasswordDigest computation).
`customer_id`	string	Yes	Your Emarsys customer ID.
`key_field_id`	string	No	Numeric field ID used as the contact key. Defaults to `3` (email).

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Emarsys under the Marketing Automation category.
Click Install, and fill in the required fields with the credentials gathered above.
Click Install Integration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/emarsys/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Emarsys",
    "variant": "default",
    "config": {
      "api_username": "datafly_signal",
      "api_password": "xxxxxxxxxxxxxxxxxxxx",
      "customer_id": "12345",
      "key_field_id": "3"
    },
    "delivery_mode": "server_side"
  }'

API endpoint

POST https://api.emarsys.net/api/v3/event/{{event_id}}/trigger

Allow egress to api.emarsys.net from the network your delivery workers run on.

Event Mapping

Datafly Event	Emarsys Concept	Notes
`page`	External event	Sent via Trigger External Event API.
`Product Viewed`	External event	Forwarded with product properties.
`Order Completed`	External event with revenue	Mapped to a revenue-bearing external event.
`identify`	Contact update	Creates or updates the contact via Contact API.

Identity

Field	Source	Notes
`key_field` (email by default)	`traits.email`	The contact key. Field ID `3` by default.
`firstName`	`traits.first_name`	Maps to Emarsys field `1`.
`lastName`	`traits.last_name`	Maps to Emarsys field `2`.

Emarsys events should be sent under the marketing consent category. Emarsys maintains its own opt-in/opt-out records — Signal forwards the visitor’s CMP consent state so contact updates can include opt-in field changes when appropriate.

Verify it’s working

Trigger a test event from your website.
In Emarsys, navigate to Contacts > Search and look up the test contact by email.
View the contact’s External Events history to confirm Signal-delivered events.
In Signal, check Live Events to confirm delivery with a 200 response status.

Troubleshooting

Symptom	Possible Cause	Resolution
`401 Unauthorized`	Invalid Wsse credentials	Verify the API username and password in Admin > Security Settings > API Users.
`500 InvalidKeyField`	`key_field_id` doesn’t match Emarsys schema	Check the field ID in Admin > Field Editor and update the config.
Contact not created	Missing required fields	Ensure events include an email (or the field you configured as `key_field_id`).
External event not triggering automation	Event name not registered	External event names must be pre-registered in Emarsys before they can trigger automations.

Visit Emarsys API documentation for full reference.