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

Multi-org, realm, and BU scenarios

Each of the three primary products in your Salesforce B2C solution architecture partitions data in different ways and has a different structure for an instance. This section covers the reasons organizations end up with multiple orgs, realms, and BUs in the first place and why you may or may not want to consolidate that data into a single viewpoint.

Throughout this chapter, we'll use the example of a fictitious organization that has multiple brands and geographies. We'll call this company Packt Enterprises, the parent company of Packt Gear. They also own Packt Sport, an athletics and leisurewear brand.

Each brand has operations in multiple parts of the world, as shown in the following org chart:

Figure 10.1 – Packt Enterprises org chart

This view is focused on the structure of the organization, not the technology they use—we'll evolve that viewpoint as we work through the example in this chapter...