Salesforce Salesforce-Loyalty-Management - Salesforce Loyalty ManagementAccredited Professional Exam (SP25)

When designing an experiential Loyalty Program, the recommended objects to use for tracking member activities with the program are:

Loyalty Ledger & Transaction Journal (A):The Loyalty Ledger tracks the overall balance of a member's points or currencies, while the Transaction Journal records all point-related transactions, including accruals, redemptions, and adjustments. Together, these objects provide a comprehensive view of a member's interactions and engagements with the loyalty program.

Journal Type & Journal Subtype (D):These objects allow for the categorization and sub-categorization of transactions within the Transaction Journal, making it possible to track different types of member activitiesand engagements within the program, such as event attendance, purchases, or other actions.

Options B (Loyalty Member Currency & Transaction Journal) and C (Transaction Journal Type & Transaction Journal Subtype) are partially correct but do not fully capture the recommended best practices for tracking member activities in an experiential loyalty program.

Salesforce documentation on Loyalty Management would detail the use of these objects and best practices for tracking and managing member activities withina loyalty program, ensuring a rich and engaging member experience.

To enable agents to view Loyalty Program Member information on a Case record in Service Cloud, the IT Administrator shouldOn the Case Page Layout, add the 'View Member Profile' component and select the required Related Lists from Loyalty Program Member (B). This component allows for the display of relevant Loyalty Program Member information directlywithin the context of a Case record, enhancing the service agent's abilityto access pertinent loyalty information while managing customer cases.

To edit Loyalty Management objects,the "Loyalty Management" permission set license is required. This license grants users the necessary permissions to access and modify Loyalty Management-specific data and configurations.

Option B"Loyalty Management" is the correct answer as it directly relates to the permissions needed to work with Loyalty Program configurations and objects within Salesforce.

Options A, C, and D pertain to analytics and data pipeline functionalities and do not grant permissions to edit Loyalty Management objects.

To target a promotion only for specific products in a Loyalty Program, the correct implementation approach is toMapproducts to promotion through an out-of-the-box Related List (B). This approach leverages standard Salesforce functionality, allowing administrators to associate specific products with a promotion directly within the promotion's record. This direct mapping ensures clarity and ease of administration, enabling targeted promotional activities that are specific to certain products.

Option A (Create a custom list on the promotion), Option C (Create product attributes in Promotion Setup), and Option D (Add promotion to the lookup field on the product) are not standard Salesforce Loyalty Management functionalities for associating products with promotions and may require custom development or configuration that is more complex and less maintainable than using out-of-the-box related lists.

Salesforce documentation on Loyalty Management would detail the process for setting up and managing promotions, including how to associate promotions with specific products to achieve targeted marketing objectives within the Loyalty Program.

Within the Salesforce Customer Data Platform (CDP), the Loyalty Program entity is attributed with various fieldsthat help in managing and analyzing the loyalty program's performance. Two essential fields attributed to this entity are Created Date and Last Modified Date.

The Created Date field records the timestamp when the Loyalty Program entity was initially created in the system, providing a reference point for the program's inception. The Last Modified Date field, on the other hand, keeps track of the most recent update made to the Loyalty Program entity, offering insights into the program's maintenance and evolution over time.

These fields are crucial for administrative and analytical purposes, allowing businesses to monitor the lifecycle of their loyalty programs and make data-driven decisions based on the program's history and modifications.

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

PromoCode (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 vouchertypes 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.

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.

QUESTIONNO: 19

A large retail company wants to award its customers 500 points when they join the Loyalty Program.

Which two configuration tasks below will be required to enable this type of award?

A. Create a Transaction Journal with an Activity type of ‘’Enrollment’’ that needs to be created when the customer signs up to join the Loyalty Program.

B. Create a Process rule that awards 500 points when the Activity Type =’Enrollment’’.

C. Create a Loyalty Partner and associate one of the Partner’s products that mustbe purchased to award the 500 points.

D. Create a Benefit that adds 500 points when the new member reaches the Top Platinum Level tier.

Answer: A, B

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 create personalized experiences across Cloud Kicks' customer journey, the Loyalty Consultant should utilizeSalesforce Marketing Cloud (B). Marketing Cloud provides a comprehensive suite of marketing tools designed to create personalized customer journeys, segment audiences, and deliver targeted content and communications. Leveraging Marketing Cloud's capabilities in conjunction with Loyalty Management allows for the creation of highly personalized and engaging experiences for loyalty program members, enhancing customer satisfaction and loyalty.

For integrating a custom object "Member TierUpdate_c" with a journey in Salesforce Marketing Cloud for real-time tier change notifications, the correct data source option is:

Option D"Salesforce Data" as the Entry Source, with the custom object "Member TierUpdate_c" as the data source. This option allows for real-time triggering of journeys in Marketing Cloud based on updates to Salesforce records, in this case, the "Member TierUpdate_c" object which tracks tier upgrades.

Options A and B do not correctly target the custom object designed to track tier changes.

Option C, using a "Data-Extension," would not provide the real-time integration needed for immediate email notifications upon tier changes.

When configuring a new user account in Marketing Cloud for integration with Salesforce Loyalty Management, the Consultant must ensure toGrant access tothe correct business unit (B)andEnable API access (D). Access to the correct business unit is necessary to ensure that the user has access to the relevant data and functionalities within Marketing Cloud. API access is essential for the technical integration, allowing for communication between Salesforce Loyalty Management and Marketing Cloud.