Emarsys quick info
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, contact the Emarsys Support team.
This document is about a destination which is in beta
This means that the Emarsys Destination is in active development, and some functionality may change before it becomes generally available.
- From the Segment web app, click Catalog.
- Search for “Emarsys” in the Catalog, select it, and choose which of your sources to connect the destination to.
- Enter 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 is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property
order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Segment lets you change these destination settings from the Segment app without having to touch any code.
|Direct Integration Channels||
The channels this direct integration supports.
|Direct Integration Endpoint||
The API endpoint of the direct integration.
This page was last modified: 20 Oct 2020
Questions? Problems? Need more info? Contact us, and we can help!