This event executes a job when import of a file with contact addresses and profile data finishes. During import, contacts, addresses and attribute data are imported into a Engage group from a CSV, XML or text file.

This includes:


WARNING!

Do not use the combination ​Contact Import Finished (S)​+ ​Send Prepared Message to Group (S)​ if you are importing multiple files from an FTP or similar server. The automation will fire once for every import file. As a result the same message is sent to the group multiple times. Instead, use the scenario Welcome Program (Import)​, which creates two time-based automations.

Hint:

In Engage, the designation ​(S)​ means system-related. Generally, you only combine ​system (S) events​ with ​system (S) jobs​. For more information, see Contact (C) vs. System (S) Automations​

General

​Name​

Defines the name of the automation. The name is used to identify the automation in the system. The maximum length is 100 characters.

​Description​

Provides information about the automation. The description makes it easier to identify the automation in the system.

​Event​

Selects the type of event that, when combined with a job, forms the automation. Every time this event occurs, the system executes the dependent job. The job is defined in the ​Edit Event-based Job​ window.

Recommended Automations​

An automation is a combination of an event plus a resulting job. The following combinations are recommended. It is possible to create other combinations, as well, but not all combinations of events and jobs result in meaningful system behavior.

Contact Import Finished (S) + Send Prepared Message to Group (S): This automation sends a prepared message to all group members when the import is finished. The prepared message is sent to both existing members and newly imported members.
Do not use the combination ​Contact Import Finished (S)​+ ​Send Prepared Message to Group (S)​ if you are importing multiple files from an FTP or similar server. The automation will fire once for every import file. As a result the same message is sent to the group multiple times. Instead, use the scenario Welcome Program (Import)​, which creates two time-based automations.

Contact Import Finished (S) + Generate Import Report (S): This automation is used to exports detailed results from an import job when the import is finished. Alternatively, the automation can be set up so that the job only executes when address import fails.

Contact Import Finished (S) + Export Data to Server (S): This automation exports data to a server when the import is finished. The export includes all address-related data, including newly imported and updated information.

WARNING!

The following combinations are not possible or not recommended.

Address Import Finished (S) + Store Data in Profile Attribute (C): This combination does not store data in the profiles of all contacts in an address import. The only profile changed with this automation is that the of the system user performing the import.

Address Import Finished (S) + Send Prepared Message to Contact (C): This combination does not send a prepared message to individual contacts in an address import. The prepared message is only sent to the system user performing the import

Define Event​

This area defines the specific parameters of the event.

Group Email: These fields restrict the event to imports into a certain group or groups. This restriction is based on the group email, not on the group name.
Leave this field blank to include address imports in all groups in the system.

  • Equals: The group email address exactly matches the value entered in the input field.

  • Does Not Equal: The group email address does NOT match the value entered in the input field.

  • Starts with: The group email address starts with the value entered in the input field.

  • Ends with: The group email address ends with the value entered in the input field

  • Matches [Regex]: The group email address matches the Regular Expression entered in the input field.

Success: This drop-down list restricts the event to successful or unsuccessful imports.
Only the success of the import itself is relevant. An infrastructure problem (for example, an FTP failure) is not relevant here.

  • Blank: Both successful and unsuccessful imports initiate the job.

  • Yes: Only successful imports initiate the job. A successful import means the process completed successfully, even if the file was empty or no new contacts were added.

  • No: Only unsuccessful imports initiate the job. Only the success of the import itself is relevant.
    Examples of an unsuccessful import: the file is not readable, processing fails on the Engage side (not an FTP failure), or the import contains invalid enumerated attributes.

Actions

The following actions are available: