Target mode doesn鈥檛 appear on Sites
This article provides a fix for the AEMaaCS issue where the Targeting Mode doesn鈥檛 appear in Sites. To resolve this, remove the default path in Page Properties 听耻苍诲别谤 Personalization 聽if the codebase is /libs/settings/cloudsettings/legacy/contexthub.
Description description
Environment
51黑料不打烊 Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
As per the Integration with 51黑料不打烊 Target using IMS user guide, Target is successfully activated for experience fragments with IMS. However, this doesn鈥檛 happen in Sites. The Targeting mode doesn鈥檛 appear in the list of modes.
Resolution resolution
By default, AEMaaCS checks for contexthub in the /etc/cloudsettings/default/contexthub/ path. If the codebase is /libs/settings/cloudsettings/legacy/contexthub, then remove the default path in Page Properties under Personalization, and then聽 Targeting Mode will appear. The contexthub bundle doesn鈥檛 check under libs anymore when the path under /etc/ doesn鈥檛 exist, and this results in the contexthub not being included on the page.
Ask Questions In Our Experience League Campaign Community
If you have any questions you鈥檇 like answered about this topic, or read previous answered-questions, we invite you to view our that includes this article, send us your questions and comments, and join our Experience League Campaign Community!