Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
This page describes component personalization, adapting the content of a component to the visitor according to his or her personal preferences, needs and capabilities. Personalization at the level of components works the same way as page personalization except that you are personalizing a smaller item.
Component personalization is a feature available only in Magnolia EE Professional.
You can personalize a page and its components at the same time. The feature is disabled by default. To enable it, set
Component personalization is possible through the following actions in the Component action bar:
If the selected component hasn't been personalized yet, only the Add component variant option will be available:
To add a new variant to a component select the Add component variant . A new pull-down menu will appear in the component's top bar together with the variant icon placed next to the menu:
If not associated with any target audience, the newly added variant of the component will be named automatically by Magnolia ("VARIANT-0"). Once the target audience is defined and associated with the variant, the name of the audience will be displayed in place of the automatically generated name. The original component content will be renamed and accessible under the "ORIGINAL" option in the pull-down menu. This version of the component will be displayed to page visitors if no audience trait can be matched with the personalization properties assigned to the other variant(s) of the component.
Adding a variant to a component will affect its publishing status as well as the publishing status of its parent area and parent page: all of these are will be changed to "modified" (yellow) because creating a variant is considered an edit action on the component.
The fact that a page has content variants for some of its components, e.g. the page below called "maps-download" included in the documentation-tutorial-module, is marked by the variants icon appearing in the top bar of the page in the Edit and Preview views, and by the same icon placed also next to the name of the page in the page tree view:
Select the Choose audience option in the Action bar to choose the target audience for a component variant. Selecting a component variant is a prerequisite to choosing an audience for the variant.
The "ORIGINAL" content of a component can be marked as "ORIGINAL – HIDDEN". When marked as hidden, the content associated with the "ORIGINAL" will only be visible in the page Edit view.
Why hide the original? Hiding the original can be useful in a scenario in which the content is exclusive, targeting a particular audience. If no variants match, the original (fallback) content will be hidden. To hide/show the content of a component, select the Hide/Show original option in the Action bar.
You can serve different content to different audiences by changing the template used in a personalized component. This enables you to serve text to one audience, an image to another audience, video to a third audience and so on. To change the template of a component variant, click Change template in the Action bar and in the next dialog choose the template you wish to apply to the actual component variant:
There are three ways in which a variant may be deleted:
After the deletion of the component the publishing status of the parent area and the parent page will change to modified (yellow) because deleting a component is considered an edit action on the page.
personalizable property to
false in the component template to disable personalization. This disables the Add component variant action. You may disable personalization in components that must display the exact same content such as legal boilerplate text to all visitors. All components can be personalized by default.
renderType: freemarker templateScript: /my-module/components/html.ftl dialog: my-module:components/html deletable: false writable: false moveable: false personalizable: false
Define which roles are allowed personalize components. Name the roles in your area definition.
areas: myArea: availableComponents: myComponent: id: my-module:components/myComponent permissions: write: roles: [editors, superuser] move: roles: [senior-editor, superuser] delete: roles: [editors, superuser] personalize: roles: [senior-editor, superuser]
You can personalize a page and its components at the same time. This feature is disabled by default. To enable it, set