Integrating Opportunity Detect with Unica Campaign in interactive mode

The following example illustrates how you might use the Expanded Outcome data in Unica Campaign, in interactive mode.

Before you begin

You must have Unica Campaign and Opportunity Detect installed and running.

About this task

The following diagram illustrates the example described in this procedure.


The diagram illustrates the interactive use case.

Procedure

  1. Create the Expanded Outcome tables in your database using the script provided with Opportunity Detect.
  2. Do one of the following.
    • If you plan to use a queue connector, configure a queue for your transaction data in your queue server.
    • If you plan to use the Web Service, develop the required Java™ classes.
  3. On the Server Groups page in Opportunity Detect, do the following.
    • If a database connection for the database where you created your Expanded Outcome tables does not exist, create one.
    • If an Expanded Outcome data source connector does not exist, create one.

      If you make the connector sharable, you can map the connector to your primary Expanded Outcome table on the Server Groups page or on the Deployment tab of the workspace. If you do not make the connector sharable, you can map it only on the Deployment tab.

  4. Configure the Opportunity Detect workspace to use the Web Service or a queue data source connector for transaction data, and the Expanded Outcome data source connector for Outcome data.
  5. Configure your Unica Campaign flowchart as follows.
    1. In a Select process, create a new table mapping as follows.
      • Map your main audience in Unica Campaign to the OUTCOMEID field in the primary Expanded Outcome table. This is required so that you can select Outcome records for use in the flowchart. Selection must use the OUTCOMEID field, as the same AUDIENCEID field can be repeated in multiple Outcome records.
      • Map your alternate audience in Unica Campaign to the AUDIENCEID field in the primary Expanded Outcome table. This mapping defines the audience on which rest of the flowchart logic should be performed.
      Note: If you plan to use Opportunity Detect Outcome data in multiple flowcharts, save the mapped table information into a table catalog and load this catalog in other flowcharts.
    2. Select records where the value in the PROCESSED field in the primary Expanded Outcome table is 0.

      This value indicates that the record has not been processed yet.

    3. Set the value in the PROCESSED field in the primary Expanded Outcome table to 1, to indicate that the record has been processed.

      You could write SQL in a Select process to set this value.

    4. In an Audience process, switch the audience from OUTCOMEID to AUDIENCEID.
    5. Use the Opportunity Detect data as desired in your flowchart.
    6. Use a MailList process to assign an offer and update contact history.
  6. Use your own scheduling utility or the Unica Scheduler to schedule flowchart runs at the desired interval; for example, every minute.