Handling multiple packages

If your post-optimization flowchart retrieves optimized contacts from more than one package, you must separate each package into distinct contact processes.

Using separate contact processes places audience IDs into their various groups, for example, High-value and Low-value.

You can handle multiple packages in your flowchart using one of the following methods:

  • Selecting more than one package from a single Extract process. This method works only when the audience IDs are guaranteed to be treated only in a single package.
  • Including one Extract process per package.

    If the same audience ID can be treated in multiple packages, you must use this approach. Otherwise, the same offers can be sent in duplicate to members of multiple packages. To retrieve results from a few packages, it might be easier to create a separate Extract process per Optimize process. Setting up a segmentation field in the Unica Optimize template table and using the Segment process in the post-optimization flowchart might be more complicated.

Proposed packages must be preserved post-optimization, since the contact fatigue rules might be based on the number of interruptions that are allowed to each individual. Rearranging the surviving offers into different packages, and therefore a different number of interruptions to the recipient, might violate your corporate contact fatigue strategy.

If you select more than one package of optimized contacts when you configure the Extract process, you must include a Segment process in your flowchart. The Segment process separates the various audience IDs from multiple packages back into individual packages. These individual packages can then be handled individually.

Note: You can retrieve multiple packages in a single Extract process only if you are certain that the audience IDs are mutually exclusive across packages. Otherwise, the audience IDs belonging to multiple packages can receive duplicate offers.

To use the Segment process to divide customer IDs into their original packages, you must include a field in the optimization template table. This field must act as an identifier for the Optimize process from which the package originated.