Web personalization

When initializing the Cloud SDK, developers can enable web personalizations by initializing the browser module of the events and the personalize packages, and then setting webPersonalization to true in the addPersonalize method:

CloudSDK({
  /* Your initialization settings */
})
  .addEvents()
  .addPersonalize({ enablePersonalizeCookie: true, webPersonalization: true })
  .initialize();

Behind the scenes, when web personalizations run, a <script> tag is inserted into the HTML document. This JavaScript contains the personalized content that will be displayed to site visitors. By default, the script loads in your app with async but without defer. You can change how the script loads by updating the code that enables web personalizations, such as:

webPersonalization: { async: true, defer: true }

After enabling web personalizations, they automatically run once when your app first loads.

When enabled, web personalizations run once when your app first loads, but they don't automatically run again on the same page. This means that you'll need to rerun web personalizations in, for example, the following scenarios:

You can rerun web personalizations by running window.scCloudSDK.personalize.triggerExperiences, either in your source code or directly inside the JavaScript of the web experience in Sitecore Personalize. Before running triggerExperiences, decide when you want web experiences to run again and make sure that scCloudSDK is available on the window object.

You can run functions available in the Cloud SDK events package to capture events that occur inside a web personalization. For example, when a site visitor clicks a button in a personalized pop-up. To do this, you need to run the event-capturing functions in the JavaScript inside your web experience or web experiment.