Salesforce Salesforce-Loyalty-Management Dumps

For creating a large multi-country, multi-currency, and tier-dependent Redemption Catalogue, the recommended approach is toCreate a Decision Table and define the Redemption Catalogue as business rules (C). A Decision Table allows for the efficient management of complex business rules and conditions, such as those involved in a multi-faceted Redemption Catalogue, providing a clear and structured method for defining redemption options based on various criteria like country, currency, and loyalty tier.

To introduce program members to the "Summer Sales" promotional campaign and send email communication via Marketing Cloud with minimal configuration effort, the required actions within the org would be:

• “Add Segments” within the “Promotion Segments” section of the “Summer Sales” Promotion (A):This action allows for the direct association of specific member segments to the promotion, enabling targeted communication and engagement with minimal effort.
• Create a new segment within CDP (D):By creating a new segment within the Customer Data Platform (CDP), you can easily define and manage the group of loyalty program members who qualify for the "Summer Sales" promotion. Thissegment can then be used in conjunction with Marketing Cloud for targeted email campaigns.

Options B and C, involving adding segmented loyalty program members to new campaigns and creating custom reports, are not as directly related to the goal of minimal configuration effort for introducing members to the promotion and communicating via Marketing Cloud.

Salesforce documentation on Loyalty Management, CDP, and Marketing Cloud integration would provide insights into efficiently setting up promotions and communicating with targeted segments of loyalty program members.

To ensure Loyalty members can access their program-specific records on the Loyalty Member Portal, an Administrator should:

• Using Experience Cloud sharing sets, specify Account as the object of your sharing set (A):Sharing sets in Experience Cloud allow you to define access rules for external users based on their relationship to records in Salesforce. Specifying Account as the object in a sharing set can enable portal users to access theirLoyalty Program information if their portal user account is linked to their Account record in Salesforce.
• For the Loyalty Member, 'Enable Customer User' on the Contact or 'Enable Partner User' on the Account (D):Enabling a Customer or Partner User on the Contact or Account associated with the Loyalty Member allows that individual to access the portal. This step is crucial for granting Loyalty Program members the ability to log in and view their Loyalty Program-specific information.

Options B and C, while related to portal access and user setup, do not directly address the specific requirement of accessing Loyalty Program information. Option E is also relevant but more focused on enabling self-registration and user creation/login processes rather than directly impacting access to Loyalty record information.

Salesforce documentation on Experience Cloud and Loyalty Management would provide guidance on setting up and configuring access for Loyalty Program members to view their information on a member portal, ensuring a seamless user experience.

For a retailer looking to allow Loyalty program members to redeem points with redemption partners, the correct setup in Salesforce Loyalty Management involves configuring the partner record as a redemption partner. This includes:

• Setting the program partner type to "redemption" to indicate that the partner is involved in the points redemption process.
• Activating the partner record to make it available for transactions within the Loyalty Management application.
• Defining the redemption cost per unit, which specifies how many points are required for members to redeem specific rewards or benefits from the partner.

This setup ensures that Loyalty program members can redeem their points when shopping with strategic partners, aligning with the retailer's goal of enhancing the value and utility of their Loyalty program.

To accomplish the hotel group's goals, a Loyalty Consultant should use Non-Qualifying Points as the currency type for the Loyalty program. Non-Qualifying Points are ideal for rewards that do not contribute to tier progression but can be redeemed for benefits, such as a free night's stay. This setup allows members to earn points based on their stays, which can then be redeemed for rewards within the hotel group, encouraging more frequent bookings and enhancing member loyalty.

To meet the company's business requirements of making points available for Loyalty Program Members after a return period of 14 days, the best solution is toEnable Deferred Points (C). Deferred points are a feature in Salesforce Loyalty Management that allows points to be earned but not immediately available for redemption, typically used to account for return periods or other conditional delays. By enabling deferred points, the company can ensure that points are only made available after the specified return period has passed, aligning with their business strategy and reducing the risk of point redemption for returned products.

