Bookshelf Home | Contents | Index | PDF |
Siebel Marketing User Guide > Designing Marketing Programs > About Using the Program Flow > About Using Triggers with Campaign StagesTriggers detect an event automatically and trigger the appropriate program stage. Actual event detection is performed by an external event triggering framework, such as a third-party database trigger, Oracle Business Activity Monitoring Engine (BAM), or workflows that monitor the creation of records in a Siebel OLTP table. The event detection application notifies the Siebel Marketing application to implement a trigger. The integration point between the external detection application and Siebel Marketing is an event repository, which stores references to event definitions and key parameters that the program might need from the event application. The Create Event Trigger and Execute Event Trigger SOAP API Web services allow the external event detection application to populate the event repository with data for the event attributes. For more information on Web services, see Siebel CRM Web Services Reference. You can manage the event repository by navigating to the Administration-Marketing screen, then the Triggers view. NOTE: A triggered stage cannot be scheduled. A scheduled stage cannot be triggered. Trigger-Based Execution of Marketing ProgramsOnce a trigger is associated with a campaign, the event capture application sets the steps illustrated in Figure 1 in motion. These steps are as follows:
Figure 1 illustrates trigger-based execution of marketing programs. If the Execute Event Trigger Web service is called in batch mode (that is, if Real Time Flag is set to N), then all the records remain queued in the History table and are picked up when the number of records reaches the threshold specified in the Stage Allocation Threshold server parameter. All the customer Ids are then concatenated and sent to Oracle BI as a single, comma-separated Id and are then processed. For information about adding a trigger to a campaign, see Adding Triggers to a Campaign Stage. NOTE: Real Time Flag is a parameter for the stage threshold in the Marketing Event Trigger Execution Web service. You can change this value when calling this Web service. Real Time Flag is a case-sensitive parameter. To enable throttling during a campaign load, a parameter called '"-Contact Profile".ROW_ID' stores the Customer Id value in the Get List Format System Data step of the Marketing Campaign Load workflow. You can enable throttling on other parameters by adding them to the same workflow step. You can also use the '"-Contact Profile".ROW_ID' parameter to enable throttling in the Marketing Create Lead and Marketing Create Responses workflows. If you have modified the name of the Contact Profile variable in Oracle Business Intelligence, then be sure to modify the parameter name to match. |
Siebel Marketing User Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |