The Loyalty Member Profile Cards component on a Contact or Account Lightning Record Page is designed to display a member's key information, such as their tier, points balance, and currency. For this component to render, Salesforce must know which loyalty program's data to display, especially if a member belongs to multiple programs. By designating one loyalty program as "Primary," you establish this necessary context. If no program is set as primary, the component has no data source to pull from and will not be visible on the page, even if permissions are correctly configured.

A. Setup the Member Summary Embedded Dashboard: This is an analytics dashboard component. Its setup is independent and not a prerequisite for the visibility of the core member profile cards.

B. Setup the Member Preferences Embedded Dashboard: This is another distinct analytics dashboard. Its configuration does not control the display of the fundamental member profile information cards.

D. Setup the Member NPS Dashboard: This dashboard is used for tracking Net Promoter Score analytics. It is a separate component and its setup does not affect the visibility of the profile cards.

---

1. Salesforce Help Documentation, "Set Up Your Loyalty Program":

Section/Topic: Set Up Your Loyalty Program

Content Reference: The documentation explicitly states, "To show a member's loyalty information on the member's Contact or Account record, you must set up a primary loyalty program. When you set a program as primary, the loyalty information of members of the primary program is shown on the members' Contact or Account records." This directly links the visibility of member information on record pages to the "Primary" program setting.

2. Salesforce Help Documentation, "Add Loyalty Components to Record Pages":

Section/Topic: Add Loyalty Components to Record Pages

Content Reference: This guide details the available components, including "Loyalty Member Profile," "Loyalty Member Tiers," and "Loyalty Member Currency." The functionality of these components implicitly relies on a defined program context, which is established by the primary program setting for the record page to correctly display the relevant data. Without a primary program, these components have no context to render.