Select an email touchpoint when you want to connect to the customer using email
communication. If you have integrated both Unica Link and Deliver, you will see the options
Deliver and
Link as
delivery options for the email Touchpoint.
Before you begin
Before you start this procedure, see Touchpoints.
About this task
To configure an email touchpoint, execute any one of the following steps:
If
you have set a default email connection in Setting a default email connection, and if the default connection set is
Mailchimp, move to Step (4). If the default connection set is
Mandrill, move to Step (5). If you have not set a default
email connection, the Existing Connections dialog opens.
Procedure
-
Select either Mailchimp or
Mandrill and click Next.
The Create New Action dialog appears. In this
dialog, you can also switch to a different connector by selecting
Existing Connection.
-
If the default connection is Mailchimp, complete the
following steps:
-
Provide values for the following fields:
- Contact Action - Mandatory. The action to
be performed on the contacts.
- Audience - Mandatory. The list in which
you want the audiences to be saved.
- New Email Campaign - Mandatory. The name
of the new email campaign.
- Email Template - Mandatory. The template
used for the email.
- Email Subject - Mandatory. The subject of
the email to be sent to the users.
- Preview Text - Optional. The text that
will be part of the body of the email.
- Sender's Name - Mandatory. The sender who
sent the email to the customer.
- Reply to Email - Mandatory. The email
address which will be used for a customer to reply back..
- Group Contacts By Tag - Optional.
- Fetch Results End Date - Optional.
-
Click Next.
The Field Mapping dialog
appears.
-
Map the email connector fields with the appropriate Journey fields (coming from the
Data Definition associated with the Journey during Journey creation). This is
essential as the mapping changes the value on runtime.
Note: Journey gives each user a unique id known as
audience id. This id helps in tracking different ongoing events for
a particular audience. It is not mandatory to map Journey audience
id field on Link screen because Link understands the significance of
audience id field and sends audience values for different audiences.
The mapping achieves personalization to the email. In mailchimp, if
you map first_name of mailchimp to
fname of Journey and the
last_name to lname,
the salutation in the email will be personalized to the value of the
field.
-
Click Save.
-
If the default connection is Mandrill, complete the
following steps:
-
Provide values for the following fields:
- Email Template - Mandatory. Click
Fetch to view the available
templates.
- Sender Email - Optional. The email
address of the user sending the communication.
- Email Subject - Optional. The subject of
the email to be sent to the users.
- Reply to Email - Optional. The email
address which will be used for a customer to reply back.
- Fetch Results End Date - Optional.
Configure a date for accepting customer responses.
Note: When
configuring Mandrill, if you do not provide values for the
optional fields, Mandrill fetches the value from the
selected Mandrill template. Ensure that you provide all the
values during template creation in Mandrill.
-
Click Next.
The Field Mapping dialog
appears.
-
Map the email connector fields with the appropriate Journey fields (coming from the
Data Definition associated with the Journey during Journey creation). This is
essential as the mapping changes the value on runtime.
The mapping achieves personalization to the email. In Mandrill, if you
map
FIRSTNAME of Mandrill to
First_Name of
Journey and the
LASTNAME to
Last_Name,
the salutation in the email will be personalized to the value of the field.
Note: Mandrill supports up to five personalization fields in the
Field Mapping dialog.
-
Click Save.
Note: Email touchpoint can be configured with delivery channels like Deliver or
Link. While the Journey is in draft mode (not published earlier) user would
not be able to change the delivery channels from Deliver to Link or vice
versa. Once you configure one delivery channel you must not change it to
another delivery channel. If there is need then user can remove the email
touchpoint and configure it with new delivery channel.
Journey support unsubscribe events
Journey support Unsubscribe events in Journey through deliver. If a user
wishes to unsubscribe from Journey emails, we will track them through
unsubscribe. Email ids of users will be saved in table EmailUnsubscribedList
and Journey will not send any mails to these users in future.