Blueprint Developer Manual / Version 2512.1
Table Of ContentsWhile Section 5.5, “Localized Content Management” addresses the need to serve different regions and languages, Native Personalization addresses the need to serve different users. It allows you to present different content to different users of the same site, depending on various conditions.
Note
To use Native Personalization, you need to have an Engagement Cloud licence. If you do not have a licence, contact your Key Account Manager or the CoreMedia Support for details.
Native Personalization supports two use cases. First, you can assign users to user segments based on their preferences, traits, or past behavior, so that the site can choose the most suitable content for them. Second, during an A/B test Native Personalization can assign users randomly to a test case group or a control group, so that you can compare new and old content.
To this end, you can define personalization variants for content items. A variant stores both the variant's content and the condition under which it is chosen. In the following, this manual refers to personalization variants simply as variants.
Note
Do not confuse personalization variants with the localization variants used for multi-site content management (see Section 5.5, “Localized Content Management”). For localization, CoreMedia clones all content items of a site to a derived site, where you can apply arbitrary changes. For personalization, you create variants only for specific content items with audience-specific content and, in general, keep the amount of changes small.
Note
Native Personalization determines and renders variants inside CoreMedia Content Cloud. This is different from the client-side Personalization Hub, which integrates third-party personalization providers such as Dynamic Yield. CoreMedia Engagement Cloud typically provides the user segments and A/B test cases used as conditions.
