To integrate AEM with Adobe Target, you must have a valid Adobe Target account. This account must have approver level permissions at a minimum. When you register with Adobe Target, you receive a client code. You need the client code and your Adobe Target login name and password to connect AEM to Adobe Target.
The Client Code identifies the Adobe Target customer account when calling the Adobe Target server.
You must secure the activity settings node cq:ActivitySettings on the publish instance so that it is inaccessible to normal users. The activity settings node should only be accessible to the service handling the activity synchronization to Adobe Target.
The cq:ActivitySettings node is available in CRXDE lite under /content/campaigns/nameofbrand under the activities jcr:content node; for example /content/campaign/we-retail/master/myactivity/jcr:content/cq:ActivitySettings. This node is only created after you target a component.
The cq:ActivitySettings node under the activity's jcr:content is protected by the following ACLs:
- Deny all for everyone
- Allow jcr:read,rep:write for "target-activity-authors" (author is a member of this group out of the box)
- Allow jcr:read,rep:write for "targetservice"
These settings ensure that normal users do not have access to the node properties. Use the same ACLs on author and on publish. See User Administration and Security for more information.
When editing an activity in Adobe Target, the URL points to localhost unless you change the URL on the AEM author node.
To configure the AEM externalizer:
The new Target Library file, AT.JS, is a new implementation library for Adobe Target that is designed for both typical web implementations and single-page applications.
AT.js offers several improvements over the mbox.js library:
- Improved page load times for web implementations
- Improved security
- Better implementation options for single-page applications
- AT.js contains the components that were included in target.js, so there is no longer a call to target.js
AT.js is only compatible with AEM and Adobe Target Cloud Services configuration if you have Feature Pack 11577 installed. Out of the box, AEM 6.2 uses mbox.js for client-side integration. With this feature pack, you select whether to use AT.js or mbox.js for client-side integrations. This feature pack is available via PackageShare.