Target mode doesn’t appear on Sites

This article provides a fix for the AEMaaCS issue where the Targeting Mode doesn’t appear in Sites. To resolve this, remove the default path in Page Properties  under Personalization  if the codebase is /libs/settings/cloudsettings/legacy/contexthub.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

As per the Integration with Adobe Target using IMS user guide, Target is successfully activated for experience fragments with IMS. However, this doesn’t happen in Sites. The Targeting mode doesn’t 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’t check under libs anymore when the path under /etc/ doesn’t 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’d like answered about this topic, or read previous answered-questions, we invite you to view our Experience League Community blog post that includes this article, send us your questions and comments, and join our Experience League Campaign Community!