Email: Configuring the Email process in a Unica Campaign flowchart

Engage database

Required. Select a flexible Engage database associated with the contact list. All shared Engage databases are listed. A single flexible database is used for each channel (Email, SMS, and Push).

Selected input cells

Required. Select the segments who will receive this mailing. The input cells that you see depend on which process boxes (such as Select or Segment) are connected to the Email process. For example, if two Select processes are providing input to the Email process, two input cells are listed. Typically, you select all of the input cells. All of the IDs from the selected cells are then available to create the contact list and for customization (personalization).

Select all

Quickly select all of the listed input cells (the segments that are connected as input to the Email list process).

Clear all

Quickly clear the list of selections.

Use single contact list

Select Use single contact list to use the same Engage contact list every time the process runs. Then select an Engage contact list. All contacts in the list will be included in the mailing.

Check Clear contact list before updating if you want to remove all contacts from the list before reusing the list for a new run.

Use the following controls to indicate how to update the contact list upon each subsequent run:

• Always add new contacts: Do not update matching contacts. If the Unica Campaign data includes contacts that are not in the list, add them to the list.
• Update matching contacts; skip contacts that are not found: Update an existing contact with data from Unica Campaign. Do not add any new contacts to the list.
• Update matching contacts; add contacts that are not found: Update an existing contact with data from Unica Campaign. If a contact is not in the list, add it.

When you do a test or production run of the process box, a contact list is created or updated. All contacts in the list will be included in the mailing.

Create new contact list for every run

Select Create new contact list for every run if you want to create a new Engage contact list every time the process runs. All contacts in the list will be included in the mailing.

Specify a Name for the contact list.

Select either Add suffix or Add prefix to indicate whether to include the timestamp at the start or end of the filename. A timestamp for the process run is always added to ensure that the list name is unique.

Optionally, include the Unica Campaign ID and/or the Email Cell name as part of the filename.

Email template

Optional. Select an Engage email template. All shared templates are listed. The template determines the content of the email. If you do not make any changes in this dialog box, then all content comes directly from the template. Any changes that you make in this dialog override the content in the template. Changes are not saved to the template, but are used in the mailing for the current run of this process box.

The Email process box execution can upload only the contact list in Engage database without selecting Email Template or anything on the Content Customization tab. The Email process box will only upload the data to engage database. It will not send emails as no email template or customization information is passed from Unica Campaign. If no email template is selected in the Email process box, then all fields related to email send will be disabled. The Email process box will be shown as configured even if nothing is specified or selected under Content Customization tab.

This feature is applicable only to Email process box and not to the Push process box or SMS process box.

Enable inbox monitoring

Inbox monitoring is an optional Engage feature.

If this feature was purchased and enabled in Engage, you can choose whether to use it by checking or clearing this option. Using this feature might incur additional costs.

