Explanation

Earning activities in Salesforce Loyalty Management are defined through transaction journals, which log member actions like purchases or referrals that accrue points. To analyze these in reports, the management team needs visibility into the structures categorizing these activities—Journal Type for broad categories (e.g., accrual), Journal Subtype for specifics, and Transaction Journal for actual records. "Read, View All" ensures comprehensive access to all records for accurate, org-wide reporting without needing edit rights.

Correct Answer: D

✅ D. Read, View All access on Journal Type, Journal Subtype, and Transaction Journal Objects
This permission set grants the team read access to object definitions and View All to see every record across the org, perfect for querying and reporting on all earning activities. Journal Type outlines accrual categories, Subtype adds details like purchase types, and Transaction Journal captures the events—enabling detailed analysis of available activities, point earnings, and trends without data gaps or manual exports.

❌ A. Read, Edit access on Journal Type, Loyalty Member Promotions, and Loyalty Member Benefits Objects
Edit access allows modifications, which isn't needed for analysis and risks accidental changes to program rules. Promotions and Benefits focus on reward delivery, not earning setups, so reports would miss core transaction data, leading to incomplete views of activities like what qualifies for points accrual.

❌ B. Read, Create access on Journal Type, Loyalty Member Currencies, and Partner Products Objects
Create access supports adding new records but exceeds read-only needs for reporting, potentially causing over-permissioning. Currencies track point balances, and Partner Products handle external redemptions—not the earning activities themselves, resulting in reports skewed toward post-earn metrics rather than activity availability.

❌ C. Read, View access on Journal Type, Partner Products, and Loyalty Ledgers Objects
"View" likely means basic record visibility, but without "View All," access might be limited to owned records, hindering org-wide reports. Partner Products and Ledgers deal with collaborations and balances, not defining or logging earning events, so the team couldn't fully analyze activity types or historical accruals.

Reference:
Salesforce Help: Loyalty Management Permission Sets
Developer Guide: TransactionJournal

Explanation:

In this scenario, the customer is eligible for a compensation voucher because the t-shirt is out of stock. Salesforce Loyalty Management enables agents to issue vouchers directly to the customer, ensuring they can redeem it immediately. The voucher must reflect the correct discount value and validity period for proper compensation.

Correct Option:

✅ C. Use Issue voucher from the Loyalty Program Member page
Allows the agent to directly issue a voucher to a specific customer.
Ensures the voucher is linked to the Loyalty Program Member record.
Can configure a 50% discount with a one-year validity, making it immediately usable.
This is the standard Salesforce method for agent-issued, real-time vouchers.

Incorrect Options:

❌ A. Use the “issue Voucher” flow template
Flow templates are designed for automated or repeatable voucher issuance.
They are not ideal for one-off, real-time customer compensation, as the agent cannot control the immediate issuance.
Using a flow template would require additional steps to assign the voucher, delaying customer satisfaction.

❌ B. Activate the voucher assignment batch
Voucher assignment batches are intended for bulk processing of vouchers, typically scheduled for multiple members at once.
This method is not real-time; the customer would not immediately receive the 50% discount.
Relying on a batch could lead to frustration, as the compensation would be delayed until the batch runs.

❌ D. Assign a voucher definition from the customer’s Loyalty Program Member
Assigning a voucher definition only defines the type and parameters of the voucher (e.g., discount percentage, expiration).
It does not actually issue the voucher to the customer.
Without issuing, the customer cannot redeem the discount, so this step alone is insufficient.

Summary:
To ensure immediate compensation, agents must issue the voucher directly from the Loyalty Program Member page. Batch, template, or definition-only methods won’t provide instant access or usability for the customer.

Reference:
Salesforce Loyalty Management – Vouchers Overview

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

In Salesforce Loyalty Management, the distinction between point types is crucial: Non-Qualifying Points (NQP) are the currency members earn for the sole purpose of redemption (getting rewards). Qualifying Points (QP) are used to measure member engagement and determine their Loyalty Tier (e.g., Bronze, Silver, Gold). Since the hotel's goal is to reward members with points that can be converted to cover a night's stay (a redemption reward), the correct currency type to use is the one designed specifically for redemption: Non-Qualifying Points.

✅ Correct Option: D

D. Non-Qualifying Points
Non-Qualifying Points (NQP) are the standard currency used for member redemption activities.
The entire premise of the program—earning points to be redeemed for a free night's stay—aligns perfectly with the function of NQP.
NQP balances can be used directly for rewards or converted into vouchers/discounts, fulfilling the goal of incentivizing more bookings by offering tangible rewards.
Unlike Qualifying Points, NQP can have different expiration rules (fixed or activity-based) that encourage frequent engagement and redemption.

❌ Incorrect Options

A. Qualifying Points
Qualifying Points (QP) are used to measure a member's engagement level to determine their tier status (e.g., moving from Silver to Gold). They typically cannot be redeemed for rewards. Using QP alone would allow members to earn a higher tier but give them no actual spendable points for the free night's stay, failing to meet the core redemption goal.

B. Tier Qualifying Points
Tier Qualifying Points (TQP) is another name or type of Qualifying Point used exclusively to track progress toward a specific loyalty tier. Like standard QP, they are not intended to be used for redemption against the cost of a hotel night. Using this currency type would miss the primary objective of rewarding the member with a spendable value.

C. Non-Qualifying and Qualifying Points
While a full loyalty program often uses both types (QP for tier progression and NQP for redemption), the prompt specifically asks which currency should be used for the goal of redeeming points for a free night's stay. The specific goal described is purely a redemption activity, which only requires the use of Non-Qualifying Points. Including QP is unnecessary and complicates the currency setup for this particular redemption objective.

🔗 Reference
Salesforce Help: Loyalty Program Currencies (Search for the definitions of Qualifying Points and Non-Qualifying Points, noting that Non-Qualifying Points are the currency used for member redemption.)

Explanation

The requirement is to reward members for the sum of multiple activities (three purchases) over a defined period (one month). This is a classic use case for a promotion that tracks cumulative behavior, not one that triggers on a single event or involves partners. The promotion type must be capable of aggregating transaction counts over time.

Correct Option:

✅ (B) Cumulative Promotion
A Cumulative Promotion is specifically designed to reward members based on the total of their activities over a set timeframe.
It tracks progress towards a goal, such as a count of purchases or a sum of spend, and issues the reward only after the cumulative threshold is met.
This perfectly fits the need to encourage sustained engagement by rewarding three purchases in a month.

Incorrect Option:

❌ (A) Standard Promotion
A Standard Promotion provides an immediate, one-time reward for a single, qualifying transaction or event. It does not track or accumulate activities over time to meet a larger goal. For example, it could offer 10 bonus points for a single purchase, but it could not track three separate purchases to grant a final bonus.

❌ (C) Joint Promotion
A Joint Promotion is defined by its funding and partnership structure, not its reward logic. It involves one or more partner brands who share the liability for rewards. While a Joint Promotion could be a Cumulative Promotion, its defining characteristic is the multi-party involvement, not the tracking of cumulative member activities.

❌ (D) Aggregate Promotion
"Aggregate Promotion" is not a standard or valid promotion type within the Salesforce Loyalty Management platform. The correct term for tracking and rewarding the sum of member activities over a period is exclusively "Cumulative Promotion."

Key Point:
Use a Cumulative Promotion when the reward is based on the sum of multiple activities over a period, such as a total number of purchases or total amount spent.

Reference:
Salesforce Help: Loyalty Promotion Types