> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/partner-types/esp-and-marketing-automation.md). # ESP & marketing automation What email and marketing automation platforms need from your CDP, and which connectors reach them. An **email service provider** or **marketing automation platform** owns your direct relationship with a known customer: the email, the push notification, the in-app message, the journey that ties them together. These are the connectors where the CDP is not supplying an advertising identifier but a **person you already have permission to contact**. The audience you build in mediarithmics arrives as a list, a tag, or an attribute on a contact who already exists on the other side. ## What these connectors have in common * **They match on owned identifiers** - an email, a user account ID, a device channel - not on advertising IDs. Several send the email **unencrypted**, because the partner already holds it. * **They usually write onto an existing contact** rather than creating an audience from nothing. Your segment becomes a tag (Airship), an attribute (Braze), a data extension row (Salesforce), an audience (Batch CEP). * **Most are configured with your account manager.** Credentials are exchanged out of band and stored in the mediarithmics back office, and the feed then references a *credential name* rather than the secret itself. [Batch CEP](/connectors/destinations/batch.md) is the exception: you set its keys yourself. * **They can carry profile data**, which makes personalisation possible on the partner side - and makes it worth checking what your data model actually exposes before you promise it. ## Connectors

Connector
Airship	Segments arrive as Airship tags in a tag group. Emails, Channels, Named User.
Batch CEP	Customer engagement. Segments become Batch CEP audiences, kept up to date as users enter and leave. Mobile IDs, user account IDs, device IDs.
Braze	Segments arrive as a user attribute - an array element or a boolean. User account IDs.
Brevo (ex SendInBlue)	Unencrypted emails, first and last name.
Emarsys	Unencrypted emails, Emarsys user IDs.
SalesForce Marketing Cloud	Writes into a data extension. UserProfile data only - no UserAccount, UserEvent or UserChoice.

Also available through your account manager: Adobe Campaign Classic (ex Neolane), Adventori, NP6. See [Connectors on request](/connectors/connectors-on-request.md). ## What to watch {% hint style="warning" %} The most common failure on this type is not the connection but the **field contract**. Salesforce rejects a send when the `segment_name` field in the data extension is shorter than the mediarithmics segment name - and mediarithmics allows up to 255 characters. Agree field lengths and names, with exact casing, before the first send. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mediarithmics.io/connectors/partner-types/esp-and-marketing-automation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.