Skip to main content

Personalisation

 Personalisation is mainly used for displaying the content based on the user clicks/actions.

Examples: 

  • Any ecomerce website shows the personalised content based on recent search of the Products.
  • Whatever the product you search in google , the same product will be displayed in FB.
The above are just examples where this personalisation will come into picture.

In AEM Personalisation is achieved in 2 Ways.

  1. AEM Context Hub
  2. Adobe Target

Here we will discuss only AEM ContextHub. 

Below is the minimum required procedure we should know as author to personalize the content.

Segment: Segment are nothing but the different conditions are embedded within the segment.   With in this segment we need to add the conditions when this segment have to be shown to the user. 

Procedure to Personalize the Page

Create a Segment 

Personalisation Tab --> Audience --> Create Context Hub Segment --> Add Segment Title --> Create.

Edit the Segment Created (Add the Comparator Properties Like Property and Value or Property/Property , Script Reference, Segment Reference)

Personalise the Page

Select Page which needs to Personalize Page --> Edit --> Targeting --> Add Experience Targeting --> Select newly added Segment --> Select specific component which needs to Personalize --> Author the required changes to the component and Publish the page.

Using the Experience Fragment for Personalising the content for components is recommended.

Note: By Default this Personalisation is not enabled for Pages, developer need to add required code changes for the same.

For more information on AEM , go through the below syllabus.

Comments

Popular posts from this blog

AEM Author Concepts

What is AEM? Author Publisher Dispatcher in AEM Touch UI vs C lass UI   DAM (Digital Asset Management) Replication/Publish in AEM Parsys/Responsivegrid/Iparsys Components Pages Templates Experience Fragments Content Fragments Emulator / Break Points RichText Tagging Sitemap Personalisation Workflows MSM(Multi Site Management) Users and Groups Environments in SDLC

What is AEM?

  AEM is full form is Adobe Experience Manager and many people call it as adobe cq5,cq5.   AEM is a web Content Management System Tool (wcms/cms), which is a used for building websites, mobile apps and forms. AEM makes easy to manage your content and assets.  By using aem, we can dynamically change the content within fraction of seconds and same can be shown in live. Examples:  News Channel websites, in news channel websites the layout (look and feel) will be same only the content changes dynamically. Other CMS Tools: WordPress,Drupal,Sitecore. For more information on AEM , go through the below syllabus. AEM Author Concepts

MSM (Multi Site Management)

 Multi Site Manager (MSM) allows aem developers to create copy of existing site and automatically update the copy when changes are done to the source site. Advantages of using MSM: Easily manage multiple websites that share common content. MSM allows aem developers to define relations between the sites so that content changes in one site are automatically replicated in all other sites. Reduces the time to manage your websites and increases the re-use of common content. Maintain common look and feel across all websites. When we should use MSM Sites are in multiple countries. Sites are in multiple languages. Need to reuse/replicate same content in multiple websites. Maintain consistent branding and content across websites. Creation of MSM from scratch (follow below) Create Language Masters Here we will create a sample English site, which will be used in the later point of creating multiple language copies. Create language-masters with any template. Create a sample site with Eng