Emarsys Connector Setup Guide

Emarsys Connector Setup Guide

by Community Manager on ‎06-06-2017 09:08 PM - edited 3 weeks ago by Community Manager (114 Views)

This article describes how to set up the Emarsys Connector service in your Universal Data Hub profile. With the Emarsys Connector, you can connect to a comprehensive cloud-based B2C (Business to Consumer) marketing platform that fully maximizes customer value through data science and artificial intelligence marketing. 

Table of Contents Placeholder

Requirements

Supported Actions

Action Name Trigger on Audience Trigger on Streams
Add Contact to Contact List
Remove Contact from Contact List
Update an Email Contact
Trigger Transactional Email
Unsubscribe Contact From Email Campaign

Configure Settings

Go to the Connector Marketplace and add a new Emarsys Connector. Read the Connector Overview article for general instructions on how to add a Connector.

To configure your vendor, follow these steps:

  1. In the Configure tab, provide a title for the Connector instance.

  2. Enter the username that you set up with Emarsys for your account.

  3. Enter the password that you set up with Emarsys for your account.

  4. Select the environment to run the API calls against.

  5. Provide additional notes about your implementation.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. It's where you'll set up Actions and trigger them.

This section describes how to set up Parameters and Options for each Action.

Action - Add Contact to Contact List

Parameters

  1. Target Contact List (REQUIRED): Select the contact list that you would like to add the user to. This list is retrieved from your Emarsys account. See Emarsys's Contact List documentation for more info.
  2. Contact Field Data to Set (REQUIRED): Identifies the contact to be added to the contact list. Map your Attribute(s) to the contact field of choice in the To dropdown. For a complete list of contact fields, refer to the Contact Field Reference table below.

See Emarsys's Contact Field documentation for more info.

Action - Remove Contact from Contact List

Parameters

  1. Target Contact List (REQUIRED): Select the contact list that you would like to remove the user from. See Emarsys's Contact List documentation for more info.
  2. Contact Field Data to Set (REQUIRED): Identifies the contact to be removed from the contact list. Map your Attribute(s) to the contact field of choice in the To dropdown. For a complete list of contact fields, refer to the Contact Field Reference table below.

See Emarsys's Contact Field documentation for more info.

Action - Update an Email Contact

Parameters

  1. Create if Not Exists: Check this box to create a new contact if it doesn't already exist. If the contact already exists, this field will have no effect.
  2. Source ID: An optional ID that identifies contacts created or modified using external (3rd-party) applications. Select the ID of choice from this list.
  3. Contact Identifying Field (REQUIRED): Select the field with which to identify the contact to be updated. This field must be present in the Contact Field Data to Set map.
  4. Contact Field Data to Set (REQUIRED): Map your Attribute(s) to the contact field of choice in the To dropdown. For a complete list of contact fields, refer to the table below.

Action - Trigger Transactional Email

Parameters

  1. External Event (REQUIRED): This is an external event configured in Emarsys to send an email from an email campaign.
  2. Contact Lookup (REQUIRED): Identifies the contact to send email to. Map your Attribute(s) to the contact field of choice in the To dropdown. For a complete list of contact fields, refer to the Contact Field Reference table below.
  3. Content Personalization Data to Set (OPTIONAL): Map your personalization to your email template placeholders. See more about personalization.

Action - Unsubscribe Contact From Email Campaign

Parameters

  1. Launch List ID (REQUIRED): This is the ID of the launch list that contains the contact to be unsubscribed.
  2. Email Campaign ID (REQUIRED): This is the ID of the email campaign that sends the emails.
  3. Contact ID (REQUIRED): This is a randomly generated string that is mapped to the contact to be unsubscribed.

Reference - Contact Fields Reference

Option Description Example
First Name First name of the contact John
Last Name Last name of the contact Doe
E-Mail Email address of the contact JohnDoe@Email.com
Date of Birth Date of birth, must be in YYYY-MM-DD format 1956-08-23
Gender Gender of the contact 1
Marital Status Marital status of the contact 1
Children Number of Children 1
Education Level of Education 1
Title Mr, Mrs, etc. 1
Address Mailing address of the contact 1 Main St.
City Mailing address city of the contact Springfield
State Mailing address state of the contact New York
ZIP Code Zip code of the contact 12345
Country Mailing address country 1
Phone Phone number 555-867-5309
Fax Fax number 555-946-3297
Job Position Position in company 1
Company Name of company Emarsys
Department Department within company 1
Industry Industry of company 1
Phone (office) Work phone number 555-123-4567
Fax (office) Work fax number 555-7654-321
Number of Employees Number of employees at company 1
Annual Revenue (in 000 EUR) Annual Revenue 1
URL Url of the contact's website http://www.example.com
Preferred e-mail format Email format 1
Opt-in Opt-in status 1
Registration language Language used to register 1
Mobile Mobile phone number 555-987-6543
First Name of Partner First name of partner Jane
Birth date of Partner Date of birth of partner, must be in YYYY-MM-DD format 1959-06-28
Anniversary Anniversary of contact and partner, must be in YYYY-MM-DD format 1980-03-15
Company Address Mailing address of the company 1 Business Way
Zip Code (office) Zip code of the company 12346
City (office) Mailing address city of the company Springfield
State (office) Mailing address state of the company New York
Country (office) Mailing address country of the company 1
Salutation Salutation to use with the contact 1

Refer to Emarsys's Contact Field documentation for more info.

Vendor Documentation

APIs

Additional References