Home
User Guide
Unica Campaign is a web-based solution that enables you to design, run, and analyze direct marketing campaigns.
Flowchart management
Unica Campaign flowcharts define the campaign logic. Each flowchart in a campaign performs a sequence of actions on data that is stored in your customer databases or flat files.
Running flowcharts
You can do a test or production run on an entire flowchart, a branch, or an individual process in the flowchart. You can also validate flowcharts. For best results, conduct test runs and perform validation as you build a flowchart, so that you can troubleshoot errors as they occur. Be sure to save each flowchart before you do a test or production run and before you perform validation.
Testing a flowchart
Conduct test runs as you build a flowchart so that you can troubleshoot errors as they occur. You can then view a report of any errors in the flowchart.

User Guide
Unica Campaign is a web-based solution that enables you to design, run, and analyze direct marketing campaigns.
- Unica Campaign overview
  Unica Campaign is a web-based solution that enables you to design, run, and analyze direct marketing campaigns.
- Creating and managing campaigns
  One of the first things you do in Unica Campaign is to create a marketing campaign to identify your objective. Each campaign is defined by its business objective, initiative, and effective date range. A campaign always consists of at least one flowchart, where you select recipients and assign offers. You can create, view, edit, delete, and perform similar operations on marketing campaigns.
- Designing flowcharts
  Unica Campaign flowcharts define the campaign logic. Each campaign consists of at least one flowchart. A flowchart performs a sequence of actions on data that is stored in your customer databases or flat files.
- Flowchart management
  Unica Campaign flowcharts define the campaign logic. Each flowchart in a campaign performs a sequence of actions on data that is stored in your customer databases or flat files.
  - Email notification management
  - Validating flowcharts
    When you validate a flowchart, each process is checked for errors. Each error that is found displays in succession so you can view and correct each one. A best practice is to run validation on flowcharts before you do a production run. This is especially important if you are running scheduled flowcharts; using batch mode; or you are not planning to actively monitor the run.
  - Running flowcharts
    You can do a test or production run on an entire flowchart, a branch, or an individual process in the flowchart. You can also validate flowcharts. For best results, conduct test runs and perform validation as you build a flowchart, so that you can troubleshoot errors as they occur. Be sure to save each flowchart before you do a test or production run and before you perform validation.
    - Testing a flowchart
      Conduct test runs as you build a flowchart so that you can troubleshoot errors as they occur. You can then view a report of any errors in the flowchart.
    - Running a flowchart
      When you do a production run of a flowchart, the data that it generates is saved in system tables. After you run and save the flowchart, you can view the results of the run in reports.
    - Running a flowchart branch
      If you run only a process or a branch, the Run ID of the flowchart is not incremented.
    - Pausing a flowchart run
      When you pause a running flowchart, branch, or process, the server stops running but saves all of the data that was already processed. When you stop a flowchart run, the results of any currently running processes are lost and a red "X" appears on those processes.
    - Continuing a stopped flowchart run
      If you stopped a flowchart run, you can continue the run by running the flowchart branch that begins with the process where the run stopped. That process is rerun along with all downstream processes.
    - Continuing a paused flowchart run
      When you continue a paused run, the run resumes at the exact point at which it stopped. For example, if a Select process was paused after processing 10 records, it resumes by processing the 11th record.
    - Troubleshooting runtime errors
  - Working with flowchart log files
    Each flowchart has its own log file, named CampaignName_CampaignCode_ FlowchartName.log. By default, flowchart log files are saved in Campaign_home/partitions/partition_name/logs.
  - Searching for flowcharts and flowchart-related objects
    Use Search flowcharts to find a flowchart or a flowchart-related object by entering one or more characters as search criteria.
  - Copying flowcharts
    Copying an existing flowchart saves time because you can start with a completed flowchart and modify it to meet your needs.
  - Reviewing flowcharts
    Depending on your permissions, you might be allowed to review, but not edit, flowcharts. Reviewing a flowchart means you can look at process configurations and make changes, but you cannot save any changes or perform production runs. The flowchart auto-save option is disabled and cannot be enabled. To save changes to a flowchart, you must have Edit permissions.
  - Viewing flowcharts in Read-Only mode
    If you have View permissions for a flowchart, you can open it in Read-Only mode to see which processes are used and how they are connected. However, you cannot open process configuration dialogs or make any changes.
  - Viewing two flowcharts side-by-side
    Some Unica Campaign designers prefer to view two flowcharts side-by-side when developing new flowcharts. When using Internet Explorer, you must use File > New Session to open additional browser windows.
  - Viewing history of flowcharts
    You can view the history of the Unica Campaign Flowcharts and the events (activities) associated with them.
  - Printing flowcharts
    You can print hardcopies of flowcharts from Unica Campaign.
  - Deleting flowcharts
    You can delete a flowchart if you are sure that you no longer need it.
