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

When configuring a new user account in Marketing Cloud for integration with Salesforce Loyalty Management, the Consultant must ensure to Grant access to the correct business unit (B) and Enable 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.

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.

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.

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.

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.

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 integrating Loyalty Management and Service Cloud, a Technical Consultant should use the following methods to associate a Loyalty Program Member with a Case:

Add the Loyalty Program Members' related list on the Case page layout (A): This allows agents to view and access loyalty program member information directly from a Case record.

Add the 'Cases' related list on the Loyalty Program Member page layout (D): This enables the viewing and management of cases related to a specific loyalty program member from their loyalty member record.

These configurations enhance the integration between Loyalty Management and Service Cloud, providing a seamless experience for service agents handling loyalty program members' inquiries and cases.

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.

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.

When implementing a new Loyalty Program while retaining the design and functionalities of an existing Loyalty Member Portal built with the Loyalty Experience Cloud template, Universal Containers should consider:

Option B: Utilizing existing Experience Cloud components to ensure consistency in design and functionality. This approach leverages the reusable nature of Experience Cloud components, allowing for efficient replication of the portal's look and feel without the need for extensive redevelopment.

Option D: Creating a new Loyalty Member Portal specifically for the new Loyalty Program. This ensures that the new program has a dedicated portal tailored to its unique requirements while maintaining the desired design and functionalities. This approach allows for customization and scalability, accommodating any program-specific features or requirements.

Incorporating a targeted strategy in a Loyalty Program can lead to the following benefits:

Personalized digital marketing (A): A targeted strategy allows for more personalized communication and offers, tailored to the specific behaviors, preferences, and tiers of loyalty program members, enhancing member engagement and program effectiveness.

Data-based segmentation strategy (D): By leveraging data to segment the loyalty program members, the program can deliver more relevant and appealing offers and communications, increasing member satisfaction and program participation.

Automatically archiving transaction journey data (option B) is more of a data management practice and not directly a benefit of running a targeted strategy. Rewarding customers based on their tiers (option C) is a common practice in loyalty programs but does not specifically result from implementing a targeted strategy.

Salesforce documentation on Loyalty Management would detail the advantages of implementing targeted strategies within loyalty programs, including how to leverage Salesforce tools for personalized marketing and data-driven segmentation.

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.

To grant users proper access to a newly created analytics app, two steps are required. First, assigning user access to the analytics for Loyalty role ensures that users have the necessary permissions to view and interact with Loyalty-specific analytics content. This role typically encompasses permissions tailored to accessing and analyzing data within the context of the Loyalty Management application.

Second, assigning user access to permission sets for analytics for Loyalty is another way to grant targeted access. Permission sets allow for fine-grained control over user permissions, enabling the Administrator to specify exactly what analytics content a user can access and interact with. By using permission sets, access can be customized to fit the specific needs and roles of different users within the organization.

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.

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 communicate a new Promotion to eligible Loyalty Program members, Northern Trail Outfitters can utilize integrated Salesforce applications such as:

Option C: Salesforce Customer Data Platform (CDP), which allows for the aggregation and management of customer data, enabling targeted communication based on member attributes and behaviors.

Option D: Salesforce Marketing Cloud, which offers robust email marketing and customer engagement tools. By integrating Loyalty Management data with Marketing Cloud, NTO can create personalized and targeted email campaigns to inform members about new promotions.

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

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.

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 activities and 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 within a loyalty program, ensuring a rich and engaging member experience.

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.

The Loyalty Analytics Base App license allows technical Consultants to access Loyalty analytics data with the limitation that administrators can analyze up to 10 million rows (D). This limitation is set to ensure system performance and scalability while providing sufficient data analysis capabilities for most loyalty program needs. Salesforce documentation on Loyalty Management and its integration with analytics tools would detail these limitations and provide best practices for managing and analyzing loyalty data within these constraints.

To provide the Member Services team with the information they need directly on the Contact record, the IT Administrator can take two main actions. Firstly, embedding the 'Member Summary Embedded Dashboard' on the Contact record allows the team to have a visual and comprehensive overview of a member's loyalty activities, including recent transactions and adjustments, directly within the context of the contact. This dashboard is specifically designed to aggregate and display relevant loyalty information, making it a suitable tool for quick insights.

Secondly, adding the 'Transaction Journals' related list to the Contact record enables the team to view detailed entries of each transaction and manual adjustment made by or for the member. This related list provides granular data about each activity, allowing for a deeper analysis and understanding of the member's loyalty interactions.

These recommendations are based on best practices for Salesforce Loyalty Management, ensuring that the team has access to both summarized and detailed loyalty information within their usual workflows, enhancing efficiency and providing a holistic view of member activities.

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.

To award new members with a 10% discount and 100 points upon sign-up, the Program Administrator should:

B: Create a record-triggered flow using Journal Type, Journal SubType, Transaction Journal, Credit Points action, and Issue Voucher action. This flow will automate the process of crediting points and issuing discount vouchers to new members as part of the promotion.

To view information pertaining to a member's recent transactions and manual adjustments on the Contact record, an IT Administrator should propose:

Incorporate the ‘Member Summary Embedded Dashboard’ on the Contact record (A): This dashboard can provide a comprehensive overview of a member's loyalty activities, including recent transactions and adjustments, directly within the context of their Contact record.

Incorporate the ‘Transaction Journals’ related list on the Contact record (C): By adding this related list, the Member Services team can easily access detailed transaction and adjustment records associated with the loyalty program member directly from the Contact record, facilitating quick and informed customer service interactions.

Options B and D, involving the Member Service Manager Home Dashboard and the ‘View Member Profile’ component, do not directly address the need to view transactional information on the Contact record.