Salesforce Loyalty Management allows administrators to configure three distinct types of vouchers to reward program members. These types define the nature of the benefit provided. The available types are:

1. Discount Percentage: Offers a percentage-based discount on a transaction (e.g., 20% off an order).

2. Fixed Value: Provides a specific monetary amount off a transaction (e.g., $10 off). This is also referred to as a Fixed Amount discount.

3. Product or Service: Grants the member a specific product or service at no cost (e.g., a free coffee or complimentary shipping).

A. Promo Code: A promo code is a mechanism used to distribute and redeem a voucher, not a fundamental type of voucher benefit itself.

D. Gift Card: While a fixed-value voucher can function similarly to a gift card, "Gift Card" is not a distinct, configurable voucher type within the Loyalty Management setup.

1. Salesforce Help, Vouchers in Loyalty Management: This document outlines the voucher framework and its capabilities. It states, "Vouchers can provide members with a percentage or fixed amount discount on products. Vouchers can also provide members with a product or service, for example, a free dessert or a free car wash." This directly supports options B, C, and E.

2. Salesforce Help, Create a Voucher Definition: In the setup steps for creating a voucher, the "Discount Type" field is a required picklist. The available values in this picklist are "Percentage," "Fixed Amount," and "Product or Service," which correspond directly to the correct answers.

Member Engagement Attributes are designed to track and aggregate a member's activities and behaviors over a specified period. They are used to determine a member's eligibility for a promotion based on cumulative actions rather than a single event.

Scenario A requires tracking the total transaction amount each month for a year. Scenario B requires counting the number of training attendances within a specific two-month period. Both scenarios involve tracking member behavior over time, which is the primary function of Member Engagement Attributes.

C. Member buys apparel online and gets 400 bonus points if the member belongs to Gold Tier only.

This is a standard transactional promotion. Eligibility is based on a single transaction and a static member attribute (tier), not on cumulative behavior tracked over time.

D. Member enrolls in “welcome aboard” promotion for free surprise gift every quarter.

This scenario's eligibility is based on the act of enrolling in a promotion, not on tracking specific member activities or behaviors that would require an engagement attribute.

1. Salesforce Help, Loyalty Management, "Track Member Behavior with Member Engagement Attributes":

This document states, "Member engagement attributes help you track your members’ activities and behavior for a specified period. You can use these attributes to determine a member’s eligibility for a promotion." It provides examples like tracking the total transaction amount in the last 30 days or the number of times a member has used a voucher, which directly aligns with scenarios A and B.

2. Salesforce Help, Loyalty Management, "Promotions":

The overview of promotions explains how rules can be configured to trigger on specific events like transactions. For scenario C, a standard promotion rule would be created to check the product type (apparel) and the member's tier (Gold) within a single transaction journal, without needing to track cumulative data.

3. Salesforce Help, Loyalty Management, "Create a Promotion":

Under the section "Define Eligibility for the Promotion," the documentation distinguishes between standard eligibility (like tier or enrollment) and eligibility based on engagement attributes. This distinction clarifies why scenarios C and D do not require engagement attributes, as their eligibility can be defined through other standard promotion settings.

The requirement is to classify different types of accrual transactions, such as 'Enrollment Bonus' or 'Flight Purchase'. In the Salesforce Loyalty Management data model, the Transaction Journal object records each individual transaction. This object includes standard lookup fields to Journal Type and Journal Subtype.

The Journal Type is used for high-level categorization (e.g., Accrual, Redemption, Reversal). All the transactions listed in the scenario are of the 'Accrual' type. The Journal Subtype object is specifically designed to provide a more granular classification within a Journal Type. Therefore, the administrator should create a Journal Subtype for each specific case like 'Enrollment Bonus' and 'Member Referral' to properly classify these accrual transactions.

A. Create a custom field on transaction journal object

This is incorrect because it bypasses the standard, built-in functionality of the Journal Subtype object, which is designed specifically for this purpose, leading to a non-standard implementation.

B. Create a custom field on Loyalty Ledger object

