Salesforce Salesforce-Loyalty-Management Salesforce Loyalty ManagementAccredited Professional Exam (SU24) Exam Practice Test

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.

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.

Setting up a loyalty promotion with Salesforce CDP (Customer Data Platform) and Marketing Cloud involves several critical steps to ensure seamless integration and functionality. The first step, 'Send Loyalty Promotion Segments to Marketing Cloud,' involves identifying and segmenting your loyalty members in Salesforce CDP and then transferring these segments to Marketing Cloud for targeted marketing efforts. 'Activating and Publishing the Segment' is crucial as it makes the segment available for use within Marketing Cloud, allowing for personalized engagement with the segmented audience. Lastly, 'Enable Service Connector for Promotion Escalations' is essential for ensuring that any promotional activities or escalations are properly managed and communicated between Salesforce CDP, Loyalty Management, and Marketing Cloud, providing a cohesive experience across platforms.

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.

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.

To meet the business need of sending an SMS to a member's mobile device after a purchase and an increase in non-qualifying points, the required Salesforce solutions are Marketing Cloud Connect (A) and Marketing Cloud MobileConnect (B). Marketing Cloud Connect facilitates the integration between Salesforce Loyalty Management and Marketing Cloud, while MobileConnect is a specific tool within Marketing Cloud designed for sending SMS messages to mobile devices, allowing for timely and targeted communication with loyalty program members.

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

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.

To meet the specifications of resetting the qualifying period once a year on the 31st of March and not extending the member tier upon expiration, the Consultant should configure the Loyalty tier groups with a Tier-model = fixed and Extend Expiration = no extension. The fixed tier model ensures that the qualifying period and tier criteria remain constant over time, while the 'no extension' setting ensures that member tiers do not automatically extend beyond their expiration date. This configuration aligns with the requirement for a clear, annual reset and non-extension of tier status, ensuring a consistent and predictable tier progression structure within the Loyalty Program.

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.

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.

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.

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.

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.

To set up a 10% discount on top of the annual summer sale for loyalty program customers in Salesforce Loyalty Management, the consultant must:

Create within the Loyalty Experiences tab a new promotion for the Summer Sales campaign where the Loyalty Promotion Type is Standard and the Fulfillment Action is Issue Voucher (B): This step involves setting up a new promotion specifically for the summer sale, defining it as a standard promotion type, and specifying that the fulfillment action for eligible members will be to issue a voucher, which in this case would be the 10% discount voucher.

Create within the Loyalty Experience tab a new voucher definition where the Type Is Discount Percentage and the Expiration Type is fixed Date (D): This step involves defining a new voucher that applies a discount percentage (10% in this case) to purchases, with a fixed expiration date to limit the offer to the summer sale period. This ensures that the promotion is time-bound and encourages members to take advantage of the offer during the sale.

Options A and C involve creating a voucher definition and a benefit type, respectively, but do not align precisely with the steps required to set up a promotion that includes issuing a discount percentage voucher with a fixed expiration date for a specific campaign like the summer sale.

Salesforce Loyalty Management documentation would provide detailed guidance on creating promotions and vouchers, ensuring that loyalty program consultants can effectively design and implement targeted offers to enhance member engagement and sales during key promotional periods.

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.

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.

The most efficient way to automatically reset qualifying points for high-volume Loyalty Programs is to use the out-of-the-box ‘Reset Qualifying Points’ data processing engine and trigger its execution using, for instance, a Schedule-Triggered Flow. This method leverages Salesforce's built-in capabilities to manage the reset process without the need for custom code. The data processing engine is designed to handle large volumes of data efficiently, ensuring that the points reset process is completed accurately and timely across all relevant member accounts.

To develop an InApp-Dashboard showing top and bottom agent performers in the Loyalty call center, the most suitable dashboard available through the Analytics Studio tool is the:

Loyalty Member Services Dashboard (D): This dashboard is designed to track the performance of agents interacting with loyalty program members, including metrics like the number of members assisted, customer satisfaction scores, and modifications made by agents. It provides insights into agent performance and service quality in the context of loyalty member services.

The Program Manager Home Dashboard (option A), Member Services Manager Home Dashboard (option B), and Team Performance Dashboard (option C) may contain relevant metrics but are not specifically tailored to tracking individual agent performance in the context of loyalty member services.

