To target a specific audience with a Promotion in Salesforce Loyalty Management, an administrator could:

Option C "Create a segment in the Salesforce Customer Data Platform and associate the segment to the promotion." This allows for precise targeting based on detailed segmentation criteria.

Option D "Link a promotion to a campaign and associate a segment to the campaign." This method utilizes Salesforce's campaign management features to target promotions to specific segments.

For integrating a custom object "Member TierUpdate_c" with a journey in Salesforce Marketing Cloud for real-time tier change notifications, the correct data source option is:

Option D "Salesforce Data" as the Entry Source, with the custom object "Member TierUpdate_c" as the data source. This option allows for real-time triggering of journeys in Marketing Cloud based on updates to Salesforce records, in this case, the "Member TierUpdate_c" object which tracks tier upgrades.

Options A and B do not correctly target the custom object designed to track tier changes.

Option C, using a "Data-Extension," would not provide the real-time integration needed for immediate email notifications upon tier changes.

To enable the Data Processing Engine for processing tier assessment rules on members' anniversary dates, the required permission set is:

Data Pipelines Base User (B): This permission set grants the necessary access to configure and manage Data Processing Engine definitions, allowing for the transformation of Salesforce data and the writing back of transformation results as new or updated records. This capability is crucial for automating tier assessments and other data-intensive processes within Salesforce Loyalty Management.

Options A (CLA Analytics Base Admin), C (Rule Engine Designer), and D (Loyalty Analytics Admin) do not specifically pertain to enabling the Data Processing Engine for tier assessment and other data processing tasks within Loyalty Management.

Salesforce documentation on Loyalty Management and Data Processing Engine would provide insights into the required permissions and best practices for setting up and managing data transformations and tier assessments within a loyalty program.

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.

One of the ways a company can measure member engagement with the Loyalty Program is through Analytics Studio. Analytics Studio is a powerful tool within Salesforce that allows organizations to create custom dashboards and reports based on their data. By leveraging Analytics Studio, a company can analyze various aspects of the Loyalty Program, such as member activity, redemption rates, point accumulation, and more. This insight can help identify trends, areas for improvement, and opportunities to enhance member engagement and loyalty.

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.

In Salesforce, objects that count toward data storage capacity include Person Account, Orders, Loyalty Program Members, Transaction Journals (A). These objects are essential components of a Loyalty Program and each record created within these objects occupies space in Salesforce's data storage. Person Accounts and Orders are standard Salesforce objects, while Loyalty Program Members and Transaction Journals are custom objects introduced by the Loyalty Management application, all contributing to the overall data storage usage.

To segment and identify specific tier members for a journey within Marketing Cloud, it's essential to synchronize the right objects from Salesforce to Marketing Cloud. Synchronizing the 'Contact' object ensures that the basic member information is available. The 'Loyalty Program Member' object provides detailed information about the member's involvement in the loyalty program, and the 'Loyalty Member Tier' object offers insights into the member's current tier status. This setup allows for precise targeting and personalization of marketing efforts aimed at encouraging Loyalty Tier B customers to ascend to Loyalty Tier A, thereby enhancing member engagement and program value.

To present Loyalty Program data to the Marketing Manager, an Administrator needs to enable CRM Analytics and create a Loyalty app within it. CRM Analytics (formerly Einstein Analytics) allows for the creation of custom analytics apps that can visualize and analyze data from various sources, including Salesforce Loyalty Management. By creating a Loyalty app within CRM Analytics, the Administrator can design dashboards and reports specifically tailored to the needs of the Marketing Manager, providing insights into the reward program's progress and effectiveness.

To provide Cloud Kicks' customer base, who are heavy mobile users, with access to member program information, the consultant should Enable Experience Cloud and customize the Loyalty Member Portal (A). Experience Cloud (formerly known as Community Cloud) allows for the creation of branded, mobile-responsive portals that can be customized to meet specific business needs, including providing loyalty program members with access to their program information, account status, rewards, and more. This approach leverages existing Salesforce capabilities and does not require the development of a new mobile app, making it a cost-effective and efficient solution.

To develop an InApp-Dashboard showing top and bottom agent performers in the Loyalty call center, the most suitable dashboard available through the Analytics Studio tool is the:

Loyalty Member Services Dashboard (D): This dashboard is designed to track the performance of agents interacting with loyalty program members, including metrics like the number of members assisted, customer satisfaction scores, and modifications made by agents. It provides insights into agent performance and service quality in the context of loyalty member services.

The Program Manager Home Dashboard (option A), Member Services Manager Home Dashboard (option B), and Team Performance Dashboard (option C) may contain relevant metrics but are not specifically tailored to tracking individual agent performance in the context of loyalty member services.

Salesforce documentation on Analytics for Loyalty would provide information on available dashboards and their intended use cases, including how to customize and leverage them for specific analytical needs, such as tracking call center agent performance.

To turn on analytics and dashboards for Loyalty, the three essential steps are:

Assign Analytics for Loyalty User Permissions (A): This step ensures that users who need to access Loyalty Analytics have the necessary permissions to view and interact with the analytics and dashboards.

Schedule dataflow for the analytics (C): Dataflow is the process by which data moves from Salesforce objects into Analytics datasets. Scheduling dataflow is crucial for ensuring that the analytics and dashboards have up-to-date information from the Loyalty Management system.

Install CRM Analytics package (E): This involves adding the CRM Analytics package to your Salesforce org, which provides the tools and capabilities needed to create and customize analytics and dashboards for Loyalty Management.