If this feature was not purchased and enabled in Engage, this option is ignored for the email send in the integration. (You can check or clear the box; it doesn't matter.)

Send email to all contacts immediately

• The Send email to all contacts immediately option is available only after you select the Email Template.
• If you check Send email to all contacts immediately, the email is sent to all recipients when you do a production run in Unica Campaign. (Note that a test run in Unica Campaign never sends emails, regardless of whether this option is selected.)
• Leave this option unchecked if you prefer to use Engage to send the emails. When this option is not checked, a production run in Unica Campaign uploads the contact list to Engage but does not send out the emails. You can then initiate/schedule the send from Engage.

Subject

Optional. If you leave this field blank, the Subject line from the Engage template is used. If you enter content in this field, it will be used as the Subject line in the mailing.

To indicate variables, surround them with %%. For example, specify Hello %%FirstName%%! to use values from the FirstName field. If a value in that field is "John" the email Subject line will resolve to Hello John!.

Email name

Required. The Email name identifies the mailing in Engage and Unica Campaign. The name that you specify is used instead of the Mailing Name that is specified in the Engage template. You can use a name that indicates the purpose of the mailing and its flowchart, so you can easily identify it later. Use static text only (no variables). Recipients never see this name.

To support response tracking, a timestamp for the process run is added to the name at process run time to ensure that the mailing name is unique for every process run. Additionally, the Unica Campaign code is included to track responses. This unique mailing name is included in every event generated by Engage, so it is used to correlate responses.

From name

Optional. Override the From Name that is specified in the email template. The template itself remains unchanged. Recipients see this name as the "From" name in the mailing. Use static text only (no variables). If you leave the field empty, the mailing uses the "From Name" that is specified in the email template. If you have any questions about what was used in the email template, check with an Engage marketing specialist who can look at the template in Engage. Example of a From name: Jane Smith

Reply-to address

Optional. Override the Reply To Address that is specified in the email template. The template itself remains unchanged. Use static text only (no variables). If you leave the field empty, the mailing uses the Reply To Address that is specified in the template. If you have any questions about what was used in the email template, check with an Engage marketing specialist who can look at the template in Engage. Example of a Reply-to address: jsmith@example.com

From address

Optional. Override the From Address that is specified in the email template. The template itself remains unchanged. Use static text only (no variables). If you leave the field empty, the mailing uses the From Address that is specified in the template. If you have any questions about what was used in the email template, check with an Engage marketing specialist who can look at the template in Engage. Example of a From address: jsmith@example.com

Static values for template

Optional. Use the Static values for template field to override variables in the email body with static text. The text that you provide appears in the body of the email when it is sent.

Syntax: Specify name:value pairs. Use a semicolon (;) to separate multiple pairs. Field1:StaticText;Field2:StaticText

Example: The email contains the variable %%Country%% in the email body. You specify Country:Canada in the Static values for template field. The resulting email uses "Canada" in place of %%Country%%.

Use case: You configure a flowchart to segment data by country (Canada, USA, Mexico). You add three Email process boxes to the flowchart and configure each one with a different static value. For example: Country:Canada and Country:USA and Country:Mexico. When you run the flowchart, the static text (country name) replaces the variable (%%Country%%) that is defined in the email. The result is three contact lists, each customized for a specific country.

Optional. This option applies only if Send email to all contacts immediately is selected.

Specify where the sent mailing will be stored in Engage (Content > View Mailings > Sent). If you do not specify a folder, the mailing will appear in the root of the Sent tab. If you specify a folder that does not exist in Engage, you are given the opportunity to create it as a subfolder (under "Sent").

Guidelines for specifying paths: Only use forward slashes. Do not use periods. Do not specify leading or trailing slashes. Do not specify static paths such as C:\Folder. If you specify an invalid path, you receive a runtime error of "Folder not found." Only the following characters are supported: # _ - () A-Z a-z 0-9 /

Example: Specify Campaign/Test to save the mailing in Sent/Campaign/Test.

Refresh

Refresh the table fields information for the selected Engage database. Use this option if any new fields are added to the Engage database or if any existing fields are modified.

Candidate fields

This list shows all of the available fields from the processes that are providing input to the Email process box. These are the Campaign fields that contain data such as contact names and addresses, demographics, purchase history, or other information that is stored in Campaign databases or flat files.

Fields to export to Engage

The fields in this list provide data to create or update the Engage contact list. The values for the mapped fields come from Campaign databases or flat files.

For example, if you map the Campaign field FirstName to the Engage field CustomerFirstName, the values are pulled from the Campaign FirstName field. When the contact list is uploaded to Engage, the value of the Campaign FirstName field will be used to update the CustomerFirstName field in the Engage database. Engage will then use the newly updated CustomerFirstName field when populating the email template.

When you map Candidate fields (in Campaign) to Fields to export to Engage (in Engage), be sure that the mapped fields use the same Field Type (data type), such as Text, Date, Time, etc. If the data types do not match, errors occur when the system tries to import the values in the Candidate fields into the mapped Engage database fields.

EMAIL (Text data type) is a required field, so be sure to match an equivalent Candidate field from Campaign (one that uses a Text data type) by clicking >>.

Also ensure that the order of fields in the list matches the order of the fields in the Engage contact list. Use the arrow icons to move a selected field up or down in the list. For example, move First Name before Last Name. Note: The order of the fields in this list determines the order of the fields in the commas-separated values (CSV) file that is created to form the contact list.

If a field for a specific record lacks a value, that field is left empty in the contact list. For example, if you map the ZIP field in Campaign to the ZipCode field in Engage, and the zip code field is empty for a particular customer, that field is not populated in the comma-separated values (CSV) field that is used to create the contact list.

After you complete the mapping, click the check mark in the Sync column for the field or fields that are to be used as the sync fields. If you do not select any sync fields, the campaignaudienceId is used as the sync field by default.

Profile

It can be helpful to see the actual values that are stored in a database field in Campaign. To do so, select a Candidate field and click Profile. Wait until profiling is complete to ensure that you see all of the values. For example, profile a field called Email to see a list of email addresses that are stored in that field.

Derived fields

Optionally, click the Derived fields button to create a new variable for querying, segmenting, sorting, calculating, or providing output to a table. Derived fields are variables that do not exist in a data source and are created from one or more existing fields, even across different data sources.

Process name

Assign a descriptive name. The process name is used as the box label on the flowchart. It is also used in various dialogs and reports to identify the process. Customers never see this name.

Note

Provide information to help you and other Campaign users understand the purpose or result of this process. The content of this field appears when you rest your cursor over the process box in a flowchart. Customers never see this note.