Push: Configuring the Push process in a Unica Campaign flowchart

Acoustic Campaign database

Required. Select a flexible Acoustic Campaign database associated with the contact list. All shared Acoustic Campaign databases are listed. You must select the flexible database that is used for the Push channel.

If you are using Email, SMS, and Push channels in the integration, use a separate database for each channel.

Selected input cells

Required. Select the segments who will receive the mobile push notification. The input cells that you see depend on which process boxes (such as Select or Segment) are connected to the Push process. For example, if two Select processes are providing input to the Push 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.

Select all

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

Clear all

Quickly clear the list of selections.

Use single contact list

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

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 push.

Create new contact list for every run

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

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 Campaign ID and/or the Push Cell name as part of the filename.

Push template

Required. Select an Acoustic Campaign push template. All shared templates are listed. The template determines the content of the push notification. If you do not make any changes in this dialog box, then all content comes directly from the template. Any changes that you make here override the content from the template. Changes are not saved to the template, but are used in the push notifications that are sent for the current run of this process box.

Push name

Required. The Push name identifies the push in Acoustic Campaign and Campaign. The name that you specify is used instead of the Push Name that is specified in the Acoustic Campaign template. You can use a name that indicates the purpose of the push 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 push name is unique for every process run. Additionally, the campaign code is included to track responses. This unique push name is included in every event generated by Acoustic Campaign, so it is used to correlate responses.

Send push notifications to all contacts immediately

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

Refresh

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

Candidate fields

This list shows all of the available fields from all of the processes that are providing input to the Push process. 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 Acoustic Campaign

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

When you map Campaign Candidate fields to Fields to export to Acoustic Campaign, 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 Acoustic Campaign database fields.

Ensure that the order of fields in the list matches the order of the fields in the Acoustic Campaign 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. In other words, 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.

In the Fields to export to Acoustic Campaign list, check at least one field in the Sync column that identifies a unique mobile user ID on the Acoustic Campaign side. For example, use a mobile phone number field.

An Acoustic Campaign flexible database is used for Push. To update data in this database, the Sync fields are treated as a primary key and the row that matches the columns in the Sync field is updated. For example, if MobilePhone is the Sync field, then the update happens on the row in which the criteria of the Sync field is matched.

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 Surname to see a list of names 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 or others 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.