This is incorrect because the Loyalty Ledger object tracks a member's aggregate point balance, not individual transactions. Classification must occur at the transaction journal level.

C. Create a Journal Type for each case.

This is incorrect because Journal Type is for broad categories like 'Accrual' or 'Redemption'. Creating a new Journal Type for each accrual reason misuses the data model.

1. Salesforce Help Documentation, Loyalty Management Objects:

Journal Subtype: "Represents the subtype of a transaction journal, such as referral bonus or welcome bonus." This directly aligns with the examples in the question ('Enrollment Bonus', 'Member Referral').

Journal Type: "Represents the type of a transaction journal, such as accrual or redemption." This confirms its use for high-level categories, not the specific reasons mentioned in the scenario.

Transaction Journal: The documentation shows that the Transaction Journal object has standard fields for JournalTypeId and JournalSubtypeId, indicating these are the intended objects for classification.

2. Salesforce Developer Guide, Object Reference for Salesforce and Lightning Platform:

JournalSubtype: The API documentation for the JournalSubtype object describes its purpose as providing a sub-classification for a JournalType. For a JournalType of 'Accrual', JournalSubtype could be 'Product Purchase' or 'Welcome Bonus', which directly supports the correct answer. (Section: Standard Objects > JournalSubtype).

Transaction Journals are the foundational records within Salesforce Loyalty Management that log every member activity affecting their loyalty balance. Each time a member earns points (accrual), spends points (redemption), or has their balance adjusted, a Transaction Journal record is created. By analyzing the volume, frequency, and type of these transactions, a company can directly and granularly measure how members are engaging with the loyalty program. These journals serve as the primary source of truth for all member interactions and are essential for tracking engagement patterns over time.

A. Analytics Studio: Analytics Studio (CRM Analytics) is a tool used to visualize and analyze data. While it can be used to create dashboards to measure engagement, it relies on the underlying data from Transaction Journals to do so.

B. Qualifying Currency: Qualifying Currency is a metric that contributes to a member's tier status. It is an outcome of engagement (e.g., points earned from purchases), not the method or record used to measure the engagement itself.

D. Benefits types: Benefit types define the perks or rewards offered to members, such as discounts or free shipping. They are designed to drive engagement, not to measure it.

1. Salesforce Help Documentation, "Transaction Journals": "A transaction journal is a record of a member’s credit or debit transaction. Transaction journals are created when a member accrues or redeems points, or when points are adjusted or expired." This establishes Transaction Journals as the primary record of member activity.

2. Salesforce Help Documentation, "View a Member's Loyalty Activity": "Use transaction journals to track a member's activities in a loyalty program. You can view a member's transaction history in the Transaction Journals related list on the Loyalty Program Member record page." This directly states that Transaction Journals are used to track member activities.

3. Salesforce Help Documentation, "Reports and Dashboards for Loyalty Management": "You can create reports on transaction journals to analyze the transactions that occurred in a specific period." This confirms that Transaction Journals are the source object for analyzing and measuring engagement through reporting.

4. Salesforce Developer Documentation, "Loyalty Management Data Model": The entity relationship diagram for Loyalty Management shows the TransactionJournal object as the central object linking a LoyaltyProgramMember to their specific point-related activities, highlighting its role in recording engagement.

To meet the Chief Marketing Officer's requirements, the administrator must configure three core elements. First, to "award points... that can be redeemed," a non-qualifying currency is required, as these points are spendable. Second, to "gamify customers that spend the most," a tier system is necessary to segment members and provide exclusive benefits. Tier progression is tracked using a qualifying currency or metric. Therefore, setting up both currency types (Option A) is foundational. Finally, promotions (Option E) are the mechanism used to define the rules for how members earn these points, directly fulfilling the "award points" requirement. These three elements (currencies, tiers, and promotions) form the essential structure of the requested loyalty program.

B. Set up one qualifying currency: This is insufficient. It only addresses tier progression and omits the non-qualifying, redeemable currency required for members to redeem points for products.

D. Set up vouchers for specific products: This is a type of reward or benefit, not a foundational program element. The core requirement is to award redeemable points; vouchers are just one possible redemption option.

