As part of the Adobe Marketing Cloud, Adobe Target lets you increase content relevance through targeting and measuring across all channels. Integrating Adobe Target and AEM as a Cloud Service requires:
Adobe Launch is necessary for managing client-side properties for both Analytics and Target in AEM pages (JS libraries/tags). That said, the integration with Launch is needed for “experience targeting”. For the Experience Fragments export to Target, you only need the Adobe Target Configuration and IMS.
Adobe Experience Manager as a Cloud Service customers who do not have an existing Target account, can request access to the Target Foundation Pack for Experience Cloud. The Foundation Pack provides volume limited use of Target.
An IMS configuration for both Launch and Target is necessary to properly integrate Target with AEM and Launch. While the IMS configuration for Launch is preconfigured in AEM as a Cloud Service, the Target IMS configuration must be created (after Target is provisioned). Refer to this video and this page to learn how to create the Target IMS configuration.
When configuring the Adobe Target Tenant ID and Adobe Target Client Code fields, please be aware of the following:
In both cases, be aware that:
As stated previously, the first case is the most common for AEM as a Cloud Service. Either way, make sure that both fields contain the correct information depending on your requirements.
If you want to change an existing Target Configuration:
To edit the Target configuration, follow these steps:
To apply a Touch UI configuration to a site, go to: Sites → Select any site page → Properties → Advanced → Configuration → Select the configuration tenant.
AEM offers an out of the box integration with Experience Platform Launch. By adding the Adobe Target extension to Experience Platform Launch, you can use the features of Adobe Target on AEM web pages. Target libraries will only be rendered by using Launch.
Existing (legacy) frameworks still work, but cannot be configured in the Touch UI. It is advisable to rebuild the variable mapping configurations in Launch.
As a general overview, the integration steps are:
A property is a container that is filled with extensions, rules, data elements.
Data elements are the placeholders to which you can map context hub parameters.
In Rule we define and order a sequence of actions, which are executed on site, to achieve targeting.
To learn how to build and publish please refer to this page.
|Change||Classic UI Configuration||Touch UI Configuration||Consequences|
|Location of the Target Configuration.||/etc/cloudservices/testandtarget/||/conf/tenant/settings/cloudservices/target||Earlier multiple configurations were present under /etc/cloudservices/testandtarget but now a single configuration is present under a tenant.|
Legacy configurations are still supported for existing customers (without the option to edit or create new ones). Legacy configurations will be part of content-packages uploaded by customers using VSTS.