Configuring Event Based Rewards in Siebel Loyalty

Administrators set up and configure Event Based Rewards in Siebel Loyalty through an intuitive UI that guides them step-by-step in setting up milestones and reward criteria.

Create an Event Reward UI Flow

Event Reward is specific to a loyalty program and should be configured as part of metadata setup.

Note: Attributes referenced in the Event Reward setup should be preconfigured and set to Active.

1. Navigate to the program where the Event Reward needs to be set up.
2. Drill down to the program name to access the LOY Program Promotions View - Admin view.
3. Search for Event Rewards from the level-three menu.
4. Create a new event record by providing:
   • Event Name: Required; free text
   • Member Attribute: Required; multi-select list (must be a date-type member attribute)
   • Subtracted Days: Default 0; number field (days to subtract from system date for the start date range)
   • Added Days: Default 0; number field (days to add to system date for the end date range)
   • Cooling Off Period in Weeks: Optional; number field. Prevents duplicate rewards within the period.
   • Ignore Year: Boolean (default N)
   • Active: Boolean (default N)
5. Set up transaction attributes for the event as needed.
   • Transaction Attribute:
     • Attribute: Multi-select list field based on Transaction Attribute
     • Member Attribute: Multi-select list field based on Member Attribute (data type level mapping between Transaction and Member Attribute – for example, string data type of Transaction Attribute is mapped with string data type of Member Attribute,and so on.)
     • Static Value: Free text field

     Transaction Attribute is the placeholder for administrators to get the event transaction created as per required data. Here, administrators are setting a transaction comment with the required information of the Event Transaction.

Set Up EDR Product Association as Service Product

1. Navigate to the program where Service Product for EDR Product Association needs to be set up.
2. Drill down to the program name to get the LOY Program Promotions View - Admin view.
3. Search for the Service Product Association from the level-three menu.
4. Select the plus sign to select the Product Name, which is Gift - Points in our case.
5. Add a Service Type as Event Rewards to complete the Service Product Association.

Simulate Transactions for Specific Events

In the LOY Program Event Rewards View, you can simulate transactions for members for a particular event.

1. Add a new entry by clicking the plus sign in the simulate applet.
2. Select a member.
3. Select Simulate to run the simulation.

Simulation Cases

• Case 1

  No value in a member field. For example, if the selected member's attribute is Member DOB and it's empty, an error will occur.

• Case 2

  If Joined Date is selected as the Member Attribute and a value is present (for example, 10/17/2025), but the member isn't within the range of added or subtracted days, the member isn't eligible for rewards, and an error is shown.

• Case 3

  If you adjust the subtracted days so that the member falls within an eligible range, the transaction is created, and the Transaction Status is set to In Progress.

• Case 4

  If you try to simulate the same member again and a transaction has already been created for them, the reason Member Transaction already created will be shown as a failure, and the simulation won't continue.

• Case 5

  If you deselect the Active mark in the program applet, the simulation will fail and the corresponding error will be displayed.

Set Up the Batch Component

1. A new batch component is available under the existing Loyalty Engine Component group with these details:
   • Name: eLoyalty Processing Engine - EventReward
   • Alias/Short Name: LoyEngineEventReward
   • Component Group: LoyaltyEngine
2. For this feature to work, enable the new batch component on the Siebel server and set the component to online.

Create Jobs to Provide Event Based Rewards to Members

1. Go to Administration - Server > Jobs.
2. Click the plus icon to create a new job.

   Enter your component name, such as eLoyalty Processing Engine - EventReward and specify your machine name as the Requested Server.

3. Create a new record at Job Parameter Applet.

4. Select Name "LOY Event Id" from the Job Parameter Pick. Provide Value of this Job Parameter as Row Id of Event Reward record setup at Loyalty Programs Administration Screen > Event Rewards View.
5. Select Submit Job.
6. After you submit the job, the status will change from Creating to Queued. Note the Job ID for tracking purposes.
7. Check the status by querying the Job ID. After the status changes to Success, you can view the Queued transactions for eligible members of provided Event Reward at Job Parameter.

Note: As an admin, if you want to run the job for only one event, make sure event is set to Active in the event setup view. Also make sure to provide row id of correct Event Reward record in Job Parameter. In case no row id is provided or job parameter is not present in the Job it will process all the active events across the programs.

Create Component for an Upgrade

In the case of an upgrade, the EventRewards component needs not to be created manually. From 26.3 onward, the batch utility will handle this automatically.

Refer to, Adding Object Manager for Loyalty Event Based Rewards.

Create Jobs for Event Based Rewards Using Siebel Server Manager Commands

Administrators can use Siebel Server Manager commands to start the event-based rewards job:

1. Connect to Siebel Server Manager.
2. Verify that the Event Rewards batch component is online by running:
   • list comps for compgrp LoyaltyEngine
3. After the component is online, start the job with the following command:
   • start task for component LoyEngineEventReward server <server_name> with LOY Event Id = <RowId of Event configured>
4. Monitor the task status by running the following command:
   • list task for comp LoyEngineEventReward
5. After the task status is Success, event rewards transactions for all eligible members will be available.