As part of the Adobe Marketing Cloud, Adobe Target lets you increase content relevance through targeting and measuring across all channels. Adobe Target is used by marketers to design and execute online tests, create on-the-fly audience segments (based on behavior) and automate the targeting of content and online experiences. AEM has adopted the targeting workflow that is used in Adobe Target Standard. If you use Target, you will be familiar with the targeting editing environment in AEM.
Integrate your AEM sites with Adobe Target to personalize content in your pages:
- Implement content targeting.
- Use Target audiences to create personalized experiences.
- Submit context data to Target when visitors interact with your pages.
- Track conversion rates.
To integrate with Target, perform the following tasks:
- Perform prerequisite tasks: Register with Adobe Target and configure certain aspects of the AEM author instance. Your Adobe Target account must have approver level permissions at a minimum. In addition, you must secure the activity settings on the publish node so that it is inaccessible to users.
- Opt into Adobe Target: The opt-in wizard takes your Target account information and creates an Adobe Target cloud configuration and a Target Framework. The wizard also associates your sites with the Target Framework. If the wizard cannot connect to target, refer to the connection trouble shooting section.
- Modify the default cloud configurations: If necessary, modify the cloud configuration and framework that the opt-in wizard created. For example, modify the framework to send additional context data to Target. If you want to use Adobe Analytics as a reporting source for Adobe Target, you need to modify the cloud configuration to point to the A4T configuration.
- Configure Activities: Associate your Activities with the Target cloud configuration.
If you are using Target with a custom proxy configuration, you need to configure both HTTP Client proxy configurations as some functionalities of AEM are using the 3.x APIs and some others the 4.x APIs:
- 3.x is configured with http://localhost:4502/system/console/configMgr/com.day.commons.httpclient
- 4.x is configured with http://localhost:4502/system/console/configMgr/org.apache.http.proxyconfigurator
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.
See Prerequisites for Integrating with Adobe Target for detailed information.
Out of the box, AEM 6.2 uses mbox.js for client-side integration. With Feature Pack 11577, you select whether to use at.js or mbox.js for client-side integrations. This feature pack is available via PackageShare. See Manually Configuring the Integration with Adobe Target.
Please note: You must have Service Pack 1 installed before installing this feature pack.
When you target a component in AEM author, the component makes a series of server-side calls to Adobe Target to register the campaign, set up offers, and retrieve Adobe Target segments (if configured). No server-side calls are made from AEM publish to Adobe Target.
Integrating AEM with Adobe Target requires knowlege of Adobe Target, AEM Activities management, and AEM Audiences management. You should be familiar with the following information:
When working with Adobe Target, the following is the maximum number of artifacts allowed within a campaign:
- 50 locations
- 2,000 experiences
- 50 metrics
- 50 reporting segments