Salesforce-Loyalty-Management Salesforce Loyalty Management Accredited Professional (AP-212) Questions and Answers

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.

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

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 proc ess 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 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 sp ending 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 u se 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 i f 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 rul es 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 efficiently display information about the Loyalty Program Member on the case detail page, embedding Loyalty Member Profile Cards is a standard solution. These profile cards are designed to provide a concise and comprehensive view of the member's loyalty information, including membership details, points balance, tier status, and recent transactions, directly within the context of a case. This allows customer support agents to quickly access relevant loyalty information without navigating away from the case record, improving efficiency and enabling better support. Salesforce documentation suggests using embedded component s like profile cards to enhance user experience and access to information within record pages.

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 t he 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 a nd 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 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.

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 reachi ng 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 set up a new tier-point reset process for a Loyalty Program with the least configuration effort, the consultant should:

Option A "Create a copy of the reset qualifying points DPE template." This approach leverages existing DPE templates designed for similar purposes, minimizing the need for extensive custom configuration.

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.

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 ma nagement of targeted marketing campaigns to engage Loyalty Program members, promote rewards, and encourage participation.

To create personalized experiences across Cloud Kicks' customer journey, the Loyalty Consultant should utilize Salesforce Marketing Cloud (B) . Marketing Cloud provides a comprehensive suit e 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 p ersonalized and engaging experiences for loyalty program members, enhancing customer satisfaction and loyalty.

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

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 meet the business n eed 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 me mbers.

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.

To offer Platinum members exclusive access to VIP events, an Administrator should Set up Members "Exclusive Access to VIP Events" as a Loyalty Tier Benefit (D) . Configuring this exclusive access as a tier benefit specifically for Platinum memb ers allows for clear differentiation of tiers and provides a compelling incentive for members to reach and maintain the Platinum tier. This setup ensures that the highest-tier members receive appropriate recognition and rewards, enhancing their loyalty and engagement with the program.

Options A (Voucher), B (Member Promotion), and C (Transaction Journal) do not accurately represent the method for providing exclusive event access as a distinct benefit of attaining the Platinum tier within a 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.

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.

To fulfill the new voucher's requirements, the voucher definition settings should be: Type: Fixed Value, Expiration Type: Period, Expiration Period: 3, Expiration Period Unit: Month, Face Value: $300, Pa rtial Redeemable: Checked. This configuration ensures that two vouchers with the specified face values can be issued within the defined period and used within three months after the first voucher’s disbursement date. The 'Partial Redeemable' option allows the vouchers to be used partially, providing flexibility in how they are redeemed by the members.

The Da ta 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 aggregatio n, 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.

QUESTION NO: 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 must be 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 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 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 their Loyalty Program informatio n 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 associa ted 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.

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 troubl eshooting automations, including the necessary permission sets for different actions.

In the context of Salesforce Loyalty Management, when setting up transactions and points accrual for a customer purchasing a ticket in an airline loyalty program, the appropriate automations are Evaluatio n Flow and Schedule-Triggered Flow .

Evaluation Flow: This automation can be set up to evaluate transactions as they occur, applying loyalty program rules to determine if the transaction qualifies for point accrual and, if so, how many points should be awar ded. This is crucial for real-time processing and immediate feedback to loyalty program members.

Schedule-Triggered Flow: This type of automation is used to evaluate transactions on a scheduled basis, which can be daily, weekly, or any other predefined sch edule. It is useful for batch processing transactions, such as nightly batch jobs that process all transactions from the day and apply loyalty points accordingly.

The use of Autolaunched Flow (No Trigger) and Screen Flow would not be as appropriate in this scenario. Autolaunched Flows without a trigger require manual initiation or a programmatic event, which might not be efficient for real-time transaction processing. Screen Flows are interactive and require user input, which is not suitable for automated transaction and points accrual processing.

References to official Salesforce documentation on flows and automation in Salesforce Loyalty Management would provide further insights into how these automations can be set up and utilized effectively.