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

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

Explanation

The issue involves loyalty components being added to a Lightning page but not displaying, despite correct permissions. This typically occurs when the page lacks the necessary context to determine which loyalty program's data to display. The primary program setting provides this system-wide context, and without it, loyalty components cannot render properly even when technically placed on the page.

✅ Correct Option

C. Setup the Loyalty Program as Primary
The "Primary" designation for a loyalty program establishes it as the default program across the Salesforce org. Loyalty components like profile cards rely on this system-level setting to understand which program's member data to retrieve and display. Without a primary program selected, these components have no contextual anchor and will remain hidden, regardless of page layout configuration.

❌ Incorrect Options

A. Setup the Member Summary Embedded Dashboard
This dashboard displays member transaction history and points summary, but it's a separate component. Configuring this dashboard does not resolve the fundamental missing context needed for the core loyalty profile cards to appear.

B. Setup the Member Preferences Embedded Dashboard
This component shows member opt-in preferences for marketing communications. While useful, it addresses a different functionality and does not activate the primary visibility setting required for the main loyalty components.

D. Setup the Member NPS Dashboard
This dashboard is for Net Promoter Score metrics and member feedback analysis. It is unrelated to the core member profile information and does not control the visibility of fundamental loyalty components.

Summary
The root cause is the absence of a designated primary loyalty program, which provides essential context for all loyalty components to render correctly on Lightning pages.

📚 Reference
Salesforce Help - "Set Up Your Loyalty Program" and "Add Loyalty Components to Lightning Pages"

Explanation

Analyzing Loyalty Program performance requires access to CRM Analytics (formerly Tableau CRM) templates tailored for loyalty metrics, like dashboards tracking engagement, redemptions, and tier progression. System Administrators handle setup of these analytics apps, including customizing datasets, lenses, and queries for deeper insights. This involves assigning specialized permission set licenses that enable creation and editing of loyalty-specific analytics assets, ensuring admins can tailor views without relying solely on out-of-the-box reports.

Correct Option:

✅ A. Loyalty Analytics User
This permission set license unlocks the CRM Analytics for Loyalty Management app, granting users access to create, edit, and publish customized dashboards, datasets, and stories focused on program KPIs such as member acquisition, transaction volumes, and liability trends. For admins, it provides the necessary object permissions and app builder tools to configure loyalty data models, integrate with external sources, and deploy tailored analytics—essential for performance optimization beyond standard views.

Incorrect Options:

❌ B. CRM Analytics User
This general permission set license offers broad access to CRM Analytics for building any custom analytics across Salesforce data, but it lacks loyalty-specific datasets, templates, and pre-built metrics. Admins with this can set up generic apps, yet they'd need to manually recreate loyalty structures, missing out on optimized components for program analysis like redemption rates—making it inefficient for targeted Loyalty Management customization.

❌ C. CLAAnalytics Base Admin
Focused on Customer Data Platform (CDP) analytics for audience segmentation and unified profiles, this admin license enables setup of data streams and calculated insights in CLA (Customer 360 Audiences). However, it doesn't extend to Loyalty Management's performance dashboards or object-specific analytics, so admins couldn't customize loyalty-focused reports or integrate program data effectively for engagement tracking.

❌ D. Data Pipeline User
This license supports Data Cloud pipelines for ingesting and transforming raw data from various sources, crucial for feeding analytics but not for setting up customized visualizations or dashboards. It handles backend ETL processes, like loading transaction journals into CRM Analytics, but lacks front-end tools for loyalty-specific app configuration—admins would prepare data but still need analytics permissions to build and analyze program performance.

Reference:
Analytics for Loyalty
Get Started with Loyalty Analytics

Explanation

When launching a new Loyalty Program while maintaining an existing portal design, the approach must balance reusability with proper program separation. The Experience Cloud template components can be reused across multiple sites, but each loyalty program requires its own dedicated portal assignment to ensure data integrity and proper member segmentation between programs.

✅ Correct Options

B. Use existing Experience Cloud components to handle the same design and functionalities.
The existing Experience Cloud components contain the pre-built design and functionality that already work with Loyalty Management data model.
These components are reusable across different community sites, allowing consistent user experience without rebuilding the same interfaces from scratch.
This approach saves implementation time and ensures functional consistency with the existing portal while applying it to the new program context.

D. Create a new Loyalty Member Portal and assign it to the new Loyalty Program.
Each loyalty program requires its own dedicated Experience Cloud site to maintain proper data isolation and member management.
Assigning multiple loyalty programs to a single portal would cause data conflicts and improper member experience between programs.
Creating a separate portal ensures clean segmentation where members only see and interact with their specific program's data and benefits.

❌ Incorrect Options

A. Assign the existing Loyalty Member Portal to the new Loyalty Program too.
A single Loyalty Member Portal cannot be assigned to multiple loyalty programs simultaneously in Salesforce.
This would create data visibility issues where members from different programs might see incorrect points, tiers, or benefits.
The platform architecture requires one-to-one relationship between loyalty programs and their associated member portals.

C. Create new Experience Cloud Components for the new Loyalty Member Portal.
Creating entirely new components is unnecessary when existing components already provide the required functionality and design.
This would duplicate development effort and create maintenance overhead for nearly identical component sets.
It could also introduce inconsistencies between the two portals' user experience and behavior.

Summary
Reuse existing components for consistency but create a new dedicated portal for proper program isolation and data management.

📚 Reference
Salesforce Help - "Set Up Loyalty Management for Experience Cloud"