The Emarsys Marketing Platform allows consumer-facing companies of any industry to convert, grow and retain their clients by enabling automated and personalized interactions across the customer lifecycle and across channels and devices.
This destination is maintained by Emarsys. For any issues with the destination, please reach out to their team.
NOTE: The Emarsys Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on April 4, 2019. If you are interested in joining their beta program or have any feedback to help improve the Emarsys Destination and its documentation, please let their team know!
The first step is to make sure Emarsys supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “Emarsys” within the Destinations Catalog and confirm the Source you’d like to connect to.
- Drop in the “API Key” into your Segment Settings UI which you obtain from your Emarsys Account Manager.
- Work with your Emarsys Account Manager to establish the initial processing rules required within the Emarsys platform.
Once enabled you will have a new item in the Add-Ons menu: “segment.com”. This will open the configuration page to set up data maps and rules. An Emarsys integration consultant will assist you with setting up your first data maps and rules.
Page, Screen, Identify, Track
Identify, Track, Screen and Page requests have identical behavior for the Emarsys Destination.
Emarsys maintains an intermediate users table which stores three different identification properties:
primarykey. While a
userId will be used from Segment’s standard properties you can define which property in the JSON from Segment has to be used as the primary key (e.g. traits -> email). Each incoming request will update this intermediate users table.
The Emarsys Destination allows you to map any data property to fields in the Emarsys platform. With the integrated rule builder you can define sequences of events which will trigger marketing automation programs in the Emarsys platform.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.
Please consult your Emarsys account manager for your API Key.