Task Actions

Inserting Data when you have the iMIS ID
Use this action to insert non-contact data—that is, data that does not reside in the Contact source—when the iMIS ID is known (e.g., activities, panel data, gifts, credentials, event registrations, etc.).

Creating New Contacts
Use this action to create new contacts. A new iMIS ID is automatically assigned, and any mapped data is added to the new record.

Inserting Table Data
Use this action to insert table-type data such as Products, Events, Gen Tables, Promotions, and Freight.

Use this action when you need help matching to the correct record in iMIS and do not have the iMIS ID.

For example, if you have a spreadsheet of Activities with name and email, but no ID, this action will attempt to find the correct contact to associate the data with.

Avoid using this action when you already have the iMIS ID. In those cases, use the Insert action instead.

Use this action when you are updating existing iMIS data. Accurate matching is critical—match on as many fields as possible to avoid unintentional changes. Common fields include:

• iMIS ID

• SEQN

• Ordinal

For example, when updating activities, if SEQN is not available, match on as many fields as possible. At a minimum, use:

• iMIS ID

• Activity Type

• Transaction Date

Matching on too few fields can result in updates to the wrong activity records.

Options
The following option is especially important when updating:

• Skip update if more than one record is found
  Prevents unintended updates when your matching returns multiple results.

Use this action when you need to insert and/or update data in the same job. It is critical that your matching logic is configured correctly to ensure accurate inserts and updates.

Options
The following options are available for an Insert/Update job:

• Do not update records; insert only when no match is found
  Use this when you only want to insert new data and leave existing iMIS data unchanged.

• Skip update if more than one record is found
  Use this to prevent unintended updates when your matching logic is too broad or returns multiple results.

Use this action to delete panel data, activities, relationships, user credentials, shopping carts, general lookup table values, interactions, and more.

Important: It is critical to match on as many fields as possible.
For example, if you only match on iMIS ID when deleting an activity, all activities for that contact will be deleted. Always narrow your matching to the specific data you intend to remove.

Deleting Contacts
The Delete action cannot be used to remove contact records directly.
To delete a contact, update their status to one that is marked for erasure.