- Send Time Optimization
  Send time optimization calculates the best time to contact the target customer via various channels based on past interactions.
- Offer management
  Offers are specific marketing communications that you send to particular groups of people, using one or more channels. Each offer is based on an offer template that a Unica Campaign administrator defines.
- Target cell management
  A cell is a group of people that you want to target, such as high value customers. A target cell is a cell that has an offer assigned to it.
- Contact history
  Unica Campaign maintains contact history to record information about offers that are sent to contacts. History is also recorded about control cells, to identify customers who are purposely not sent the offer.
- Unica Campaign response tracking
  Use the Response process in a flowchart to track the actions that occur after a campaign. When you run the Response process, data is recorded in the response history tables and is available for the Unica Campaign performance reports.
- Stored objects
  If there are campaign components that you use frequently, you can save them as stored objects. Reusing stored objects across flowcharts and campaigns saves time and ensures consistency.
- Session flowcharts
  Sessions provide a way to create persistent, global "data artifacts" for use in all campaigns. Each session contains one or more flowcharts. Running a session flowchart makes the outcome of the session (the data artifacts) available globally to all campaigns.
- Unica Campaign reports overview
  Unica Campaign provides reports to aid in campaign and offer management.
- Special characters in Unica Campaign object names
  Some special characters are not supported in any Unica Campaign object names. In addition, some objects have specific naming restrictions.
- Packaging flowchart files for troubleshooting
  If you need help from HCL to troubleshoot a flowchart, you can automatically collect relevant data to send to the Technical Support.

Doing a test run of a process, branch, or flowchart

Conduct test runs as you build a flowchart so that you can troubleshoot errors as they occur. You can then view a report of any errors in the flowchart.

Before you begin

Always save an edited flowchart before you do a test run. When you do a test run, be aware of the following:

Test runs do not update any tables or files. However, triggers run on completion of test runs and global suppression is applied.
The option Advanced settings > Test run settings > Enable output determines whether output is generated during test runs.
When you test run a data manipulation process (Select, Merge, Extract, Audience), you can limit the number of records. Use the Limit output cell size option on the Cell Size Limit tab in the process configuration dialog.
Results from a previous test run are lost.
If a process requires data from an upstream process, you might have to run the upstream process first so that its data is available to the downstream process.

Procedure

Open a flowchart in Edit mode.
To test run a process or branch, right-click a process, open the Run menu and select Test run selected process or Test run selected branch.
To test run blue process boxes only, open the Run menu in the toolbar and select Test run blue process boxes only. When we choose Test run blue process boxes, all data manipulation processes (Blue Process Boxes) run in test mode, stop when any Red Process Boxes are detected, and the Blue Process Boxes that follow the Red Process Box will not be run.
To test run the entire flowchart, open the Run menu in the toolbar and select Test run flowchart.

The process, branch, or flowchart runs in test mode. Each process that runs successfully displays a green check mark. If there are errors, the process displays a red "X".
If you want to pause or stop the run, right-click a process box and select Pause or Stop from the Run menu.
Use one of the Save options in the toolbar. If you click Save and exit before the flowchart finishes the test run, the flowchart continues to run and is saved when it finishes. If anyone reopens the flowchart while it is still running, any changes made to the flowchart are lost. For this reason, always save a flowchart before you run it.
To determine if there were any errors in the run, click the Analysis tab and view the Campaign flowchart status summary report.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.