Enable Analytics and Personalize in XM Cloud
XM Cloud offers analytics and personalization capabilities, albeit in a limited feature version. In this article, we will show you the steps to enable this.
You can check blog articles order by publish date.
XM Cloud offers analytics and personalization capabilities, albeit in a limited feature version. In this article, we will show you the steps to enable this.
In a previous article, we introduced how to set up SAML authentication with Microsoft Entra when setting up SSO in Sitecore Cloud Portal, and in this article, we will explain how to connect with Auth0 and OpenID Connect.
In the last issue, we proceeded to the SSO setup. This time, we will invite the target users, configure the applications they can use, and proceed to login. We can now proceed to the SSO settings and adding users.
The first step in using Sitecore's SaaS product is to add SSO, a user authentication mechanism. In this article, we will focus on the SSO configuration.
In this article, we will introduce you to the features of Sitecore Cloud Portal, a portal site that is available when you subscribe to Sitecore's SaaS product. In this article, we will reintroduce the Sitecore Cloud Portal.
XM Cloud offers two settings for redirects. Redirect Items, which operate on an item-by-item basis, and Redirect Map, which manages URLs related to redirects. These two are introduced in this article.
XM Cloud has a GraphQL Endpoint that allows content editing using GraphQL. This functionality is turned off by default, so this article will introduce the process of turning it on and making it usable.
Up to the last article, we were able to create a template of the target item in XM Cloud and retrieve the sample item in Json data using GraphQL. In the second half of this article, we will make the data viewable via RSS.
In this article, we will show you how to get a list of articles from GraphQL and create an RSS feed for XM Cloud content.
In the previous article, we deployed a website in Vercel using Context ID. I will check the procedure for synchronising the environment variables set in Vercel using the Vercel CLI so that they can be used in the development environment at hand.
Previously, when deploying in Vercel or connecting to XM Cloud using local Next.js, deployment was done using API keys and endpoints; since JSS 21.6, this has been changed to allow the use of Context IDs. This is introduced in this issue.
I have previously introduced the procedure for creating a new project and launching a new CMS. This time, we would like to create a development branch in the same GitHub repository and launch an instance using the code under development.