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

Identifying the customer

Identifying customers, just like any other data record, requires understanding two important concepts. The first is the unique identifiers (IDs) that point to that record and the second is the scope in which that identifier is unique.

Some IDs, most notably Universally Unique Identifiers (UUIDs), are unique across all systems for all time. Statistically speaking, the same ID will never be generated twice. Other IDs, such as an order number that increments each time an order is placed, are unique within the scope of a particular commerce site or organization.

These IDs are particularly important because the integration options for each product require internal IDs. That means each system must know the appropriate ID for the systems it needs to update or retrieve a record from to do so efficiently.

The following table shows the required customer identifiers for each of the three-component systems we've discussed so far:

Figure...