To set up an expiration model based on activity after the last accrual transaction in a points-based Loyalty Program at Universal Container, the Salesforce Administrator shouldSet up Expire Activity Based Non-Qualifying Points (C). This expiration model allows non-qualifying points to expire after a certain period of inactivity, meaning no new accrual transactions occur within that timeframe. It encourages ongoing engagement from Loyalty Program members by incentivizing regular transactions to keep their non-qualifying points active.

Option A (Expire Activity Based Qualifying Points) pertains to qualifying points, which are typically used for tier progression and may have different expiration criteria. Option B (Expire Fixed Non-Qualifying Points) refers to a fixed expiration model that does notconsider member activity. Option D (Set up Reset Qualifying Points) involves resetting qualifying points, which is a different concept from expiration based on activity.

Salesforce documentation on Loyalty Management would provide insights into configuring various expiration models for points within a Loyalty Program, including activity-based expiration to foster continuous member engagement and transactional activity.

To enable agents to view Loyalty Program Member information on a Case record in Service Cloud, the IT Administrator shouldOn the Case Page Layout, add the 'View Member Profile' component and select the required Related Lists from Loyalty Program Member (B). Thiscomponent 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.

Salesforce Loyalty Management offers seamless integrations within the Salesforce ecosystem that can be easily enabled to meet ABC Corp.'s business requirements for launching a new Loyalty program, including:

• Option A:Salesforce Service Cloud, which can be integrated to manage customer service interactions and inquiries related to the Loyalty Program, enhancing the overall customer experience.
• Option D:Salesforce Marketing Cloud, which allows for the creation and management of targeted marketing campaigns to engage Loyalty Program members, promote rewards, and encourage participation.

To configure tiers within the Loyalty Program at Northern Trail Outfitters (NTO) for giving vouchers to members in the Premium Tier, the configuration involvesVoucher Management; Benefits Setup (in Program console); Benefit Action to define downstream actions and FLOW - Benefit action for orchestration (C). This comprehensive approach allows for the creation and management of vouchers as benefits associated with the Premium Tier, the setup of these benefits within the Loyalty Program console to specify the conditions and entitlements, and the use of Salesforce Flow for orchestrating the process of issuing vouchers to qualifying members.

This method ensures that vouchers are systematically managed, associated with the correct tier and member eligibility criteria, and efficiently distributed to members through automated processes, enhancing the value and appeal of the Premium Tier.

Salesforce documentation on Loyalty Management would detail the steps for setting up and managing tier-based benefits, including the use of Voucher Management and Flow for effective benefit administration and member engagement.

When designing an experiential Loyalty Program, the recommended objects to use for tracking member activities with the program are:

• Loyalty Ledger & Transaction Journal (A):The Loyalty Ledger tracks the overall balance of a member's points or currencies, while the Transaction Journal records all point-related transactions, including accruals, redemptions, and adjustments. Together, these objects provide a comprehensive view of a member's interactions and engagements with the loyalty program.
• Journal Type & Journal Subtype (D):These objects allow for the categorization and sub-categorization of transactions within the Transaction Journal, making it possible to track different types of member activities and engagements within the program, such as event attendance, purchases, or other actions.

Options B (Loyalty Member Currency & Transaction Journal) and C (Transaction Journal Type & Transaction Journal Subtype) are partially correct but do not fully capture the recommended best practices for tracking member activities in an experiential loyalty program.

Salesforce documentation on Loyalty Management would detail the use of these objects and best practices for tracking and managing member activities within a loyalty program, ensuring a rich and engaging member experience.

To analyze the performance of the Loyalty Program, a System Administrator needs the 'Loyalty Analytics User' permission. This permission set grants access to the analytics and reporting features within Salesforce Loyalty Management, allowing the administrator to customize, view, and analyze data related to the loyalty program's performance, member engagement, and other key metrics.

When adding a program partner in Salesforce Loyalty Management, the required fields include:

• Name, Program, Program Partnership Category, Type, Billing Type (B):This combination of fields ensures that a program partner is properly defined and categorized within the Loyalty Management system.

Options A, C, and D include fields like "Partnership Start Data," "Industry," and "Status," which, while important, are not the core required fields for initially setting up a program partner in Salesforce Loyalty Management.

Salesforce Loyalty Management documentation provides comprehensive details on setting up program partners, including the required fields and best practices for managing partnerships to enhance member engagement and program value.

