This blog will take you through the Inbound Triggers – triggers sent from other applications to Campaign. Inbound Triggers

Inbound triggers are triggers sent from other applications to Campaign.  The other applications send information to the unica_actrg executable that resides in the bin directory (<CAMPAIGN_HOME>/bin).  The application calls unica_actrg and passes parameters:

Usage of unica_actrg
parameters can be seen by typing ‘unica_actrg’ from the command line:
Unica_actrg [-p <port.] [-s ] [-v] [ |  |
-n ] , , …
Where items enclosed in [] brackets are optional.
The | sign indicates an ‘OR’ – campaign code can be used, or campaign name or flowchart name.
-v is used to indicate the version of the Campaign Trigger Utility.
1)     All flowcharts waiting for ‘Go’
This would send a message to continue execution of all flowcharts (the * is a wildcard) waiting for the command ‘go’.
Tip:  In Unix, if there are spaces in the campaign name or flowchart name this will cause an error.  To avoid this put quotes around the asterisk.
<CAMPAIGN_HOME>/bin/unica_actrg ‘*’ Go
2)     All flowcharts waiting for ‘Go’ specifying the port.
<CAMPAIGN_HOME>/bin/unica_actrg –p 5664 ‘*’ Go
This would call the Campaign on port 5664 (if multiple versions of Campaign are installed on the same server you may need to specify the port) and send a message to continue execution of all flowcharts (the * is a wildcard) waiting for the command ‘Go’.
3)     A specific flowchart waiting for the command ‘Go’
<CAMPAIGN_HOME>/bin/unica_actrg TestFlowchart Go
This would send a message to continue execution of the flowchart ‘TestFlowchart’ waiting for the command ‘Go’.

Campaign A Triggers Execution of Campaign B
In this example Campaign A will send an outbound trigger that will then be the inbound trigger that Campaign B is waiting for.
1) Campaign B is waiting for an inbound trigger before executing.  In Campaign, B add a Schedule Process. In the ‘Schedule box’ choose Custom Run.  Select ‘Run on Trigger’ and add a trigger name, e.g. ‘Go’.
2) From the Session menu, start Campaign B.  You should see three green dots on the Schedule process. Save and Exit Campaign B.
3) Campaign A will send a message to unica_actrg to kick off Campaign B.  To set this up an outbound trigger needs to be created.
4) In Campaign A go to the Tools menu and select ‘Stored Triggers’.  
5) Click ‘New Item’.
6) Give the trigger a name, e.g. ‘Run_Flowchart_B’
7) In the ‘Command box’ type the command for the trigger.
        e.g. /opt/Campaign/bin/unica_actrg -n FlowchartB Go
8)     From a Mail List or ‘Schedule process call the trigger.  Example, in the Contact process, click on the ‘Contact List’ tab.
9)     Check ‘Send Trigger’
10)   Select the outbound trigger that was just created, Run_Flowchart_B
11) Start Campaign A.  When the file has been created (or table written/appended to) the trigger will execute and will launch Campaign B.


  Sumitra Chachar
  Product Manager
  HCL Products and Platforms

Marketing Platform, Campaign, Interact, Marketing Operations, Contact Optimization, and Opportunity Detect are trademarks of IBM Corporation, in at least one jurisdiction, and are used under license. 
Comment wrap
Further Reading
Automation | May 15, 2018
Reading and Using Campaign Log files
Log files are useful for troubleshooting and performance improvements within Campaign. Once we had a slow running flowchart at a client, and by reviewing the log file we identified that the actual issue was caused by the network traffic to the database. This helped us to fix the issue and optimize the performance of the flowchart.
Automation | May 24, 2021
The Three Keys to Success for HCL Software Support
While HCL Software as a division within HCL Technologies has grown tremendously over
Automation | October 15, 2020
Securing Remote Employees From Cyber Threats
According to Google, in April, there were more than 18 million daily malware and phishing email cases related to COVID-19 in just one week.
Filters result by