Salesforce-Loyalty-Management Salesforce Loyalty Management Accredited Professional Exam (SP24) Questions and Answers

For configuring a tier point reset in Salesforce Loyalty Management that occurs once every two years, the administrator needs to consider:

• The qualifying point reset date, period, and frequency are set on the tier group (B):This setting ensures that members' qualifying points are reset according to the specified schedule, in this case, every two years. This reset mechanism is crucial for maintaining the program's competitiveness and encouraging ongoing member engagement.

The option A, "The Loyalty tier group field is populated," is a prerequisite for tier management but not directly related to the reset settings. Options C and D, regarding the Currency type field, are not relevant to the tier point reset settings, as the resetpertains to the accumulation and expiration of qualifying points within the tier structure, not the currency type.

Salesforce Loyalty Management documentation would provide detailed instructions on configuring tier resets, including the impact of different settings on member tiers and how to communicate changes effectively to maintain member satisfaction and engagement.

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 formaintaining 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.

To troubleshoot and correct the issue of a Loyalty member missing benefits despite achieving Gold tier status, the Administrator should first confirm that the member is assigned to the correct tier and that the tier includes the expected benefits. This involves checking the member's tier assignment within the Loyalty Program to ensure it reflects their Gold status and reviewing the associated tier benefits to confirm they are correctly configured and active. This step is crucial in identifying any discrepancies or issues in tier assignment or benefit configuration that may be causing the member to miss out on their entitled benefits.

To analyze the performance of the Loyalty Program, a System Administrator needs the 'Loyalty Analytics User' permission. This permission set grants access to the analytics and reporting features within Salesforce Loyalty Management, allowing the administrator to customize, view, and analyze data related to the loyalty program's performance, member engagement, and other key metrics.

To meet the company's business requirements of making points available for Loyalty Program Members after a return period of 14 days, the best solution is toEnable Deferred Points (C). Deferred points are a feature in Salesforce Loyalty Management that allows points to be earned but not immediately available for redemption, typically used to account for return periods or other conditional delays. By enabling deferred points, the company can ensure that points are only made available after the specified return period has passed, aligning with their business strategy and reducing the risk of point redemption for returned products.

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 varioussources, 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.

For creating a large multi-country, multi-currency, and tier-dependent Redemption Catalogue, the recommended approach is toCreate 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.

Loyalty Management data, including Loyalty Program, Loyalty Tier, and Member Benefits, is made available in Salesforce CDP throughConfigure Loyalty Management Bundle Data Mappings (D). This approach involves setting up specific data mappings within Salesforce CDP to ensure that data from Loyalty Management is correctly ingested, transformed, and made available within CDP for further analysis and segmentation.

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 complete the integration between Loyalty and B2C Commerce Cloud using the reference cartridge, the steps required are:

• Configure Loyalty Program preferences for B2C Commerce Site (A): This involves setting up specific preferences and configurations within B2C Commerce Cloud to align with the Loyalty Program's requirements.
• Configure connected app named B2C Loyalty Connector (C): This step involves setting up a connected app within Salesforce to facilitate secure communication and data exchange between Loyalty Management and B2C Commerce Cloud.
• Add Loyalty Management for Commerce Cartridge (E): This involves installing the specific cartridge within B2C Commerce Cloud that integrates with Salesforce Loyalty Management, enabling the Commerce site to utilize loyalty program features.

These steps ensure a seamless integration between Salesforce Loyalty Management and B2C Commerce Cloud, allowing for a unified customer experience across commerce and loyalty program interactions.

The last step the Salesforce Administrator must complete to create a private portal for the Loyalty Program using Experience Cloud is to activate the Experience Cloud site. Activation is the final step that makes the site accessible to users. Once the site is activated, members can access the portal, where they can engage with the Loyalty Program, view their points and tiers, and take advantage of program benefits. Activation is crucial as it transitions the site from a development or staging phase to a live environment.

Personalized benefits for each Loyalty Program member can be displayedOn 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 clearand organized display of benefits, making it easy for members and administrators to understand the perks associated with each member's status.

When a user cannot access a Loyalty Member Portal, the Loyalty Administrator can verify the issue by checking if the user profile has access to the new portal1. This can be done through Workspaces1. The Salesforce admin enables Loyalty Management in the org and users can create profiles and assign permissions to access the loyalty application as appropriate2. If the user profile does not have the necessary permissions, they will not be able to access the portal12. Therefore, it’s important to ensure that the user profile has the correct permissions for the new Loyalty Member Portal12.

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.

For a retailer looking to allow Loyalty program members to redeem points with redemption partners, the correct setup in Salesforce Loyalty Management involves configuring the partner record as a redemption partner. This includes:

• Setting the program partner type to "redemption" to indicate that the partner is involved in the points redemption process.
• Activating the partner record to make it available for transactions within the Loyalty Management application.
• Defining the redemption cost per unit, which specifies how many points are required for members to redeem specific rewards or benefits from the partner.