To grant users proper access to a newly created analytics app, two steps are required. First, assigning user access to the analytics for Loyalty role ensures that users have the necessary permissions to view and interact with Loyalty-specific analytics content. This role typically encompasses permissions tailored to accessing and analyzing data within the context of the Loyalty Management application.

Second, assigning user access to permission sets for analytics for Loyalty is another way to grant targeted access. Permission sets allow for fine-grained control over user permissions, enabling the Administrator to specify exactly what analytics content a user can access and interact with. By using permission sets, access can be customized to fit the specific needs and roles of different users within the organization.

QUESTIONNO: 22

A Loyalty Management Consultant recently created a new analytics app, but users cannot access the app.

Which two statement correctly describes how to grant proper access on the user details page

A. Assign user access to the analytics for Loyalty role.

B. Assign access by checking CRM Analytics plus user

D. Assign user access to permission sets for analytics for Loyalty.

D. Assign the user the analytics profile for analytics for Loyalty.

Answer:AC

To enable users to access a new analytics app, it's crucial to assign them the appropriate roles and permission sets. Assigning user access to the analytics for Loyalty role ensures that users are granted the necessary permissions to view and interact with the Loyalty analytics content. This role is designed to encompass the permissions required for accessing and analyzing Loyalty-specific data.

Additionally, assigning user access to permission sets for analytics for Loyalty is an effective way to provide access. Permission sets offer a flexible and granular approach to managing user permissions, allowing Administrators to specify the exact capabilities each user should have within the analytics app. This method ensures that users have access to the appropriate analytics tools and data relevant to their roles and responsibilities within the Loyalty program.

To add a new accrual and redemption partner to a Loyalty program in Salesforce Loyalty Management, the steps are:

• Enter the program partner name > Associate to an account > Set program partner type to ‘Both’ (Accrual and Redemption) (A):This process involves identifying the new partner by name, associating them with a specific account in Salesforce to link their business details, and defining their role in the loyalty program as both an accrual and redemption partner. This ensures that thepartner can both award points to members for eligible transactions and redeem points for rewards, enhancing the program's value and appeal to members.

Options B, C, and D offer variations that do not align with the standard process for adding a new partner in Salesforce Loyalty Management. The correct procedure involves associating the partner with an account (not just a contact) and specifying their role in terms of point accrual and redemption to ensure clear and effective partnership management within the program.

Salesforce Loyalty Management documentation provides guidelines on adding and managing program partners, including the steps to integrate new partners effectively, ensuring they contribute positively to the loyalty program's goals and member experiences.

When implementing a new Loyalty Program while retaining the design and functionalities of an existing Loyalty Member Portal built with the Loyalty Experience Cloud template, Universal Containers should consider:

• Option B:Utilizing existing Experience Cloud components to ensure consistency in design and functionality. This approach leverages the reusable nature of Experience Cloud components, allowing for efficient replication of the portal's look and feel without the need for extensive redevelopment.
• Option D:Creating a new Loyalty Member Portal specifically for the new Loyalty Program. This ensures that the new program has a dedicated portal tailored to its unique requirements while maintaining the desired design and functionalities. This approach allows for customization and scalability, accommodating any program-specific features or requirements.

When setting up tier groups in Salesforce Loyalty Management for a sports clothing and accessories retailer, the three necessary attributes to define are:

• Qualifying period (A):This defines the time frame within which the members' activities (like purchases or interactions) contribute towards their tier status. It's crucial for determining how member activities are evaluated against tier criteria.
• Tier Period (C):This attribute specifies the duration for which a member remains within a particular tier once qualified, before re-evaluation. It's important formaintaining the tier structure over time and for member expectation management.
• Tier Model (D):This outlines the basis on which the tiers are structured, such as points accrued, spending amount, or other qualifying activities. It forms the foundation of the tier system, dictating how members progress through different levels.

Option B, Fixed Tier Model, is not an attribute but a type of Tier Model. Option E, Non-Qualifying Period, is not a standard attribute required for setting up tier groups in Salesforce Loyalty Management.

