Expand my Community achievements bar.

Join Cristinel Anastasoaie, Timothy Furlow, and Brent Kostak, WEDNESDAY, 2/28/24 @8am PT for the next Adobe Target Community Q&A Coffee Break on topics from the recent High Performance Recommendations Webinar PT 2 of the ongoing Target Personalization Maturity Webinar Series

Steps to Integrate AEM with Target


Level 4

Sharing steps below highlighting integration from AEM to Target (on AEM 6.3.2),considering At.js is enabled till staging servers through DTM.

a. Cloud Configuration done in AEM for Target

b. Enable targeting mode in project

In head.html add below line at the top

<sly data-sly-use.clientLib="/apps/granite/sightly/templates/clientlib.html data-sly-call="${clientlib.js @ categories='granite.utils,cq.analytics'}"/>

b. Before closing body tag, add line in bold below

<cq:include path="cloudservices" resourceType="cq/cloudserviceconfigs/components/servicecomponents"/>

c. In body.html add below line at top

<sly data-sly-resource="${'cloudservices' @ resourceType='cq/cloudserviceconfigs/components/servicecomponents'}"/>

If changes are not getting reflected in AEM for rules applied for different experiences, validate and getting mbox option required issue. To Resolve this , need to install service pack AEM- Release Notes available at https://helpx.adobe.com/experience-manager/6-3/release-notes/sp3-release-notes.html

0 Replies