Book Image

Salesforce B2C Solution Architect's Handbook

By : Mike King
Book Image

Salesforce B2C Solution Architect's Handbook

By: Mike King

Overview of this book

There’s a huge demand on the market for Salesforce professionals who can create a single view of the customer across the Salesforce Customer 360 platform and leverage data into actionable insights. With Salesforce B2C Solution Architect's Handbook, you’ll gain a deeper understanding of the integration options and products that help you deliver value for organizations. While this book will help you prepare for the B2C Solution Architect exam, its true value lies in setting you up for success afterwards. The first few chapters will help you develop a solid understanding of the capabilities of each component in the Customer 360 ecosystem, their data models, and governance. As you progress, you'll explore the role of a B2C solution architect in planning critical requirements and implementation sequences to avoid costly reworks and unnecessary delays. You’ll learn about the available options for integrating products with the Salesforce ecosystem and demonstrate best practices for data modeling across Salesforce products and beyond. Once you’ve mastered the core knowledge, you'll also learn about tools, techniques, and certification scenarios in preparation for the B2C Solution Architect exam. By the end of this book, you’ll have the skills to design scalable, secure, and future-proof solutions supporting critical business demands.
Table of Contents (20 chapters)
1
Section 1 Customer 360 Component Products
7
Section 2 Architecture of Customer 360 Solutions
13
Section 3 Salesforce-Certified B2C Solution Architect

Chapter 2

  1. Professional Edition does not support API-based integrations by default, which are required in a B2C integration. The client must either enable API integration for Professional Edition or upgrade to Enterprise or Unlimited.
  2. Service Console – this is where agents work with customers. The service app is for managing the Service Cloud instance.
  3. Omni-channel routing.
  4. Knowledge articles.
  5. Pre-chat variables stored in a hidden form field.
  6. A REST API for individual record updates and queries, a Bulk API for large-volume data exchange, and a Connect API for building external user experiences.
  7. Service Cloud API limits would not support tracking data as high-volume as storefront page views, nor would they have appropriate performance characteristics. Since most commerce browsing is for anonymous users, it's also unlikely that this data can be accurately correlated with known customers, making it of limited use. An analytics solution, or Customer...