Salesforce documentation on Loyalty Management would detail the process of setting up tier groups, including the necessary attributes and considerations for effectively structuring a multi-tiered loyalty program.

For Northern Trail Outfitters to display member information in its external member portal, a crucial prerequisite is the creation of a Connected App in Salesforce Platform. This Connected App facilitates secure API access to Salesforce data, including Loyalty Management information, by providing an authentication and authorization framework.

By setting up a Connected App, Northern Trail Outfitters can establish a secure connection between its external member portal and Salesforce, enabling the retrieval of member information through Loyalty APIs. This setup ensures that the external portal can access up-to-date loyalty data, such as member points, tier status, and transaction history, in a secure and controlled manner, enhancing the member experience outside of Salesforce.

To communicate a new Promotion to eligible Loyalty Program members, Northern Trail Outfitters can utilize integrated Salesforce applications such as:

• Option C:Salesforce Customer Data Platform (CDP), which allows for the aggregation and management of customer data, enabling targeted communication based on member attributes and behaviors.
• Option D:Salesforce Marketing Cloud, which offers robust email marketing and customer engagement tools. By integrating Loyalty Management data with Marketing Cloud, NTO can create personalized and targeted email campaigns to inform members about new promotions.

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 reaching 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 target a promotion only for specific products in a Loyalty Program, the correct implementation approach is toMap products to promotion through an out-of-the-box Related List (B). This approach leverages standard Salesforce functionality, allowing administrators to associate specific products with a promotion directly within the promotion's record. This direct mapping ensures clarity and ease of administration, enabling targeted promotional activities that are specific to certain products.

Option A (Create a custom list on the promotion), Option C (Create product attributes in Promotion Setup), and Option D (Add promotion to the lookup field on the product) are not standard Salesforce Loyalty Management functionalities for associating products with promotions and may require custom development or configuration that is more complex and less maintainable than using out-of-the-box related lists.

Salesforce documentation on Loyalty Management would detail the process for setting up and managing promotions, including how to associate promotions with specific products to achieve targeted marketing objectives within the Loyalty Program.

To edit Loyalty Management objects, the "Loyalty Management" permission set license is required. This license grants users the necessary permissions to access and modify Loyalty Management-specific data and configurations.

• Option B"Loyalty Management" is the correct answer as it directly relates to the permissions needed to work with Loyalty Program configurations and objects within Salesforce.
• Options A, C, and D pertain to analytics and data pipeline functionalities and do not grant permissions to edit Loyalty Management objects.

In the reference integration between Salesforce Loyalty Management and Commerce Cloud, two key features are supported: 'Loyalty member profile' and 'Loyalty member enrollment.' The 'Loyalty member profile' feature allows for the management and viewing of loyalty member information within Commerce Cloud, providing a seamless experience for members as they interact with the brand across different platforms. The 'Loyalty member enrollment' feature enables new customers to join the loyalty program directly through Commerce Cloud, facilitating the growth of the loyalty program and enhancing customer engagement by leveraging the commerce platform.

When creating and managing member groups in Salesforce Loyalty Management, administrators should consider the following key facts:

• Groups are associated with tiers (A):This statement is not necessarily true as groups can be created for various purposes, not just tied to specific tiers. Groups can be used to segment members for targeted promotions, communications, or benefits irrespective of their tier status.
• Accrual type transactions associated with a group can be canceled (B):This is an important consideration as it implies that transactions contributing to a group's accrual points can be adjusted or canceled if necessary, affecting the group's total points and potentially members' benefits.
• Qualifying points can’t be transferred to a group (C):This is a critical consideration because it highlights the limitation that individual member's qualifying points cannot be directly transferred into a group's pool of points. Thisensures the integrity of qualifying points for tier progression and other individual benefits.
• Vouchers can’t be issued to groups (D):This is another important consideration. While individual members within a group can receive vouchers, a voucher cannot be issued at the group level. This ensures that benefits are tailored and distributed to individual members, maintaining personalization in the loyalty program.
• Promotions can’t be offered to groups (E):This statement is incorrect. Promotions can indeed be targeted at specific groups, allowing for more tailored marketing efforts and member engagement strategies within the loyalty program.

