# Emarsys (Actions) Destination ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Emarsys (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** > \[!NOTE] > > This page is about the Emarsys (Actions) Destination. See below for information about other versions of the Emarsys destination: > > * [Emarsys (Classic)](/docs/segment/connections/destinations/catalog/emarsys/) [Emarsys](https://www.emarsys.com) Emarsys, An SAP Company, is the omnichannel customer engagement platform, which empowers marketers to build, launch, and scale personalized cross-channel campaigns that drive business outcomes. By rapidly aligning desired business results with proven omnichannel customer engagement strategies the platform enables marketers to accelerate time to value, deliver superior 1:1 experiences and produce measurable results fast. ## Benefits of Emarsys (Actions) vs Emarsys Classic Emarsys (Actions) provides the following benefits over the classic Emarsys destination: * **Easy self-setup**. Use standard API credentials to connect to an Emarsys account. * **Standard actions**. Use standard API functionality to manage contacts and start marketing automations. ## Getting Started 1. In the Segment web app, go to **Catalog** > **Destinations**. 2. In the left menu, click Destination Actions. 3. Click **Configure Actions Emarsys**. 4. Select an existing Source to connect to Emarsys (Actions). 5. Click Customized Setup to start with an empty mapping. ## Important differences compared to the classic Emarsys destination The classic Emarsys destination handles any kind of Segment traffic but it requires additional configuration in the Emarsys account. Emarsys (Actions) does not need additional configuration in the Emarsys account, it is only configured in the Segment user interface. Please note that standard API rate limits apply. ## Destination Settings | Field | Description | Required | Type | | ------------ | -------------------------- | -------- | -------- | | API password | Your Emarsys API password. | Yes | password | | API username | Your Emarsys API username | Yes | string | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Emarsys-supported actions: > \[!NOTE] > > Individual destination instances have support a maximum of 50 mappings. * [Add to Contact List](#add-to-contact-list) * [Remove from Contact List](#remove-from-contact-list) * [Upsert Contact](#upsert-contact-4) * [Trigger Event](#trigger-event) ### Add to Contact List Add a contact to a contact list. The contact must exist before it can be added. Add to Contact List is a **Cloud** action. | Field | Description | Required | Type | | ---------------------- | -------------------------------------------------------------------------- | -------- | ------- | | Id of the contact list | The Id of the contactlist | Yes | INTEGER | | Key field | The field to use to find the contact | Yes | STRING | | Key value | Value for the key field used to find the contact. E.g. the email address | Yes | STRING | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN | ### Remove from Contact List Remove a contact from a contact list. Remove from Contact List is a **Cloud** action. | Field | Description | Required | Type | | ---------------------- | -------------------------------------------------------------------------- | -------- | ------- | | Id of the contact list | The Id of the contactlist | Yes | INTEGER | | Key field | The field to use to find the contact | Yes | STRING | | Key value | Value for the key field used to find the contact. E.g. the email address | Yes | STRING | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN | ### Upsert Contact Insert or update a contact on the Emarsys platform Upsert Contact is a **Cloud** action. | Field | Description | Required | Type | | ---------------- | ------------------------------------------------------------------------------------------------------ | -------- | ------- | | Key field | The field to use to find the contact | Yes | STRING | | Key value | Value for the key field used to find the contact. E.g. the email address | Yes | STRING | | Fields to write | Use the emarsys field id (number) as key and set a value (string) (static, function or event variable) | Yes | OBJECT | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN | ### Trigger Event Trigger an external event on the Emarsys platform to launch automation programs. Note: You can only pass objects to event\_payload (no literals, no arrays). Trigger Event is a **Cloud** action. | Field | Description | Required | Type | | ------------------------ | ---------------------------------------------------------------------------------------------------- | -------- | ------- | | Id of the external event | The Id of the external event | Yes | INTEGER | | Key field | The field to use to find the contact | Yes | STRING | | Key value | Value for the key field used to find the contact. E.g. the email address | Yes | STRING | | Event payload | A JSON object that will be passed to the Emarsys template engine and can be used for personalization | No | OBJECT | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN |