Salesforce-Loyalty-Management Salesforce Loyalty ManagementAccredited Professional Exam (SU24) Questions and Answers

To monitor members' tier history in the dashboards from the Analytics Studio App, the two fields that need to be enabled in field history tracking on the Loyalty Member Tier object are:

Change Reason Type (B): This field captures the type of change (e.g., manual adjustment, system-generated change) that led to the tier change, providing context for the tier history.

Reason for Change (D): This field provides specific reasons for the tier change, offering detailed insights into why a member's tier was adjusted, which is valuable information for analyzing member behavior and program effectiveness.

Option A (Loyalty Tier Group) and Option C (Loyalty Tier) are important fields for understanding tier structures and member status, but they do not specifically relate to tracking changes or the reasons behind tier history, which are crucial for analytical purposes.

Salesforce documentation on Loyalty Management and Analytics would provide guidance on configuring field history tracking and leveraging Analytics Studio to create insightful dashboards that monitor and analyze members' tier history, aiding in strategic decision-making and program optimization.

In Salesforce Loyalty Management, the types of vouchers that can be configured include:

Promo Code (A): This voucher type allows members to redeem a code for a specific offer or discount, typically used in marketing promotions and online purchases.

Discount Percentage (B): This type of voucher provides a percentage-based discount on products or services, offering flexibility in creating varied promotional offers for loyalty program members.

Fixed Value (C): Fixed Value vouchers offer a specific monetary value that can be applied as a discount or credit towards purchases, providing a straightforward benefit to loyalty program members.

The option D, "Gift Card," and E, "Product or Service," while potentially part of a loyalty program's offerings, are not classified as voucher types within the standard configurations of Salesforce Loyalty Management. Vouchers are typically used for discounts or special offers rather than representing a stored monetary value or specific products/services.

The Salesforce Loyalty Management documentation would include detailed information on configuring and managing different types of vouchers, ensuring that loyalty program administrators can effectively create and offer a variety of benefits to meet their program's goals and member needs.

For Northern Trail Outfitters to display member information in its external member portal, a crucial prerequisite is the creation of a Connected App in Salesforce Platform. This Connected App facilitates secure API access to Salesforce data, including Loyalty Management information, by providing an authentication and authorization framework.

By setting up a Connected App, Northern Trail Outfitters can establish a secure connection between its external member portal and Salesforce, enabling the retrieval of member information through Loyalty APIs. This setup ensures that the external portal can access up-to-date loyalty data, such as member points, tier status, and transaction history, in a secure and controlled manner, enhancing the member experience outside of Salesforce.

To accomplish the hotel group's goals, a Loyalty Consultant should use Non-Qualifying Points as the currency type for the Loyalty program. Non-Qualifying Points are ideal for rewards that do not contribute to tier progression but can be redeemed for benefits, such as a free night's stay. This setup allows members to earn points based on their stays, which can then be redeemed for rewards within the hotel group, encouraging more frequent bookings and enhancing member loyalty.

In Salesforce Loyalty Management, member engagement attributes are used to track and reward customer behaviors that are not directly tied to transactions. In the scenarios provided:

Member is eligible for ‘Bonus days” if the member constantly spends more than $500 each month for a year (A): This scenario is ideal for using member engagement attributes to track consistent high spending over a year. The attributes can be used to monitor monthly spending and, once the criteria are met, trigger the bonus days reward.

Member attends three trainings between March 1st and April 30th to get 200 bonus points (B): This is another perfect use case for member engagement attributes. The attributes can be set to track participation in specific events (like training sessions) and award points when the member meets the attendance requirement.

Member buys apparel online and gets 400 bonus points if the member belongs to Gold Tier only (C): This scenario is more about transactional behavior combined with tier status, which might not necessarily require the use of engagement attributes. Instead, this could be managed through regular transactional rules and tier benefits.

Member enrolls in “welcome aboard” promotion for free surprise gift every quarter (D): While engagement attributes could potentially track enrollment in promotions, this scenario seems more straightforward and could be managed through the promotion and voucher functionalities in Salesforce Loyalty Management without the need for engagement attributes.

Engagement attributes are particularly useful for tracking non-purchase behaviors and engagements, providing a flexible tool to reward members for a wide range of activities, enhancing their loyalty and engagement with the program. The Salesforce Loyalty Management documentation provides extensive guidance on configuring and using member engagement attributes effectively.

To enable users to access a new analytics app, it's crucial to assign them the appropriate roles and permission sets. Assigning user access to the analytics for Loyalty role ensures that users are granted the necessary permissions to view and interact with the Loyalty analytics content. This role is designed to encompass the permissions required for accessing and analyzing Loyalty-specific data.

Additionally, assigning user access to permission sets for analytics for Loyalty is an effective way to provide access. Permission sets offer a flexible and granular approach to managing user permissions, allowing Administrators to specify the exact capabilities each user should have within the analytics app. This method ensures that users have access to the appropriate analytics tools and data relevant to their roles and responsibilities within the Loyalty program.

To integrate Salesforce Marketing Cloud with Loyalty Management with minimal development effort, the recommended approach is:

Option D: Installing and configuring Marketing Cloud Connect. This tool facilitates seamless integration between Salesforce CRM platforms, including Loyalty Management, and Salesforce Marketing Cloud, enabling the synchronization of data and the automation of personalized email campaigns to Loyalty Program members.

To configure tiers within the Loyalty Program at Northern Trail Outfitters (NTO) for giving vouchers to members in the Premium Tier, the configuration involves Voucher Management; Benefits Setup (in Program console); Benefit Action to define downstream actions and FLOW - Benefit action for orchestration (C). This comprehensive approach allows for the creation and management of vouchers as benefits associated with the Premium Tier, the setup of these benefits within the Loyalty Program console to specify the conditions and entitlements, and the use of Salesforce Flow for orchestrating the process of issuing vouchers to qualifying members.

This method ensures that vouchers are systematically managed, associated with the correct tier and member eligibility criteria, and efficiently distributed to members through automated processes, enhancing the value and appeal of the Premium Tier.

Salesforce documentation on Loyalty Management would detail the steps for setting up and managing tier-based benefits, including the use of Voucher Management and Flow for effective benefit administration and member engagement.

Salesforce Loyalty Management offers two types of currency out-of-the-box that can be configured to accomplish the company's objectives for rewarding members based on purchases and engagement:

Non-Qualifying Points and Qualifying Points (B): Non-Qualifying Points are typically used for redemption purposes, allowing members to redeem these points for rewards or benefits. Qualifying Points, on the other hand, are often used to determine a member's tier or status within the loyalty program, often based on their purchases or engagement activities.

Fixed Model and Activity Model (option A), Activity Points (option C), and Fixed Model in combination with Qualifying Points (option D) are not types of currency offered by Salesforce Loyalty Management. The system specifically uses Non-Qualifying and Qualifying Points to differentiate between points that contribute to tier status and those available for redemption.

Salesforce documentation on Loyalty Management would detail the configuration and use of these currencies within a loyalty program, including how they can be tailored to meet specific program objectives.

In the reference integration between Salesforce Loyalty Management and Commerce Cloud, two key features are supported: 'Loyalty member profile' and 'Loyalty member enrollment.' The 'Loyalty member profile' feature allows for the management and viewing of loyalty member information within Commerce Cloud, providing a seamless experience for members as they interact with the brand across different platforms. The 'Loyalty member enrollment' feature enables new customers to join the loyalty program directly through Commerce Cloud, facilitating the growth of the loyalty program and enhancing customer engagement by leveraging the commerce platform.

For creating a large multi-country, multi-currency, and tier-dependent Redemption Catalogue, the recommended approach is to Create a Decision Table and define the Redemption Catalogue as business rules (C). A Decision Table allows for the efficient management of complex business rules and conditions, such as those involved in a multi-faceted Redemption Catalogue, providing a clear and structured method for defining redemption options based on various criteria like country, currency, and loyalty tier.

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.

Personalized benefits for each Loyalty Program member can be displayed On the Member Benefit Related List, linked to Loyalty Program Member (B). This related list can be configured on the Loyalty Program Member page layout to show the specific benefits that a member is entitled to, based on their tier and personalized criteria. This setup allows for a clear and organized display of benefits, making it easy for members and administrators to understand the perks associated with each member's status.

For Northern Trail Outfitters' Loyalty Program offering, the Administrator should configure:

B: One qualifying currency to track points that can be redeemed for products.

C: A tier system based on cumulative spending to gamify and reward top spenders with exclusive benefits.

E: Promotions to create special offers or rewards that can enhance the Loyalty Program's appeal and engagement.

To meet the hotel group’s requirements for providing live updates to Loyalty members about their program membership without complex customization, the following three tasks should be implemented:

LoyaltyLedger: This feature allows members to view their points balance and transaction history1. It is a key component of the Loyalty Management product that tracks the accumulation and redemption of loyalty points, which is essential for members to stay informed about their membership status.

Contact Record: Maintaining up-to-date contact records is crucial as it ensures that members can receive notifications and access their membership details1. The contact record in Salesforce is the central repository of member information, which can be used to personalize communication and provide members with relevant updates.

LoyaltyMemberTier: Implementing the LoyaltyMemberTier feature enables members to see their current tier status and understand how they can move to the next tier1. This feature motivates members to engage more with the loyalty program by providing them with clear goals and benefits associated with each tier.

These features are part of the Salesforce Loyalty Management application and are designed to enhance customer engagement without requiring extensive customization. They enable the hotel group to provide a seamless experience for members to access their loyalty program details.

When creating and managing member groups in Salesforce Loyalty Management, administrators should consider the following key facts:

Groups are associated with tiers (A): This statement is not necessarily true as groups can be created for various purposes, not just tied to specific tiers. Groups can be used to segment members for targeted promotions, communications, or benefits irrespective of their tier status.

Accrual type transactions associated with a group can be canceled (B): This is an important consideration as it implies that transactions contributing to a group's accrual points can be adjusted or canceled if necessary, affecting the group's total points and potentially members' benefits.

Qualifying points can’t be transferred to a group (C): This is a critical consideration because it highlights the limitation that individual member's qualifying points cannot be directly transferred into a group's pool of points. This ensures the integrity of qualifying points for tier progression and other individual benefits.

Vouchers can’t be issued to groups (D): This is another important consideration. While individual members within a group can receive vouchers, a voucher cannot be issued at the group level. This ensures that benefits are tailored and distributed to individual members, maintaining personalization in the loyalty program.

Promotions can’t be offered to groups (E): This statement is incorrect. Promotions can indeed be targeted at specific groups, allowing for more tailored marketing efforts and member engagement strategies within the loyalty program.

References to Salesforce documentation on Loyalty Management would provide detailed guidelines on how to effectively create, manage, and leverage member groups within a loyalty program, ensuring that administrators are well-informed of these considerations.

For migrating "members-record" from an SQL database into Salesforce Loyalty Management, the correct combination of objects to use is:

D: "LoyaltyProgramMember," "LoyaltyMemberTier," "LoyaltyMemberCurrency," "Contact," and "Account" Object. This combination covers all necessary aspects of Loyalty Program members' records, including personal information, tier status, and point balances.

To enable the Data Processing Engine for processing tier assessment rules on members' anniversary dates, the required permission set is:

Data Pipelines Base User (B): This permission set grants the necessary access to configure and manage Data Processing Engine definitions, allowing for the transformation of Salesforce data and the writing back of transformation results as new or updated records. This capability is crucial for automating tier assessments and other data-intensive processes within Salesforce Loyalty Management.

Options A (CLA Analytics Base Admin), C (Rule Engine Designer), and D (Loyalty Analytics Admin) do not specifically pertain to enabling the Data Processing Engine for tier assessment and other data processing tasks within Loyalty Management.

Salesforce documentation on Loyalty Management and Data Processing Engine would provide insights into the required permissions and best practices for setting up and managing data transformations and tier assessments within a loyalty program.

For this segmentation requirement, the key is to identify members whose membership will expire at the end of the current month and to ensure the segment is refreshed daily within the specified date range.

Option B is correct because using "This Month" for the "Membership Expiry Date" attribute will accurately segment members whose memberships expire at the end of the current month.

Option D is also correct because setting the "Publish Schedule" to "24 hours" ensures the segment is refreshed daily, capturing new members meeting the criteria as the month progresses. The "Start Date" and "End Date" should be set from the 1st of April to 30th of June to match the requirement.

Option A is not suitable because "Don't Refresh" would prevent the segment from updating daily, which is necessary to capture new members as their membership expiry dates become relevant.

Option C using "Next Number of days" = 30 might incorrectly include members whose memberships expire in the next 30 days from the current date, not specifically at the end of the current month.

To enable real-time updates of point balances in a points-based Loyalty Program, the Salesforce Administrator should:

Option B "Enable Real-Time Update of Qualifying Points Balance." This feature ensures that any changes to a member's qualifying points balance are immediately reflected, allowing for real-time communication of point updates.

The Data Processing Engine is the key component in Salesforce Loyalty Management for quickly aggregating a high volume of data spread across many Loyalty Management objects. It is designed to efficiently process and manage large datasets, enabling the aggregation, analysis, and application of loyalty data across the platform. This capability is essential for handling the complex data structures and high transaction volumes typical of loyalty programs, ensuring accurate and up-to-date loyalty information.

When using extensive Data Processing Engine (DPE) jobs to modify Salesforce data at scale, the two limits that should be monitored are:

Option A "Record Storage Limits," as extensive data processing and modification can significantly impact the volume of data stored in Salesforce, potentially reaching storage capacity limits.

Option C "Data Pipeline Limits," since DPE jobs involve data processing tasks that may be constrained by the limits of Salesforce's data processing capabilities and resources.

To integrate real-time point earning from an external eCommerce system into Salesforce Loyalty Management, utilizing an AppExchange app can be an efficient solution. These apps are designed to bridge Salesforce with external systems, enabling seamless data exchange. When a Loyalty Program Member makes a purchase on the eCommerce platform, the app can facilitate the automatic creation of 'Transaction Journals' in Salesforce, reflecting the earned points in real-time. This approach minimizes the need for custom development, leveraging pre-built solutions to enhance the loyalty experience and maintain accurate, up-to-date member point balances.

To add a new accrual and redemption partner to a Loyalty program in Salesforce Loyalty Management, the steps are:

Enter the program partner name > Associate to an account > Set program partner type to ‘Both’ (Accrual and Redemption) (A): This process involves identifying the new partner by name, associating them with a specific account in Salesforce to link their business details, and defining their role in the loyalty program as both an accrual and redemption partner. This ensures that the partner can both award points to members for eligible transactions and redeem points for rewards, enhancing the program's value and appeal to members.

Options B, C, and D offer variations that do not align with the standard process for adding a new partner in Salesforce Loyalty Management. The correct procedure involves associating the partner with an account (not just a contact) and specifying their role in terms of point accrual and redemption to ensure clear and effective partnership management within the program.

Salesforce Loyalty Management documentation provides guidelines on adding and managing program partners, including the steps to integrate new partners effectively, ensuring they contribute positively to the loyalty program's goals and member experiences.

To restore expired points for a member in a Loyalty program with a fixed model expiration for non-qualifying points and set them to expire in the next two months, the Member Services Agent should:

Use 'Adjust Points' action on Loyalty Program Member page to credit points and select the Points Expiration Date as two months from the current date (B): This action allows for the direct adjustment of the member's points balance, including the ability to specify a new expiration date for the credited points. It's a straightforward and effective way to restore expired points and set a new expiration date, aligning with the member's request.

Deleting the transaction journal that expired the points (option A), editing the 'Credit' ledgers (option C), or editing the Loyalty Member Currency record (option D) are not standard practices for restoring expired points and setting a new expiration date in Salesforce Loyalty Management.

Salesforce documentation on Loyalty Management would detail the process for adjusting points, including how to handle requests for restoring expired points and setting new expiration dates, ensuring member satisfaction and program integrity.

To address the issue of missing promotion vouchers for members who purchased coats, the Loyalty Administrator should review:

A: Ensure the promotion has been accurately created with the right characteristics and dates, and that the Voucher Definition is correctly associated. This verifies that the promotion is set up to trigger the desired rewards (hat and gloves) for qualifying purchases (coat).

C: Confirm that the flow intended to apply the promotion is active and properly configured. This flow is responsible for detecting qualifying transactions and applying the voucher to the member's account.

To present Loyalty Program data to the Marketing Manager, an Administrator needs to enable CRM Analytics and create a Loyalty app within it. CRM Analytics (formerly Einstein Analytics) allows for the creation of custom analytics apps that can visualize and analyze data from various sources, including Salesforce Loyalty Management. By creating a Loyalty app within CRM Analytics, the Administrator can design dashboards and reports specifically tailored to the needs of the Marketing Manager, providing insights into the reward program's progress and effectiveness.

To integrate Marketing Cloud with Loyalty Management for creating journeys for promotions, the most effective method is:

Option D "Use Marketing Cloud Connect." Marketing Cloud Connect integrates Salesforce CRM data with Marketing Cloud, allowing for the creation of targeted, personalized journeys based on Salesforce data, including Loyalty Management data.