To monitor members' tier history in the dashboards from the Analytics Studio App, the two fields that need to be enabled in field history tracking on the Loyalty Member Tier object are:

Change Reason Type (B): This field captures the type of change (e.g., manual adjustment, system-generated change) that led to the tier change, providing context for the tier history.

Reason for Change (D): This field provides specif ic reasons for the tier change, offering detailed insights into why a member's tier was adjusted, which is valuable information for analyzing member behavior and program effectiveness.

Option A (Loyalty Tier Group) and Option C (Loyalty Tier) are important fields for understanding tier structures and member status, but they do not specifically relate to tracking changes or the reasons behind tier history, which are crucial for analytical purposes.

Salesforce documentation on Loyalty Management and Analytics would provide guidance on configuring field history tracking and leveraging Analytics Studio to create insightful dashboards that monitor and analyze members' tier history, aiding in strategic decision-making and program optimization.

To provide live updates to Loyalty members about their program membership, the following tasks should be implemented:

Associate the site with the new Hotel Group Loyalty Program : This task involves linking the hotel’s loyalty program with their website, allowing for seamless access to loyalty program details for members 1 .

Create a site using the Experience Cloud site template called the Loyalty Member Portal : Salesforce provides a specialized site template within Expe rience Cloud specifically designed for loyalty programs.  This template, known as the Loyalty Member Portal, is tailored to display loyalty program de tails, points balance, recent transactions, and tier information 2 .

Add Loyalty lightning components to the site : By addi ng Lightning components to the site, members can view their loyalty program details, points balance, recent transactions, and current tier assignments in real-time.  These components are designed to provide a comprehensive overview of a member’s status within the loyalty program without the need for complex customizations 2 .

These steps will ensure that members can view their membership details at their convenience, fostering greater engagement and satisfaction with the hotel group’s Loyalty program.

The Loyalty Analytics Base App license allows technical Consul tants 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.

For a member who join s 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 y ear, 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 expira tion 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.

For this segmentation requirement, the key is to identify members whose membership will expire at the end of the current month and to ensure the segment is refreshed daily within the specified date range.

Option B is correct because using "This Month" for the "Membership Expiry Date" attribute will accurately segment members whose memberships expire at the end of the current month.

Option D is also correct because setting the "Publish Schedule" to "24 hours" ensures the segment is refreshed daily, capturing new members meeting the criteria as the month progresses. The "Start Date" and "End Date" should be set from the 1st of April to 30th of June to match the requirement.

Option A is no t suitable because "Don't Refresh" would prevent the segment from updating daily, which is necessary to capture new members as their membership expiry dates become relevant.

Option C using "Next Number of days" = 30 might incorrectly include members whose memberships expire in the next 30 days from the current date, not specifically at the end of the current month.

To create urgency for Loyalty program members to return and redeem their points within a specified period, where the entire points balance expires if a member's last activity reaches 18 months, the Loyalty Consultant should:

Set up a Non-Qualifying Points currency, apply the expiration model 'Activity Model' (C): This setup allows for the expiration of Non-Qualifying Points based on member activity, specifically if there is no purchase or points redemption activity within an 18-month period. The Activity Model is used to track the last activity date and trigger expiration based on this inactivity period.

Setting up a Non-Qualifying Points currency with a 'Fixed Model' expiration (option A), a Qualifying Points currency with either 'Activity Model' (option B) or 'Fixed Model' expiration (option D), would not meet the retailer's requirement for creating urgency based on the last activity.

Salesforce documentation on Loyalty Management would provide guidance on configuring expiration models for loyalty currencies, ensuring that program objectives, such as encouraging regular member engagement, are achieved.

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.

To complete the integration between Loyalty and B2C Commerce Cloud using the reference cartridge, the steps required are:

Configure Loyalty Program preferences for B2C Commerce Site (A) : This involves setting up specific preferences and configurations within B2C Commerce Cloud to align with the Loyalty Program's requirements.

Configure connected app named B2C Loyalty Connector (C) : This step involves setting up a connected app within Salesforce to facilitate secure communication and data exchange betwee n Loyalty Management and B2C Commerce Cloud.

Add Loyalty Management for Commerce Cartridge (E) : This involves installing the specific cartridge within B2C Commerce Cloud that integrates with Salesforce Loyalty Management, enabling the Commerce site to util ize loyalty program features.

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

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 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 Pro file' 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.