Free Salesforce Salesforce-Loyalty-Management Practice Exam with Questions & Answers | Set: 3

When adding a program partner in Salesforce Loyalty Management, the required fields include:

Name, Program, Program Partnership Category, Type, Billing Type (B): This combination of fields ensures that a program partner is properly defined and categorized within the Loyalty Management system.

Name: Identifies the partner within the loyalty program.

Program: Links the partner to a specific loyalty program.

Program Partnership Category: Categorizes the partner according to the nature of the partnership (e.g., accrual, redemption).

Type: Defines the nature of the partnership, such as whether the partner is involved in point accrual, redemption, or both.

Billing Type: Specifies how the partner is billed, which could be related to transaction fees, membership fees, or other financial arrangements.

Options A, C, and D include fields like "Partnership Start Data," "Industry," and "Status," which, while important, are not the core required fields for initially setting up a program partner in Salesforce Loyalty Management.

Salesforce Loyalty Management documentation provides comprehensive details on setting up program partners, including the required fields and best practices for managing partnerships to enhance member engagement and program value.

To set up an expiration model based on activity after the last accrual transaction in a points-based Loyalty Program at Universal Container, the Salesforce Administrator should Set up Expire Activity Based Non-Qualifying Points (C). This expiration model allows non-qualifying points to expire after a certain period of inactivity, meaning no new accrual transactions occur within that timeframe. It encourages ongoing engagement from Loyalty Program members by incentivizing regular transactions to keep their non-qualifying points active.

Option A (Expire Activity Based Qualifying Points) pertains to qualifying points, which are typically used for tier progression and may have different expiration criteria. Option B (Expire Fixed Non-Qualifying Points) refers to a fixed expiration model that does not consider member activity. Option D (Set up Reset Qualifying Points) involves resetting qualifying points, which is a different concept from expiration based on activity.

Salesforce documentation on Loyalty Management would provide insights into configuring various expiration models for points within a Loyalty Program, including activity-based expiration to foster continuous member engagement and transactional activity.

For the scenario described, where a loyalty program wants to send an immediate notification after a voucher is added to a member's account, the entry event in Salesforce Marketing Cloud needs to trigger off of the creation of a record in Salesforce that contains the necessary data attributes for personalization.

Option C is the most suitable choice because it specifies an entry event based on the "Voucher," "Contact," and "LoyaltyProgramMember" objects. This approach aligns with the requirements because it directly utilizes the "first name" from the Contact object and the "membership number" from the LoyaltyProgramMember object, which are necessary for personalizing the notification message.

Moreover, Option C would likely require the least amount of development effort because it leverages existing Salesforce data and related objects without the need for additional configuration or data extensions. In contrast, other options would require the setup of a data extension or custom objects that may not be directly tied to the triggering event, thereby increasing the complexity and development effort.

In Salesforce Marketing Cloud, Journey Builder is the tool that would be used to create this customer journey. It allows for the configuration of entry events based on data changes in Salesforce, such as the addition of a voucher to a member's account. The real-time nature of this trigger is essential for the immediate notification requirement.

According to Salesforce's official documentation, using Salesforce data as the entry source for a journey allows for real-time messaging based on record creation or updates. This means that as soon as a voucher record is created or updated in Salesforce, the entry event can trigger and begin the journey, which will send the personalized notification to the member.

In practice, setting up this entry event in Journey Builder would involve specifying the criteria for the trigger (in this case, the creation of a voucher) and mapping the necessary data fields for personalization. This is consistent with Salesforce's best practices for creating personalized, real-time customer engagements through Journey Builder.

Salesforce's documentation on Journey Builder and real-time event triggers provides further details on how to configure these types of journeys and can be referred to for step-by-step guidance and the latest feature updates.

For a member who joins the NTO Insider program in the Silver tier and gets upgraded to the Gold tier on March 16, 2023, the new expiry date after the tier upgrade would be December 31, 2024 (C). This is because the tier group is defined with a Fixed Model and a Period of one year, with the Qualifying Points reset date set at December 31, 2022, and a frequency of one year. The Extend Expiration setting being tied to the Qualifying Points Reset Date means that regardless of when the tier upgrade occurs within the year, the expiration of the new tier status aligns with the annual reset date, extending to the end of the following reset period, which would be December 31, 2024.

