Koushik Mukherjee - Sitecore MVP

Sitecore CDP offers a flexible and extensible data model that enables organizations to manage their data as per their needs. CDP captures, unifies, and activates customer data in real time across multiple channels. Its purpose is to build single and coherent customer profiles, which then allow for more targeted personalization. If an organization has custom data models that need to be managed in CDP, they can be easily handled using data extensions. In the above image, a Guest , which is a customer/user, can have multiple orders as well as multiple sessions. An order can also have multiple order items, and similarly, a session can have multiple events. Core Entities Guests    A Guest profile is created in CDP whenever a guest interacts with the brand using any channel. A Guest is the central object in the data model that represents a single customer. A guest data extension in Sitecore CDP allows an organization to specify custom attributes with key-value pairs. A Guest profil...

  What is a Customer Data Platform (CDP)? A Customer Data Platform (CDP) is a tool that collects data from multiple sources  to create a single centralized customer database. In recent years, customer data platforms (CDP) become a hot topic. Brands are set to create strong relationships with their customers through personalized and meaningful digital experiences. In this blog, we’ll cover the basics of Sitecore CDP and user interface in Sitecore portal. What is Sitecore CDP? Sitecore CDP is a customer data platform by Sitecore. It was introduced after Sitecore acquired Boxever in 2021, which later changed to Sitecore CDP.. Sitecore CDP captures, integrates, unifies, segments, and activates all customer data and creates seamless and consistent customer experiences.  Sitecore CDP Architecture The architecture of Sitecore CDP supports  real-time data collection , processing, segmentation, and activation across different channels. It is a cloud-native , API-f...

  As Sitecore continues its evolution toward a fully composable and cloud-native architecture, the Content SDK for XM Cloud marks a significant shift from the legacy JSS SDK. The Content SDK simplifies development, enhances performance, and introduces modern patterns for integrating Sitecore content into front-end applications. In my previous blog post on the Sitecore XM Cloud Content SDK , I discussed the key differences between the JSS SDK and the Content SDK , along with some of the new concepts introduced in the Content SDK. In today's blog, I'll walk you through how you can smoothly migrate your project to the Content SDK . Prerequisites Before you begin, make sure to: Upgrade your existing app to JSS 22.8 . Review the Content SDK changelog to understand major updates. Note that any customizations in your app may require additional migration effort. Identify templates and add-ons used ( nextjs , nextjs-xmcloud , nextjs-sxa , nextjs-multisite ) from your p...

  In my previous blog post on the Sitecore XM Cloud Content SDK, I discussed how you can install and start working with the Content SDK. In this blog, I'll focus on the differences between the JSS SDK and the Content SDK, along with some of the new concepts introduced in the Content SDK. Comparison with JSS SDK 1. Reduced Folder Size and Complexity The Content SDK removes functionality not strictly required for XM Cloud, leading to smaller, less complex starter applications that are inherently easier to understand and maintain. 2. Experience Editor Removal This is one of the most impactful changes. Unlike JSS, the Content SDK does not support the Experience Editor. Instead, all visual editing is handled through the XM Cloud Pages Builder in metadata integration mode. This eliminates the need for chromes integration mode—previously central to the Experience Editor—and enables further code optimizations. 3. Mapping Components In the Content SDK, all components must be manually reg...

  Sitecore has announced the release of the Content SDK . The Content SDK helps developers integrate XM Cloud content with their front-end applications. It is set to replace the existing JSS SDK for XM Cloud. This new Content SDK will exclusively support XM Cloud, providing a cleaner and more streamlined solution. In this blog, I’ll discuss the key features of the Content SDK, how to install it locally, and how to connect it with an XM Cloud instance for local development. Key Features Starter Template: Provides a ready-to-use Next.js template for fast project setup and seamless integration. Framework-Specific Support: Leverages Next.js features like locale-based routing for multilingual sites, plus multiple rendering modes including SSR (server-side rendering) and SSG (static site generation). GraphQL Utilities: Includes prebuilt queries to fetch content, layouts, site information, and dictionary data directly from Sitecore APIs. Multi-Site Capabilities: Supports ...

In my previous blog , I discussed how we can migrate content, media, and users using the XM to XM Cloud Migration Tool – GUI option . In today’s blog, I’ll walk you through the CLI (Command Line Interface) option , which provides the same functionality but is also ideal for scripting and automation . Step 1: Configuration Setup It is very important to use the same configuration settings as in the GUI version, stored in the appsettings.json file. If needed, you can adjust some values manually. You can also refer to a sample appsettings.json file here . Key Configurations RAIFs Configuration The XM to XM Cloud Migration Tool transfers content and media via RAIFs (batches) . The default values in appsettings.json are balanced for most customers. ItemsPerRaif defines the number of items per transfer. Too low → creates too many RAIF files. Too high → may impact transfer speed. MediaSizeLimit defines the maximum media size per RAIF. Must be a long value. Conte...