How You Set Up Event-Driven Rewards

Let's look at the general steps involved in setting up event-driven rewards.

Step	Description	Guide or Topic Where You Can Find More Information
1	Create a member attribute on a member date field such as date of birth, or on a dynamic attribute such as member wedding date. You use this attribute when creating the event	Create Program-Level Attributes
2	Create an event-driven reward specifying the event parameters described in this topic.	Example of an Event Driven Reward
3	Create an event transaction attribute with the Comment transaction type. You use this attribute when setting up the related promotion.	Create Program-Level Attributes
4	Create a promotion with the condition for the event-driven reward. Use promotion type Accrual, and sub-type Event Reward.	How You Create a Promotion
5	Run the Loyalty Event-Driven Rewards Main Job to generate event reward transactions and place them in the queue. This job checks events against the member date attribute for each member to create transactions of type Accrual-Event.	Create a Batch Process
6	Run the Loyalty Batch Engine Main Job. Event reward transactions automatically process along with all other transactions when you run this job. The job checks event promotions and issues rewards to members with qualifying data.	Create a Batch Process

Event Parameters

Here are the event parameters you set when creating an event using REST.

Event Parameter	Description
Event Name	A name for the event, such as Member Birthday.
Member Attribute	The name of the member attribute you defined for the event, such as Date of Birth.
Subtracted Days	The number of days to subtract from today's date to begin the event trigger. For example, if the value is 5, the Loyalty Event-Driven Rewards Main Job creates transactions for all members with qualifying dates that are up to 5 days earlier than the event date.
Added Days	The number of days to add to today's date to end the event trigger. For example, if the value is 2, the Loyalty Event-Driven Rewards Main Job creates transactions for all members with qualifying dates that are up to 2 days later than the event date.
Cooling Period (Weeks)	The period, in weeks, during which the reward won't repeat if the Loyalty Event-Driven Rewards Main Job runs again. Once a job creates an event transaction for a particular member, it waits until the cooling off period is complete before it can generate another. For a birthday, for instance, you might set the cooling off period to 48 so that a member can't be rewarded again until their next birthday. For a monthly event-driven reward, the cooling off period could be 4 weeks. Coordinate this parameter with how frequently you run the Loyalty Event-Driven Rewards Main Job.
Ignore Year	Indicates whether the event trigger considers the year (Y or N). If an event is repeatable, such as a birthday, set the value to Y. This event doesn't consider the year, just the day and month. For one-time events where you want to take the year into consideration, such as the date of last purchase, set the value to N.
Active	Indicates whether the event is active (Y or N).