Loyalty Promotion Activation

Review an Active Promotion’s Rule

A loyalty program process rule is created for each loyalty promotion. The rule is part of an Accrual type loyalty program process whose journal type is the same as the journal type of the promotion. If your company’s loyalty program doesn’t have a process that matches the promotion’s journal subtype, first a process is created and then the rule is added to the process. If a promotion doesn’t have a journal subtype, the promotion’s rule is added to the Accrual type loyalty program process available in the org. If your org doesn’t have an Accrual type loyalty program process, first an Accrual type process is created and then the promotion’s rule is added to the process. A process that’s created for a loyalty promotion rule consists of the journal type and subtype that are applicable to the process and to the promotion.

The rule that’s created for a loyalty promotion is activated when you create the promotion. You can’t deactivate a loyalty promotion’s rule. The rule is automatically deactivated when you deactivate the promotion from the Quick Promotion wizard.

The rule has the same name as the promotion. The promotion creation date is added to the name of the rule so that you can create multiple promotions with the same name.

The rule of a promotion automatically ignores transactions when:

• The member doesn’t belong to the promotion’s target Data Cloud segment.
• The member hasn’t purchased either a product eligible for the promotion or a product from the promotion’s eligible product categories.

The rule consists of conditions and actions. The conditions check if transactions are eligible for the promotion. The actions reward members for eligible transactions.

If you offer a promotion for a member event such as a member birthday or membership anniversary, a parameter is added to the rule’s loyalty program process. The parameter stores the date range of the member event. A condition uses this parameter to check if transactions are eligible for the promotion based on the date range of the event. For example, if you offer a promotion on a purchase during a member’s birthday week, the parameter stores the exact date of the member’s birthday week.

Review a Promotion’s Engagement Attributes

Engagement attributes track the number of times each member gets a reward through a promotion when the reward has a limit. When a promotion provides the same reward to all the members and the reward has a limit, an engagement attribute is created to track the reward limit. If a reward changes based on member tier, a unique engagement attribute is created to track the reward limit for members of each tier. The Loyalty Program Engagement Attribute records store the limit for a reward in the Target Value field.

The first time a promotion’s rule finds a member’s transaction eligible for a reward, a Loyalty Program Member Attribute Values record is created for the reward and the associated member. This record tracks the number of times the promotion provides the reward to the member. The record uses the Target Value field to store the member’s limit for a reward and the Current Value field to store the number of times the member is rewarded.

Each time a member is eligible for a reward, the promotion’s rule updates the current value of the corresponding Loyalty Program Member Attribute Values record by one. A condition then checks if the member has already crossed the limit of the reward. If the member hasn’t exceeded the limit, then the member gets the reward.