• Marketing profile: Update your contact data or create new contacts.
• Audience targeting and segmentation: Update or create contact lists, trigger external events in Interaction programs.
• Contextual real-time personalization: Create external data tokens based on your triggered external events.

Here is what you need to do to set up the mParticle connector:

1. In mParticle, navigate to Directory and search for Emarsys.

2. Hover over the tile and click Setup.
3. Select the Integration Types you would like to use:

• Event - You can send raw event data to Emarsys from mParticle with this type.
• Audience - You can send user lists to Emarsys from mParticle with this type.
• Data Subject Request - You can send erasure requests from mParticle with this type.

4. On the Setup screen, enter the following:

• Configuration Name
• Customer ID - Your Emarsys account ID. In Emarsys, you can check your Emarsys account ID by clicking Profile Menu in the top right corner.
• Integration Key - To check your integration key, in Emarsys, navigate to Add-ons > mParticle Connector and click the Settings tab. The integration key is displayed on the bottom of the screen.

5. Now you can connect Emarsys as an Output to your mParticle audiences or events.

In the following example, you can see that an audience is connected to the App Install Milestone event.

6. In Emarsys, go to Add-ons > mParticle Connector and select the Settings tab. Here you need to configure the following:

• Create contact if doesn't exist - Enable this option if you would like to create contacts who do not exist yet in Emarsys.
• Opt-in Handling - Decide how the connector should handle the contacts' opt-in status. The following options are available:
  • Do not change opt-in status
  • Set opt-in status to true
• Mappings between mParticle and Emarsys - Select at least one field that is used for looking up contacts from incoming mParticle requests. You can map a maximum of three fields. The connector uses the fields in a sequential order. If you are using a custom field, make sure the field is indexed and can be used for lookups. Typically, the email field can be used for this purpose.
• Select External Event for DSR - If you would like to handle Data Subject Requests (DSR), select an external event that is triggered by the connector. Use cases may differ according to your needs, for example, you can trigger an Automation program based on the selected event.
• Integration Key

You can map mParticle User Attribute Keys to Emarsys Suite Fields on the Attribute Mapping tab.

Audiences and events sent by mParticle contain contact attributes (e.g. first name, last name, etc.). When the connector finds a new master data related attribute in requests coming from mParticle, it adds the attribute as an unmapped one to the Attribute Mapping tab.

You can choose from the following options:

• Leaving the attribute unmapped - In this case, the attribute will be ignored.
• Map the attribute to a contact field - In this case, the connector updates this contact field in the contact profile with each incoming event or audience request containing this field.

You can map mParticle events to Emarsys external events on the Event Mapping tab.

After mapping an Emarsys external event to an mParticle event, the connector triggers the specified event. Before triggering the external event, the connector updates the contact in Emarsys to ensure their attributes are up-to-date. The connector also sends data from the mParticle event as transactional payload that you can use for personalization. You can use all event types available in mParticle in Emarsys.

You can check the following metrics on the Dashboard tab:

• Incoming Contacts - Number of contacts received from mParticle.
• Incoming Events - Number of events received from mParticle.
• Incoming Requests* - Number of requests received from mParticle.
• Overview - Here you can see the following:
  • Number of identifiers set
  • Number of attributes mapped
  • Number of events mapped

• The mParticle connector can only receive events that contain the following type of user identifier information: email or mobile number. If none of these user identifiers exist in the event payload, the corresponding event is not forwarded from mParticle to Emarsys.
• You can map only data from the event payload that is sent as user_attribute to Emarsys contact fields. Only this type of contact data can be updated.