Personalization effect tracking

Current version: 10.1

Running a personalization test gives you information about how personalized content performs compared to default content, when shown to a specific audience. You can allocate up to 100% of website traffic to the test. Out of the traffic allocated to testing, 50% of the audience for a rule sees the personalized content, and 50% sees the default content.

Important

Before you start a personalization test, you must disable Personalization effect tracking for the component that you want to test.

After you apply a personalization rule, you might want to continue to keep an eye on its effectiveness. However, if everyone in a target group sees the personalized content, you no longer have a control group to compare the results to. For that reason, you might want to use the Personalization effect tracking feature.

When you enable personalization effect tracking on a component, 10% of the traffic to the component is allocated to effect tracking. Within the effect tracking group, half of the target group for each personalization rule views the personalized component while the other half views the default component. The trailing value/visit of these two groups is compared. This enables Sitecore to display effect data for each experience, for example in the Personalize a component dialog box, and in the Active personalized experiences list.

Note

The default traffic allocation for effect tracking is 10%. A system administrator can change the traffic allocation in the Content Testing config file.

You enable personalization effect tracking in the Personalize a component dialog.

Effect tracking data for a component is reset if you change content on the page or if you make any change in the Personalize a component dialog.

Note

Personalization effect tracking is only applicable to page items. If you personalize a component on a template or standard values item, you must disable effect tracking for the component.

Do you have some feedback for us?

If you have suggestions for improving this article,