You are here:
Overview of the Change Member Tier Process Template
Learn about the Change Member Tier process template and its components. Also, understand how you can use the template to create a loyalty program process and execute the process.
Required Editions
| Available in: Lightning Experience in Enterprise, Performance, Unlimited, and Developer Editions |
| Available in: Orgs that have the B2C - Loyalty, B2C - Loyalty Plus, B2B - Loyalty, Loyalty Management - Growth, or Loyalty Management - Advanced license enabled |
What Does the Template Contain?
The template contains a rule and set of parameters. The Change Member Tier rule has only one rule step to upgrade or downgrade the tier of loyalty program members in the loyalty tier group based on the input parameters. The parameters store values that the rule uses to change member’s tiers.
| Rule Step Name | What Does the Rule Step Do? | Parameters used in the Step | What Does the Parameter Do? | Examples of Customization |
|---|---|---|---|---|
| Change Member Tier | Upgrades or downgrades a member’s tier based on the input parameters. | ReasonForChange | This input parameter stores the reason for changing the member’s tier: Resolve Tier Conflict, VIP Member, and Based on Past Activities or Tier. Include any new reasons, if required. | If your program has multiple tier groups, then you can customize the change tier action for each tier group by cloning the Change Member Tier template and selecting the required tier group. Each clone is applicable for one tier group only. |
| NewTier | This input parameter stores the name of the tier that the member is being changed to. | |||
| CustomTierExpirationDate | This input parameter stores the custom date on which the new tier must expire. For example, to reward achievements such as joining a partner program, upgrade member tiers for a specific duration. | |||
| Previous Tier | This output parameter stores the name of the member’s tier before change. | |||
| CurrentTier | This output parameter stores the name of the member’s current tier. | |||
| EffectiveDate | This output parameter stores the date on which the member tier is effective. | |||
| TierExpirationDate | This output parameter stores the date on which the member tier expires. | |||
| HasTierUpgrades | This output parameter indicates whether the tier change is an upgrade. |
How Can You Execute the Processes Created Using the Change Member Tier Process Template?
Loyalty Management provides a Business API to execute processes created by cloning loyalty program process templates. You can integrate the external system and Loyalty Management with the Change Member Tier API by executing it as per the input parameters.
- The API is executed when you want to change the tier of your loyalty members in the loyalty tier group.
- The MemberId or MembershipNumber, CurrentTier, and ReasonForChange are provided in the API request.
In the API, you must specify these values to execute the API for your cloned process:
- In the API endpoint, specify the API name of your cloned process.
- In the API request, specify the values for the parameters that are used in the Change Member
Tier rule.
You must specify the MembershipNumber or MembershipId, NewTier, and ReasonForChange to change the member’s tier.
When you execute the API, it runs the loyalty program process and the process changes the member’s tier using the value provided in the API request.
Examples of How You Can Use the Template
You can clone and extend the template based on your requirements. Here’s one you can use the process template:
| Use Case | How to Achieve the Use Case? |
|---|---|
| When a member upgrades a tier, you want to issue a voucher. | From the cloned process, go to the Change Member Tier rule and add a rule step to issue a voucher.
|
