Enable Automated Personalization

Current version: 10.1

You enable automated personalization when you want to let Sitecore AI decide which variant of a component to display to your website visitors. Sitecore AI automated personalization leverages and builds on top of the native personalization functionality provided by Sitecore XP.

Note

The component you want to personalize must have the required content variants defined.

You can use automated personalization on rendering variants or on component variants to display personalized data.

You can enable automated personalization at two different levels:

  • The component level, without setting any conditions, so Sitecore AI selects the most suitable variant of the component to display.

  • The personalization rule level, so AI decides which variant of the component to display when the conditions set by the personalization rule are fulfilled.

    Note

    You can use a mix of personalization rules specifying exactly which content to use, and rules that use auto-personalization.

You can enable automated personalization using the Content Editor or using the Experience Editor. The following procedure describes how to do it using the Content Editor.

To enable automated personalization on a component:

  1. Log in to Sitecore.

  2. Go to the Content Editor.

  3. In the content tree, navigate to the content item you want to personalize, and ensure that the required variants are defined and nested as child items of the component, as shown in the following example, where the component CTA - The Perfect Connected Home-4ML has three variants defined:

  4. In the content tree, click the Home node (to personalize a component from the site's home page), click the Presentation tab, then in the Layout group, click Details.

    The Layout Details dialog box opens:

  5. In the Layout Details dialog, click the SHARED LAYOUT tab, then click Edit. The Device Editor dialog opens.

    Note

    You can apply automated personalization on the shared layout or on the final layout.

  6. In the Device Editor dialog, click Controls, click the control that you want to personalize, and then click Personalize.

    The Personalize the component dialog displays the existing personalization rules if there are any.

  7. Enable automated personalization at the component level or at the personalization rule level:

    • To enable auto-personalization at the component level, click Auto-Personalize Component. A message warns you to ensure that the component has variants. Click Ok. The generic rule Use automated personalization score is added:

    • To enable auto-personalization on a specific personalization rule, click Auto-personalize rule. A message warns you to ensure that the component has variants. Click Ok.

  8. Specify the component folder that contains the personalized component variants. In the auto-personalized rule section, in the Content field, click Browse.

  9. In the Select Associated Content dialog, locate and click the folder that contains the component variants, and then click OK.

  10. After you have completed the configuration of auto-personalization rules, if there are multiple personalization rules, use the Actions drop-down menu to move the rule up or down to change the order in which it applies.

    Important

    You must publish the item for the personalization to take effect on your website.

Disable automated personalization

To remove automated personalization on a component:

  • Locate the Use automated personalization score rule, and In the Actions dropdown, click Delete, then click OK.

To disable automated personalization from a specific rule:

  • Locate the rule, click the Remove Auto-personalization button, then click OK.

    Note

    When you disable automated personalization from a rule, you must explicitly select the personalized content to use when rule's condition are fulfilled. Otherwise, you can delete the rule: click the Actions dropdown, click Delete, then click OK.

Do you have some feedback for us?

If you have suggestions for improving this article,