Salesforce documentation on Analytics for Loyalty would provide information on available dashboards and their intended use cases, including how to customize and leverage them for specific analytical needs, such as tracking call center agent performance.

For designing a new tier-upgrade process in a Loyalty Program, the Consultant should select:

A flow to perform the tier-upgrade rule and another flow to perform the tier-upgrade orchestration process (C): This approach allows for the separation of concerns, where one flow is responsible for evaluating whether members meet the criteria for a tier upgrade, and another flow is responsible for the actual process of upgrading the member's tier. This modular design improves maintainability and scalability.

A data-processing-engine (DPE) to identify the qualified members (D): The DPE can efficiently process large sets of member data to identify those who qualify for a tier upgrade based on the program's criteria. This component is crucial for automating the tier-upgrade process at scale, especially in programs with a significant number of members.

Option A combines both processes into a single flow, which could become complex and harder to maintain. Option B suggests using a single flow for scheduling and processing, which might not offer the required flexibility and efficiency for handling complex tier-upgrade criteria and orchestration.

Salesforce documentation on Loyalty Management provides guidelines on leveraging Flow and DPE for automating and orchestrating various loyalty program processes, including tier upgrades.

In Salesforce, objects that count toward data storage capacity include Person Account, Orders, Loyalty Program Members, Transaction Journals (A). These objects are essential components of a Loyalty Program and each record created within these objects occupies space in Salesforce's data storage. Person Accounts and Orders are standard Salesforce objects, while Loyalty Program Members and Transaction Journals are custom objects introduced by the Loyalty Management application, all contributing to the overall data storage usage.

To provide Cloud Kicks' customer base, who are heavy mobile users, with access to member program information, the consultant should Enable Experience Cloud and customize the Loyalty Member Portal (A). Experience Cloud (formerly known as Community Cloud) allows for the creation of branded, mobile-responsive portals that can be customized to meet specific business needs, including providing loyalty program members with access to their program information, account status, rewards, and more. This approach leverages existing Salesforce capabilities and does not require the development of a new mobile app, making it a cost-effective and efficient solution.

In Salesforce Loyalty Management, visibility issues of components such as the Loyalty Members Profile Cards on the Lightning Record Page can often be traced back to configuration settings related to the Loyalty Program itself. While options A, B, and D mention various dashboards (Member Summary, Member Preferences, and Member NPS), these are not directly related to the visibility of profile cards on the Lightning Record Page.

The correct setting that is likely missing and preventing the visibility of the Loyalty Members Profile Cards is the configuration of the Loyalty Program as Primary. This setting is crucial because it defines which Loyalty Program is considered the main one for the organization. Without setting a Loyalty Program as Primary, Salesforce might not properly display related components, such as the Loyalty Members Profile Cards, due to a lack of context about which program's information should be displayed.

In Salesforce, the concept of a "Primary" program is used in various contexts to denote the main or default record among multiple. Similarly, in the context of Loyalty Management, setting a Loyalty Program as Primary ensures that its related data and components are given precedence and are properly displayed in the user interface, including on Lightning Record Pages.

For reference, Salesforce documentation on Loyalty Management typically covers the setup and configuration of Loyalty Programs, including how to designate a program as Primary. Although the exact steps can vary based on the Salesforce release and customizations, administrators typically need to navigate to the Loyalty Management settings or related setup area, find the specific Loyalty Program configuration section, and select an option or checkbox to designate a program as the Primary Loyalty Program for the organization.

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.

To associate the new products with their respective partners within the loyalty partner product section, the Administrator should take two steps. For the Chocolate cookies linked with the snack category, the Administrator should add the partner in the Lookup on the Chocolate cookie product. This directly associates the product with the specific partner responsible for the snack category.

Similarly, for the Green soda from the beverage importer, the Administrator should choose the ‘Product’ option and map the Green soda to the partner. This step ensures that the beverage product is correctly associated with the beverage importer, maintaining accurate and organized tracking of partner products within the Loyalty Program. These configurations facilitate seamless management and representation of partner products within the program, enhancing the clarity and efficiency of partner product associations.

To target a specific audience with a Promotion in Salesforce Loyalty Management, an administrator could:

Option C "Create a segment in the Salesforce Customer Data Platform and associate the segment to the promotion." This allows for precise targeting based on detailed segmentation criteria.

Option D "Link a promotion to a campaign and associate a segment to the campaign." This method utilizes Salesforce's campaign management features to target promotions to specific segments.

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.