1. Salesforce Help, Topic: Define Your Loyalty Program's Currencies: "You can define two types of currencies for your loyalty program: non-qualifying and qualifying. Non-qualifying points are redeemable for rewards. Qualifying points help members upgrade to a higher tier and aren't redeemable." This documentation supports the need for both currency types as described in option A to fulfill both of the CMO's requests.

2. Salesforce Help, Topic: Define Your Loyalty Program's Tiers: "Tiers help you classify members in a loyalty program based on their engagement with your brand. You can create tiers and define the benefits that members of each tier are eligible for." This directly supports the configuration of a tier system (Option C) for gamification and exclusive benefits.

3. Salesforce Help, Topic: Promotions in Loyalty Management: "Use promotions to engage with your loyalty program members. You can set up different types of promotions to credit points, issue vouchers, or provide other benefits to your members." This confirms that promotions (Option E) are the correct mechanism for awarding points to customers.

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.

To enable an external application, such as a member portal, to securely access Salesforce data via APIs, a Connected App must be configured within the Salesforce Platform. The Connected App acts as an intermediary, using standard protocols like OAuth 2.0 to authenticate the external system and authorize its access to specific Salesforce resources. This is a fundamental security and integration prerequisite for allowing external systems to call Salesforce APIs, including those for Loyalty Management, to fetch member information.

A. Create custom objects in Loyalty: Accessing standard member information does not require creating custom objects; Loyalty Management uses its own set of standard and managed objects.

C. Create customer integration code: Writing integration code is the implementation step for calling the API, but the prerequisite on the Salesforce side is to first establish the secure connection point via a Connected App.

D. Create Data Processing jobs: Data Processing Engine (DPE) jobs are used for batch processing and rule calculations, not for enabling real-time, transactional API access from external systems.

1. Salesforce Help, Loyalty Management Developer Guide, "Get Started with Loyalty Management APIs": "To get started with Loyalty Management APIs, create a connected app in your Salesforce org. The connected app gets a consumer key and a consumer secret, which are used in the OAuth 2.0 authentication flow to get an access token."

2. Salesforce Help, "Connected Apps": "A connected app integrates an application with Salesforce using APIs. Connected apps use standard SAML and OAuth protocols to authenticate, provide single sign-on, and provide tokens for use with Salesforce APIs."

3. Salesforce Developer Documentation, "OAuth 2.0 and OpenID Connect on the Salesforce Platform": This documentation details the authentication flows that rely on a Connected App's consumer key (client ID) and consumer secret (client secret) to grant access tokens for API requests. The creation of the Connected App is the first step in any of these flows.

To increase customer spending and lifetime value, a loyalty program must provide a clear structure for progression and tangible incentives. Loyalty Tiers (D) establish a hierarchical structure (e.g., Silver, Gold, Platinum) that motivates members to increase their engagement and spending to achieve higher status. Member Rewards and Benefits (A) are the actual perks, such as discounts, exclusive access, or free products, that members receive. These benefits are often tied to specific tiers, making the progression through tiers desirable. Together, these two features create the core framework that encourages repeat business and enhances customer lifetime value.

B. Loyalty Segments: Segments are used to group members for targeted promotions or analysis, but they do not inherently create the incentive structure that drives spending, unlike tiers.

C. Loyalty product Pricing: This is not a standard, distinct feature in Salesforce Loyalty Management. Special pricing is typically implemented as a benefit or through a voucher reward, not as a separate foundational component.

1. Salesforce Help, Tiers in Loyalty Management: "Tiers are the levels of a loyalty program that members can be in. Members are upgraded or downgraded from tiers based on their engagement with the brand. With tiers, you can effectively reward members who are more engaged with your brand... Each tier can be associated with different benefits." This confirms that tiers are a core feature for structuring member progression and rewards.

2. Salesforce Help, Benefits in Loyalty Management: "Benefits are the rewards that you provide to your loyalty program members. You can create different types of benefits for your loyalty program. For example, you can provide your loyalty program members exclusive access to a new product or a discount on shipping." This establishes benefits as the tangible incentives for members.

