Salesforce-Loyalty-Management Questions and Answers

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 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 ensure staff buy-in and boost adoption and engagement with the new Loyalty Program, Universal Containers should:

D: Define a company-wide initiative that includes the operations team. Engaging all relevant departments from the outset ensures a holistic approach to the implementation and addresses concerns and skepticism by involving those who will be directly impacted by the new Loyalty solutions.

Customer support agents can manually adjust points for Loyalty Program Members on the following pages:

Loyalty Program Member page (A): This is the primary interface for viewing and managing individual loyalty program members, including adjusting their points as needed.

Loyalty Program Member Related List (B): This related list, found on related records such as accounts or contacts, provides access to loyalty program member information, including point adjustments.

Transaction Journal (C): The Transaction Journal records all point transactions for loyalty program members, allowing customer support agents to make manual adjustments to points as necessary.

Options D (Account page) and E (Contact page) may provide indirect access to loyalty program member information but are not the primary interfaces for adjusting loyalty program points.

Salesforce documentation on Loyalty Management would detail the interfaces and processes for managing loyalty program members' points, including the roles and permissions required for customer support agents to make adjustments.

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.

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.

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 analyze earning activities in the Loyalty Program, Cloud Kicks' Management team needs:

Option D: "Read, View All" access on the "Journal Type," "Journal Subtype," and "Transaction Journal" Objects. This level of access allows the management team to view comprehensive information about all types of transactions and activities within the Loyalty Program, including earning activities, enabling detailed analysis and reporting.

To establish a Loyalty promotion with Salesforce CDP (Customer Data Platform) and Marketing Cloud, the three essential steps are:

Transmit Loyalty Promotion Segments to Marketing Cloud (A): This step involves sharing segmented data from Salesforce CDP to Marketing Cloud, enabling targeted marketing campaigns based on loyalty promotion criteria.

Activate and Publish the Segment (C): Once the segments are defined and populated with the relevant Loyalty Program Members, the segment needs to be activated and published to be used in campaigns and promotions within Marketing Cloud.

Enable Connector Settings on all the Loyalty Objects (D): This involves configuring the integration between Salesforce CDP, Loyalty Management, and Marketing Cloud by enabling the necessary connector settings, ensuring seamless data flow and communication between these platforms for the promotion.

Option B (Automatically Generate a New Individual Relationship) and E (Enable Service Connector for Promotion Escalations) are not directly related to the essential steps for establishing a loyalty promotion with Salesforce CDP and Marketing Cloud.

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.

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 enable agents to view Loyalty Program Member information on a Case record in Service Cloud, the IT Administrator should On the Case Page Layout, add the 'View Member Profile' component and select the required Related Lists from Loyalty Program Member (B). This component allows for the display of relevant Loyalty Program Member information directly within the context of a Case record, enhancing the service agent's ability to access pertinent loyalty information while managing customer cases.

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.

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.

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

For a member who joins the NTO Insider program in the Silver tier and gets upgraded to the Gold tier on March 16, 2023, the new expiry date after the tier upgrade would be December 31, 2024 (C). This is because the tier group is defined with a Fixed Model and a Period of one year, with the Qualifying Points reset date set at December 31, 2022, and a frequency of one year. The Extend Expiration setting being tied to the Qualifying Points Reset Date means that regardless of when the tier upgrade occurs within the year, the expiration of the new tier status aligns with the annual reset date, extending to the end of the following reset period, which would be December 31, 2024.

This approach ensures that members who achieve a higher tier partway through the year enjoy the benefits of that tier for the remainder of the current year plus the entire next year, providing a full year's benefit from the point of the annual reset.

Salesforce documentation on Loyalty Management would outline the functionality and configuration options for tier groups, tier upgrades, and expiration settings, guiding administrators on setting these up to meet the program's strategic objectives and ensure clarity and fairness for members.

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.

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

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.

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 spending 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 use 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 if 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 rules 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 turn on analytics and dashboards for Loyalty, the three essential steps are:

Assign Analytics for Loyalty User Permissions (A): This step ensures that users who need to access Loyalty Analytics have the necessary permissions to view and interact with the analytics and dashboards.

Schedule dataflow for the analytics (C): Dataflow is the process by which data moves from Salesforce objects into Analytics datasets. Scheduling dataflow is crucial for ensuring that the analytics and dashboards have up-to-date information from the Loyalty Management system.

Install CRM Analytics package (E): This involves adding the CRM Analytics package to your Salesforce org, which provides the tools and capabilities needed to create and customize analytics and dashboards for Loyalty Management.

Option B (Create standard Salesforce reports and dashboard) and Option D (Create an App using existing templates) are valuable for general reporting and app development within Salesforce but are not specifically tied to the initial steps for enabling Loyalty Analytics and dashboards.

Salesforce documentation on Loyalty Management and CRM Analytics would detail the process of enabling analytics for Loyalty, including the setup of user permissions, dataflow scheduling, and the installation of necessary packages to utilize analytics and dashboards effectively.

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.

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