Emarsys
Introduction
The Emarsys connector provides Reverse ETL destinations for SAP Emarsys. It currently supports credential validation (connection testing) for:
- SAP Emarsys Audiences
- SAP Emarsys Conversions API
Loading/syncing data into Emarsys is still in development for both destinations.
Setup
Before configuring the destination in the app, gather the required Emarsys API credentials:
- For SAP Emarsys Audiences: an Emarsys username and API secret with access to the Emarsys API.
- For SAP Emarsys Conversions API: your Conversions API base URL, API user, and API secret.
Authentication
Both destinations authenticate using HTTP Basic Authentication.
- Username / API user is sent as the Basic Auth username.
- API secret is sent as the Basic Auth password.
During connection testing, the connector validates credentials by making a GET request to an Emarsys endpoint and requiring a successful (2xx) response.
Configuration
SAP Emarsys Audiences
| Field | Type | Required | Description |
|---|---|---|---|
username | string | ✅ | Emarsys API username used for Basic Auth. |
api_secret | string | ✅ | Emarsys API secret used for Basic Auth. |
Credential validation request
GET https://api.emarsys.net/api/v3/contactlist
SAP Emarsys Conversions API
| Field | Type | Required | Description |
|---|---|---|---|
api_url | string | ✅ | Base URL for the Emarsys Conversions API (the connector will append /api/v2/event). Trailing slashes are allowed. |
api_user | string | ✅ | Conversions API user used for Basic Auth. |
api_secret | string | ✅ | Conversions API secret used for Basic Auth. |
Credential validation request
GET {api_url}/api/v2/event(with any trailing/removed fromapi_urlbefore appending)
Streams / sync behavior
This connector’s destination sync (load) functionality is not yet available. At this time:
- Connection testing (credential validation) is supported.
- Running a sync will fail with a message indicating the destination loading is still in development.
When loading is implemented, this documentation will be updated with supported objects/streams, required identifiers, and field mappings.