This approach ensures that members who achieve a higher tier partway through the year enjoy the benefits of that tier for the remainder of the current year plus the entire next year, providing a full year's benefit from the point of the annual reset.

Salesforce documentation on Loyalty Management would outline the functionality and configuration options for tier groups, tier upgrades, and expiration settings, guiding administrators on setting these up to meet the program's strategic objectives and ensure clarity and fairness for members.

To award customers 500 points upon joining the Loyalty Program, two key configuration tasks are required. Firstly, a Transaction Journal with an Activity type of ‘Enrollment’ should be created to record the act of a customer signing up for the Loyalty Program. This transaction journal serves as a record of enrollment activities and is essential for tracking new members.

Secondly, a Process Rule needs to be created that awards 500 points when the Activity Type equals ‘Enrollment’. This process rule automates the awarding of points to new members, ensuring that each new enrollment triggers the addition of 500 points to the member's account. This setup ensures a standardized and automated approach to rewarding new members, enhancing the member experience from the outset.

To automate the current redemption process for non-qualifying points based on various criteria like products, regions, available dates, and tiers, the Administrator needs to first Create a decision table with input & output values (A). A decision table in Salesforce Loyalty Management allows for the specification of complex redemption rules and conditions in a structured format, making it the foundational step in automating the redemption process. This table will define how non-qualifying points can be redeemed under different scenarios, serving as the basis for the automated redemption logic.

Salesforce Loyalty Management offers seamless integrations within the Salesforce ecosystem that can be easily enabled to meet ABC Corp.'s business requirements for launching a new Loyalty program, including:

Option A: Salesforce Service Cloud, which can be integrated to manage customer service interactions and inquiries related to the Loyalty Program, enhancing the overall customer experience.

Option D: Salesforce Marketing Cloud, which allows for the creation and management of targeted marketing campaigns to engage Loyalty Program members, promote rewards, and encourage participation.

To fulfill the new voucher's requirements, the voucher definition settings should be: Type: Fixed Value, Expiration Type: Period, Expiration Period: 3, Expiration Period Unit: Month, Face Value: $300, Partial Redeemable: Checked. This configuration ensures that two vouchers with the specified face values can be issued within the defined period and used within three months after the first voucher’s disbursement date. The 'Partial Redeemable' option allows the vouchers to be used partially, providing flexibility in how they are redeemed by the members.

The root cause of the issue where all the Loyalty automations that have Data Processing Engine actions are failing is because the Default Workflow User is missing the CLAAnalytics Base User permission set license (B). This permission set license is essential for the Default Workflow User to execute actions related to the Data Processing Engine within Salesforce Loyalty Management. Without this permission set, the user lacks the necessary access rights to run these specific automations, leading to the observed failures. Salesforce documentation on Loyalty Management would provide guidance on setting up and troubleshooting automations, including the necessary permission sets for different actions.

When setting up tier groups in Salesforce Loyalty Management for a sports clothing and accessories retailer, the three necessary attributes to define are:

Qualifying period (A): This defines the time frame within which the members' activities (like purchases or interactions) contribute towards their tier status. It's crucial for determining how member activities are evaluated against tier criteria.

Tier Period (C): This attribute specifies the duration for which a member remains within a particular tier once qualified, before re-evaluation. It's important for maintaining the tier structure over time and for member expectation management.

Tier Model (D): This outlines the basis on which the tiers are structured, such as points accrued, spending amount, or other qualifying activities. It forms the foundation of the tier system, dictating how members progress through different levels.

Option B, Fixed Tier Model, is not an attribute but a type of Tier Model. Option E, Non-Qualifying Period, is not a standard attribute required for setting up tier groups in Salesforce Loyalty Management.

Salesforce documentation on Loyalty Management would detail the process of setting up tier groups, including the necessary attributes and considerations for effectively structuring a multi-tiered loyalty program.