This setup ensures that Loyalty program members can redeem their points when shopping with strategic partners, aligning with the retailer's goal of enhancing the value and utility of their Loyalty program.

To set up Promotion Market Segments for members within a specific age range and with certain preferences, the recommended solution is:

• D:Salesforce Customer Data Platform (CDP), which allows for the creation of detailed segments based on a wide range of criteria, including demographic data and expressed preferences.

The new expiry date for the member after being upgraded to the Gold tier would be March 31, 2024. In Salesforce Loyalty Management, when a member is upgraded to a new tier, the expiry date is set based on the tier's fixed model and period. Since the member was upgraded on March 16, 2023, and the period is one year, the new expiry date aligns with the end of the month following the one-year anniversary of the upgrade, which is March 31, 2024.

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.

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.

To classify the different accrual transaction journals based on the various ways members can accrue points, the Salesforce Administrator should create a Journal Type for each case (e.g., Enrollment Bonus, Member Referral, Flight Purchase, Additional Profile Information). Journal Types in Salesforce Loyalty Management are used to categorize transaction journals according to the nature of the transaction, allowing for organized tracking and reporting of different types of point accrual activities. This configuration facilitates clear differentiation and management of the diverse ways in which members can earn points within the Loyalty Program

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.

When a tier is changed manually in Salesforce Loyalty Management, an Administrator should execute the following two actions:

• Process Member Benefit Action (A):This action ensures that any benefits associated with the new tier are correctly processed and applied to the member. It's essential for maintaining the integrity of the loyalty program and ensuring members receive the appropriate benefits for their new tier.
• Assign Member Tier Benefits Action (C):This action assigns the benefits specific to the newly assigned tier to the member. It's crucial for updating the member's benefits to align with their new tier status, ensuring they receive all entitlements associated with their new level.

Creating a scheduled job to perform the tier change (option B) and processing Transaction Journals batch job (option D) are not directly related to the manual tier change process. The focus should be on ensuring that member benefits are correctly assigned and processed in response to the tier change.

Salesforce documentation on Loyalty Management would provide detailed guidelines on managing tier changes, including the actions required to ensure member benefits are correctly updated.

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). Thiscomponent allows for the display of relevant Loyalty Program Member information directly within the context of a Case record, enhancing the service agent's ability to access pertinent loyalty information while managing customer cases.

The benefits of using Batch Management in Salesforce Loyalty Management, especially in the context of processing nightly batches of transactions from a Point of Sales (POS) system, include:

• Tracks the status and health of batch jobs (A):This allows program administrators to monitor the progress and success of batch processes, ensuring that transactions are being processed efficiently and any issues are quickly identified and addressed.
• Process large volumes of transactions (B):Batch Management is designed to handle high volumes of data, making it well-suited for processing the large number of transactions typically generated by a POS system daily.

Options C and D, while related to the benefits of batch processing, are more specific to the technical aspects of handling external data and file formats, which are not directly mentioned in the question. Batch Management's core benefits in this scenario are its ability to efficiently process and monitor large transaction volumes, ensuring the timely and accurate update of loyalty points and member statuses.

Salesforce documentation on Batch Management within Loyalty Management would offer insights into setting up and optimizing batch jobs for transaction processing, ensuring that loyalty programs can effectively manage member data and transactions even with high volumes and complex processing requirements.

To ensure Loyalty members can access their program-specific records on the Loyalty Member Portal, an Administrator should:

• Using Experience Cloud sharing sets, specify Account as the object of your sharing set (A):Sharing sets in Experience Cloud allow you to define access rules for external users based on their relationship to records in Salesforce. Specifying Account as the object in a sharing set can enable portal users to access theirLoyalty Program information if their portal user account is linked to their Account record in Salesforce.
• For the Loyalty Member, 'Enable Customer User' on the Contact or 'Enable Partner User' on the Account (D):Enabling a Customer or Partner User on the Contact or Account associated with the Loyalty Member allows that individual to access the portal. This step is crucial for granting Loyalty Program members the ability to log in and view their Loyalty Program-specific information.

Options B and C, while related to portal access and user setup, do not directly address the specific requirement of accessing Loyalty Program information. Option E is also relevant but more focused on enabling self-registration and user creation/login processes rather than directly impacting access to Loyalty record information.

Salesforce documentation on Experience Cloud and Loyalty Management would provide guidance on setting up and configuring access for Loyalty Program members to view their information on a member portal, ensuring a seamless user experience.

To segment and identify specific tier members for a journey within Marketing Cloud, it's essential to synchronize the right objects from Salesforce to Marketing Cloud. Synchronizing the 'Contact' object ensures that the basic member information is available. The 'Loyalty Program Member' object provides detailed information about the member's involvement in the loyalty program, and the 'Loyalty Member Tier' object offers insights into the member's current tier status. This setup allows for precise targeting and personalization of marketing efforts aimed at encouraging Loyalty Tier B customers to ascend to Loyalty Tier A, thereby enhancing member engagement and program value.

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.