Emarsys (SAP) Connector
Connector status: Planned Not built yet. Tajo does not run this connector today.
Illustration · sample data
Sync example
Source
Emarsys (SAP)
Connector status: Planned
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Connector implementation
Build the Emarsys (SAP) integration
SAP Emarsys customer engagement platform for contacts, segments, campaigns, events, and personalization.
Implementation Overview
Implement an Emarsys (SAP) connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
dev.emarsys.com/
| Property | Value |
|---|---|
| Integration surface | OpenAPI |
| Status | Planned |
| Category | Omnichannel Engagement |
| Setup complexity | medium |
| Vendor documentation | help.sap.com/docs/SAP_EMARSYS/5d44574160f44536b0130abf58cb87cc/fdf6023c74c11014b724bbfdb6028c98.html |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | dev.emarsys.com/ |
| MCP server | Not recorded |
| Last researched | 2026-05-13 |
SAP documents the Emarsys API and says endpoint specifications are available in JSON/YAML, OpenAPI, RAML, and Postman formats on the developer hub; Tajo has not vendored the spec yet.
Authentication
-
Use dev.emarsys.com/ to generate or validate typed API clients and request models.
-
Keep help.sap.com/docs/SAP_EMARSYS/5d44574160f44536b0130abf58cb87cc/fdf6023c74c11014b724bbfdb6028c98.html linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Contact and identity records
- Events, webhooks, and behavioral activity
- Campaign, messaging, or audience state
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
No typed contract exists for Emarsys (SAP), so the direction of each resource and its conflict handling are not recorded. Direction is declared per resource on a connector contract; see the connector catalog for how contracts are promoted.
Mapping To Tajo/Brevo
No Brevo projection is recorded for Emarsys (SAP). A projection is declared on a typed connector contract, and Emarsys (SAP) does not have one yet, so this page will not state a mapping it cannot source.
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.