Update Members' Progress for Engagement Attributes

Use actions in loyalty program process rules to update members' progress and reward members for achieving their engagement attribute target. You can also get the details of the members' engagement attribute, and then use the details for other processes.

Required Editions

Available in: Lightning Experience

Available in: Enterprise, Performance, Unlimited, and Developer Editions with Loyalty Management

When designing rules, add actions that update a member's progress in achieving the engagement attribute target by using values from the input data.

Update Current Value for the Member Attribute

Use this action to update a member's progress for an engagement attribute. In the action, provide these inputs:

Select the engagement attribute that you want to update.
Select whether you want to increase, decrease, or overwrite the current value.
Enter the value by which you want to either increase, decrease, or overwrite the current value.

After updating the member’s values for the selected engagement attribute, the action provides a list of outputs, including:

The engagement attribute's updated value

Important When an engagement attribute meets its target, the member's attribute value resets to 0 and the excess is discarded. For example, if the PurchaseAmount target is $1,000 and a transaction pushes the total to $1,500, the value resets to 0 and the remaining $500 isn't carried over.
The engagement attribute’s target value
An indicator showing whether the target is reached

All output values are from the current process run and reflect the state after the action runs. You can store the output values in parameters and then use the values in subsequent steps.

Tip To use conditions that depend on whether a member achieved an engagement attribute target, store the Target Value Achieved value in a Boolean parameter.

When you submit multiple transaction journals in a single API request or batch:

The loyalty process rule processes them in sequence to save changes from each transaction. For example, if the TransactionCount engagement attribute is 5 and three transaction journals are processed together, each journal increments the count by 1, resulting in a final attribute value of 8.
The system evaluates the milestone target only once. Transactions within the same batch don't individually trigger milestone completion. To ensure that each transaction is evaluated against the milestone target, process them in separate batches.

Example Let's say that you want to create a rule that credits points to members who complete 10 purchases. First, create a PurchaseCount engagement attribute and set its target value to 10. Next, use this action to increment the PurchaseCount engagement attribute by 1 for each transaction. Then, after the action, add a condition that checks whether the TargetValueAchieved output parameter is true before the Credit Points action.

Get a Member's Attribute Values

Use this action to get the details of the Loyalty Program Member Attribute Value record that represents the current period of the engagement attribute that you select. In the action, select the engagement attribute for which you want to fetch the member's current period details. The action provides a list of outputs that contain the member's current period values for the engagement attribute. You can use these values for other processes.

Example In a rule that encourages members to increase engagement with the loyalty program, check which engagement attribute's target that the member is close to achieving and then send a reminder email.