Option B (Create standard Salesforce reports and dashboard) and Option D (Create an App using existing templates) are valuable for general reporting and app development within Salesforce but are not specifically tied to the initial steps for enabling Loyalty Analytics and dashboards.

Salesforce documentation on Loyalty Management and CRM Analytics would detail the process of enabling analytics for Loyalty, including the setup of user permissions, dataflow scheduling, and the installation of necessary packages to utilize analytics and dashboards effectively.

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.

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.

To associate the new products with their respective partners within the loyalty partner product section, the Administrator should take two steps. For the Chocolate cookies linked with the snack category, the Administrator should add the partner in the Lookup on the Chocolate cookie product. This directly associates the product with the specific partner responsible for the snack category.

Similarly, for the Green soda from the beverage importer, the Administrator should choose the ‘Product’ option and map the Green soda to the partner. This step ensures that the beverage product is correctly associated with the beverage importer, maintaining accurate and organized tracking of partner products within the Loyalty Program. These configurations facilitate seamless management and representation of partner products within the program, enhancing the clarity and efficiency of partner product associations.

To meet the hotel group’s requirements for providing live updates to Loyalty members about their program membership without complex customization, the following three tasks should be implemented:

LoyaltyLedger: This feature allows members to view their points balance and transaction history1. It is a key component of the Loyalty Management product that tracks the accumulation and redemption of loyalty points, which is essential for members to stay informed about their membership status.

Contact Record: Maintaining up-to-date contact records is crucial as it ensures that members can receive notifications and access their membership details1. The contact record in Salesforce is the central repository of member information, which can be used to personalize communication and provide members with relevant updates.

LoyaltyMemberTier: Implementing the LoyaltyMemberTier feature enables members to see their current tier status and understand how they can move to the next tier1. This feature motivates members to engage more with the loyalty program by providing them with clear goals and benefits associated with each tier.

These features are part of the Salesforce Loyalty Management application and are designed to enhance customer engagement without requiring extensive customization. They enable the hotel group to provide a seamless experience for members to access their loyalty program details.

The new expiry date for the member after being upgraded to the Gold tier would be March 31, 2024. In Salesforce Loyalty Management, when a member is upgraded to a new tier, the expiry date is set based on the tier's fixed model and period. Since the member was upgraded on March 16, 2023, and the period is one year, the new expiry date aligns with the end of the month following the one-year anniversary of the upgrade, which is March 31, 2024.

To integrate Marketing Cloud with Loyalty Management for creating journeys for promotions, the most effective method is:

Option D "Use Marketing Cloud Connect." Marketing Cloud Connect integrates Salesforce CRM data with Marketing Cloud, allowing for the creation of targeted, personalized journeys based on Salesforce data, including Loyalty Management data.

Customer support agents can manually adjust points for Loyalty Program Members on the following pages:

Loyalty Program Member page (A): This is the primary interface for viewing and managing individual loyalty program members, including adjusting their points as needed.

Loyalty Program Member Related List (B): This related list, found on related records such as accounts or contacts, provides access to loyalty program member information, including point adjustments.

Transaction Journal (C): The Transaction Journal records all point transactions for loyalty program members, allowing customer support agents to make manual adjustments to points as necessary.

Options D (Account page) and E (Contact page) may provide indirect access to loyalty program member information but are not the primary interfaces for adjusting loyalty program points.

Salesforce documentation on Loyalty Management would detail the interfaces and processes for managing loyalty program members' points, including the roles and permissions required for customer support agents to make adjustments.

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.

Incorporating a targeted strategy in a Loyalty Program can lead to the following benefits:

Personalized digital marketing (A): A targeted strategy allows for more personalized communication and offers, tailored to the specific behaviors, preferences, and tiers of loyalty program members, enhancing member engagement and program effectiveness.

Data-based segmentation strategy (D): By leveraging data to segment the loyalty program members, the program can deliver more relevant and appealing offers and communications, increasing member satisfaction and program participation.

Automatically archiving transaction journey data (option B) is more of a data management practice and not directly a benefit of running a targeted strategy. Rewarding customers based on their tiers (option C) is a common practice in loyalty programs but does not specifically result from implementing a targeted strategy.

Salesforce documentation on Loyalty Management would detail the advantages of implementing targeted strategies within loyalty programs, including how to leverage Salesforce tools for personalized marketing and data-driven segmentation.

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 their Loyalty 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.

To meet the business need of sending an SMS to a member's mobile device after a purchase and an increase in non-qualifying points, the required Salesforce solutions are Marketing Cloud Connect (A) and Marketing Cloud MobileConnect (B). Marketing Cloud Connect facilitates the integration between Salesforce Loyalty Management and Marketing Cloud, while MobileConnect is a specific tool within Marketing Cloud designed for sending SMS messages to mobile devices, allowing for timely and targeted communication with loyalty program members.

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.

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.

The root cause of the issue where all the Loyalty automations that have Data Processing Engine actions are failing is because the Default Workflow User is missing the CLAAnalytics Base User permission set license (B). This permission set license is essential for the Default Workflow User to execute actions related to the Data Processing Engine within Salesforce Loyalty Management. Without this permission set, the user lacks the necessary access rights to run these specific automations, leading to the observed failures. Salesforce documentation on Loyalty Management would provide guidance on setting up and troubleshooting automations, including the necessary permission sets for different actions.