3. Salesforce Help, Get Started with Loyalty Management: "Define the framework of your loyalty program. Create tiers to group members and provide benefits based on their tier." This document explicitly links the creation of tiers and benefits as the foundational framework of a loyalty program.

The tier group uses a Fixed Model with a one-year period and a Qualifying Points (QP) reset date of December 31. The key setting is "Extend Expiration for this tier group is Qualifying Points Reset Date."

For a fixed-model tier group, when a member is upgraded, their new tier is valid for the remainder of the current tier assessment period plus the entire next tier assessment period.

The member was upgraded on March 16, 2023.

- The current assessment period is January 1, 2023, to December 31, 2023.

- The next assessment period is January 1, 2024, to December 31, 2024.

Therefore, the member's new Gold tier will expire at the end of the next full assessment period, which is December 31, 2024.

A. December 31, 2023: This is the end of the current assessment period. The member's tier is valid for the next full period as well, not just the current one.

B. March 16, 2024: This date is one year from the upgrade date, which is the logic for an Anniversary Model tier group, not the Fixed Model specified in the scenario.

D. March 31, 2024: This date does not align with the program's annual reset date of December 31 and is not consistent with any standard tier expiration logic.

1. Salesforce Help, Loyalty Management, "How Tier Expiration Works": This document explicitly states, "For a fixed-model tier group, when a member is upgraded to a higher tier, the member’s new tier is valid for the remainder of the current tier assessment period and the entire next tier assessment period." This directly supports the calculation that leads to the December 31, 2024 expiration date.

2. Salesforce Help, Loyalty Management, "Tier Management": This guide details the setup of Tier Groups. It describes the "Tier Model" field, where administrators choose between "Fixed" and "Anniversary". The scenario's use of a "Fixed Model" with a specific reset date (December 31) is central to the correct answer, distinguishing it from anniversary-based calculations.

3. Salesforce Help, Loyalty Management, "Create a Tier Group": In the section detailing the fields for a tier group, it explains the "Tier Period" and "Qualifying Points Reset Frequency". The combination of a one-year period and a fixed reset date (Dec 31) establishes the fixed assessment periods (Jan 1 - Dec 31) used in the expiration calculation.

To meet the requirement of a qualifying period resetting on a specific date (March 31st) for all members, the Fixed tier model must be used. This model establishes a uniform tier assessment period for the entire program, unlike the Anniversary model which is based on individual member enrollment dates.

The second requirement explicitly states that the member's tier is not extended upon expiration. The No Extension setting for the 'Extend Tier Expiration' field directly implements this rule, ensuring that a member's tier status is re-evaluated and potentially downgraded at the end of the fixed period without any grace period.

A. Extend Expiration = member enrollment anniversary: This setting explicitly extends a member's tier, which directly contradicts the requirement that the tier is not extended.

C. Tier-model = anniversary: This model bases the qualifying period on each member's unique enrollment date, which conflicts with the requirement for a single, universal reset date for all members.

1. Salesforce Help Documentation, "Set Up Loyalty Tier Groups":

Tier Model: "Select the model that determines the qualifying period for members of the tier group. Fixed: The qualifying period is the same for all members of the tier group. Anniversary: The qualifying period is based on the enrollment date of each member." This supports the choice of 'Fixed' (B) over 'Anniversary' (C).

Extend Tier Expiration: "Select whether to extend the expiration of members' tiers. If you select to extend the expiration, specify the period for which the tier is extended. No Extension: The member's tier isn't extended." This supports the choice of 'No Extension' (D) over any extension option (A).

2. Salesforce Loyalty Management Developer Guide, "LoyaltyTierGroup" Object Reference:

TierModel Field: The documentation for this field describes the 'Fixed' and 'Anniversary' picklist values, confirming that 'Fixed' is used for a common qualifying period for all members in the tier group.

ExtendExpiration Field: The documentation for this field describes the 'NoExtension' picklist value, which specifies that the member's tier is not extended upon expiration.