New: The Agentic CDP

·Read the analysis

Tool · Email & Marketing Automation

SAP Engagement Cloud integrations across CDPs

Formerly SAP Emarsys · Directory data as of October 18, 2026

13 of the 44 customer data platforms in the CdpHub directory list an integration with SAP Engagement Cloud, with 19 listings between them. Of those platforms, 4 both send data to SAP Engagement Cloud and read from it and 9 only send data to it. 13 can run server-side and 5 in the warehouse. 18 of the 19 listings link to their platform's own documentation.

13of 44 CDPs list SAP Engagement Cloud
19listings across them
4send data to SAP Engagement Cloud and read from it
#51most listed of 2,309 tools

Which CDPs list SAP Engagement Cloud

13 of 44
Sends data to SAP Engagement Cloud Does both

Not listed by 31 CDPs: 6sense, Adobe Experience Platform, Bloomreach, BlueConic, Blueshift, Braze, CaliberMind, Chord, CleverTap, Informatica, Insider One, Klaviyo, Leadspace, Listrak, Lytics, Microsoft Dynamics 365 Customer Insights, NICE, Odie, Ometria, Optimizely, Oracle, Redpoint Global, Salesforce Data 360, SAP Engagement Cloud, SAS, Simon Data, Snowplow, Spotler ActivatePro, Teradata, Treasure AI and Upland BlueVenn.

How each CDP connects to SAP Engagement Cloud

13 CDPs · 19 listings
ActionIQ (sends data to SAP Engagement Cloud)1 listing
ActionIQ → SAP Engagement Cloud

Emarsys

All ActionIQ integrations →
Amperity (sends data to SAP Engagement Cloud and reads from it)2 listings
Amperity → SAP Engagement Cloud

SAP Emarsys (destination). Maintains SAP Emarsys contact lists from Amperity audiences through the Emarsys API, adding lists and contacts and updating their attributes.

SAP Engagement Cloud → Amperity

SAP Emarsys (source). Pulls customer records exported from Emarsys into Amperity over SFTP.

All Amperity integrations →
DinMo (sends data to SAP Engagement Cloud)3 listings
DinMo → SAP Engagement Cloud

Emarsys (contact lists). Creates Emarsys contact lists from DinMo models or segments and keeps membership current for existing contacts matched by email, without creating or deleting any contact.

DinMo → SAP Engagement Cloud

Emarsys (contacts). Updates Emarsys contact fields from a DinMo model by clear-text email and can insert new contacts into a list chosen at setup, since Emarsys needs every contact in a list.

DinMo → SAP Engagement Cloud

Emarsys (RDS custom tables). Updates rows of a predefined Emarsys Relational Data Service table from a DinMo model, matched on its id column and optionally inserting rows, for accounts with RDS enabled.

All DinMo integrations →
Fivetran Activations (sends data to SAP Engagement Cloud)1 listing
Fivetran Activations → SAP Engagement Cloud

Emarsys. Upserts Emarsys contacts on an indexed field and mirrors contact list membership by email from Fivetran Activations, using an Emarsys API user and secret.

All Fivetran Activations integrations →
Hightouch (sends data to SAP Engagement Cloud)1 listing
Hightouch → SAP Engagement Cloud

Emarsys. Syncs warehouse users into Emarsys contacts and adds or removes them from contact lists as data changes.

All Hightouch integrations →
Lexer (sends data to SAP Engagement Cloud and reads from it)1 listing
Lexer ⇄ SAP Engagement Cloud

Emarsys. Imports Emarsys contacts and campaign engagement into Lexer through the API and SFTP, A/B campaign versions included, and creates or updates Emarsys contact lists and fields from Lexer segments.

All Lexer integrations →
mParticle (sends data to SAP Engagement Cloud)1 listing
mParticle → SAP Engagement Cloud

Emarsys. Sends mParticle audiences to SAP Emarsys through its Enhance marketplace, for personalized email, mobile and web campaigns.

All mParticle integrations →
RudderStack (sends data to SAP Engagement Cloud)1 listing
RudderStack → SAP Engagement Cloud

Emarsys. Sends RudderStack contacts, events and groups to SAP Emarsys to trigger automations and personalize omnichannel campaigns.

All RudderStack integrations →
SAP CDP (sends data to SAP Engagement Cloud and reads from it)1 listing
SAP ⇄ SAP Engagement Cloud

Emarsys. Sends merged SAP Customer Data Platform profiles and corporate accounts to Emarsys in real time, while Emarsys email opens, clicks, bounces and complaints flow back to the CDP.

All SAP CDP integrations →
Segment (sends data to SAP Engagement Cloud)2 listings
Segment → SAP Engagement Cloud

Emarsys (Actions). Sends Segment data to Emarsys for email marketing and analytics through Actions such as Add to Contact List and Remove from Contact List (beta).

Segment → SAP Engagement Cloud

Emarsys (classic). Sends identify, track and page calls from Segment to Emarsys for email marketing and analytics in cloud mode.

All Segment integrations →
Tealium (sends data to SAP Engagement Cloud)1 listing
Tealium → SAP Engagement Cloud

Emarsys. Creates or updates Emarsys contacts and adds them to or removes them from contact lists, in real time or batched, from AudienceStream or EventStream.

All Tealium integrations →
Zeotap (sends data to SAP Engagement Cloud and reads from it)3 listings
Zeotap → SAP Engagement Cloud

Emarsys (batch). Adds Zeotap audience contacts to Emarsys contact lists or sends them as triggered events through the Emarsys API with WSSE credentials, while the old identifiers-only action is deprecated.

Zeotap → SAP Engagement Cloud

Emarsys (real-time). Records customer events such as cart abandonment in Emarsys from Zeotap Journeys in real time, with profile fields, so follow-up messages can go out right away.

SAP Engagement Cloud → Zeotap

Emarsys (source). Pulls Emarsys email engagement data into Zeotap through the Emarsys API, first requesting campaign responses such as opens, clicks or bounces and then the matching contacts.

All Zeotap integrations →
Zeta Global (sends data to SAP Engagement Cloud)1 listing
Zeta Global → SAP Engagement Cloud

Emarsys. Pushes Zeta customers to Emarsys through a Channel Manager channel documented against the Emarsys Trigger API, using Emarsys authentication, with Experiences picking when.

All Zeta Global integrations →

Other Email & Marketing Automation tools

All tools on two or more CDPs →

About these numbers

CdpHub documents each integration from the platform's own catalog, so a listing records what the platform says it supports, not a test of the connector. Each one notes which way data flows and where the integration runs. A platform can list more than one connector for SAP Engagement Cloud, so listings can outnumber platforms; a platform that both sends data to SAP Engagement Cloud and reads from it is counted once, as doing both. The rank orders all 2,309 tools in the directory by how many platforms list them; tools listed on the same number of platforms share a rank. Counts are updated as catalogs change; this page reflects the directory as of October 18, 2026. CdpHub is independent and not affiliated with SAP Engagement Cloud or any platform listed.

Connecting SAP Engagement Cloud to a CDP?

Vendor-neutral help choosing the CDP that fits how you use SAP Engagement Cloud, and getting the connection running in your stack.

Talk to CdpHub →

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Read our cookie policy

C
CdpHub × LiveAvatar
Early Access: CdpHub's AI guide draws from our integration directory but may occasionally provide incomplete or inaccurate information. We're actively improving it — your patience and feedback are appreciated. When you use the mic, your voice is transcribed so Ed can answer.
Ed, CdpHub's AI guide

CdpHub · Powered by Claude + LiveAvatar

Ask Ed