References to Salesforce documentation on Loyalty Management would provide detailed guidelines on how to effectively create, manage, and leverage member groups within a loyalty program, ensuring that administrators are well-informed of these considerations.

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 Bis 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 Dis 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 Ais not 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 Cusing "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 set up a 10% discount on top of the annual summer sale for loyalty program customers in Salesforce Loyalty Management, the consultant must:

• Create within the Loyalty Experiences tab a new promotion for the Summer Sales campaign where the Loyalty Promotion Type is Standard and the Fulfillment Action is Issue Voucher (B):This step involves setting up a new promotion specifically for the summer sale, defining it as a standard promotion type, and specifying that the fulfillment action for eligible members will be to issue a voucher, which in this case would be the 10% discount voucher.
• Create within the Loyalty Experience tab a new voucher definition where the Type Is Discount Percentage and the Expiration Type is fixed Date (D):This step involves defining a new voucher that applies a discount percentage (10% in this case) to purchases, with a fixed expiration date to limit the offer to the summer sale period. This ensures that the promotion is time-bound and encourages members to take advantage of the offer during the sale.

Options A and C involve creating a voucher definition and a benefit type, respectively, but do not align precisely with the steps required to set up a promotion that includes issuing a discount percentage voucher with a fixed expiration date for a specific campaign like the summer sale.

Salesforce Loyalty Management documentation would provide detailed guidance on creating promotions and vouchers, ensuring that loyalty program consultants can effectively design and implement targeted offers to enhance member engagement and sales during key promotional periods.

For designing a new tier-upgrade process in a Loyalty Program, the Consultant should select:

• A flow to perform the tier-upgrade rule and another flow to perform the tier-upgrade orchestration process (C):This approach allows for the separation of concerns, where one flow is responsible for evaluating whether members meet the criteria for a tier upgrade, and another flow is responsible for the actual process of upgrading the member's tier. This modular design improves maintainability and scalability.
• A data-processing-engine (DPE) to identify the qualified members (D):The DPE can efficiently process large sets of member data to identify those who qualify for a tier upgrade based on the program's criteria. This component is crucial for automating the tier-upgrade process at scale, especially in programs with a significant number of members.

Option A combines both processes into a single flow, which could become complex and harder to maintain. Option B suggests using a single flow for scheduling and processing, which might not offer the required flexibility and efficiency for handling complex tier-upgrade criteria and orchestration.

Salesforce documentation on Loyalty Management provides guidelines on leveraging Flow and DPE for automating and orchestrating various loyalty program processes, including tier upgrades.

Within the Salesforce Customer Data Platform (CDP), the Loyalty Program entity is attributed with various fields that help in managing and analyzing the loyalty program's performance. Two essential fields attributed to this entity are Created Date and Last Modified Date.

The Created Date field records the timestamp when the Loyalty Program entity was initially created in the system, providing a reference point for the program's inception. The Last Modified Date field, on the other hand, keeps track of the most recent update made to the Loyalty Program entity, offering insights into the program's maintenance and evolution over time.

These fields are crucial for administrative and analytical purposes, allowing businesses to monitor the lifecycle of their loyalty programs and make data-driven decisions based on the program's history and modifications.

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 specific 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.

Salesforce Loyalty Management can help Universal Containers build a network of brand advocates and fulfill their new strategy in the following ways:

• Send promotions at the right time to the right program members using Salesforce CDP's market segmentation capabilities (A):Leveraging CDP for segmentation allows for targeted communication and promotional offers,engaging members with personalized experiences that can foster brand advocacy.
• Create a Loyalty program tier with member benefits to keep customers engaged (C):Implementing tiered loyalty programs with exclusive benefits can incentivize members to engage more deeply with the brand, earning rewards that make them more likely to advocate for the brand.
• Issue tickets to a concert to any Loyalty member that posts a product review on social media (D):This approach directly engages members in brand advocacy by rewarding them for sharing their positive experiences on social media, effectively turning satisfied customers into vocal supporters.

Option B (Define a transactional point-based program) is a common loyalty program feature but does not directly contribute to building a network of brand advocates. Option E (Maintain a Loyalty solution on separate systems) does not specifically address the strategy of fostering brand advocacy through personalized experiences and engagement.