Sitecore getting started to advanced

 In Part 1 of the article we have seen the Sitecore XM Cloud Limitations of allowing only 8 variants to do personalization, In this article we will see how to overcome the limitation with the workaround. Considering the requirement that we have an existing multisite in Sitecore XM Cloud which has separate sites based on each country, now the client looking to remove the country sites and use one site for all countries but they want to personalize the home page component based on the country from the user visiting the page. The other requirement is that the content author should be in full control of personalization like assigning the datasource for the components etc.  So now the requirement is clear, we need to personalize the home page components based on all the available countries that the client has requested. So, In order to make this achievable, we have the following options. Directly use Sitecore Personalize instead of depending on Embedded personalization (here cont...

Part 1 of this article covers the Sitecore Pages personalization and its limitations. Part 2 of this article will provide the workaround for the limitations with a real-world scenario and code sample. In Sitecore XM Cloud, we are personalizing the item using Sitecore Pages with the help of the audience rule.  The personalization feature is working with the help of lightweight Sitecore Personalize, which we don't have access to, so we cannot see the audience rule(Variant) that we have created in the Sitecore XM Cloud Pages for an item in the lightweight Sitecore Personalize application. S uppose still we want to get the details like the  Client key  for configuration purposes or to verify the personalization rule using the CallFlows API manually using Postman, etc. In that case,  we need to connect with the Sitecore representative to get the information about credentials details like the Client key, etc. If we have a separate Sitecore Personalize license, we can lin...