Integrating with Adobe Target
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:
- using the Touch UI to create a Target Configuration in AEM as a Cloud Service (IMS configuration required).
- adding and configuring Adobe Target as an extension in Adobe Launch .
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.
Creating the Adobe Target Configuration
- Navigate to Tools → Cloud Services .
- Select Adobe Target .
- Select the Create button.
- Fill in the details (see below), and select Connect .
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.
Editing the Target Configuration
To edit the Target configuration, follow these steps:
- Select an existing configuration and click Properties .
- Edit the properties.
- Select Re-connect to Adobe Target .
- Select Save and Close .
Adding a configuration to a site
To apply a Touch UI configuration to a site, go to: Sites → Select any site page → Properties → Advanced → Configuration → Select the configuration tenant.
Integrating Adobe Target on AEM sites by using Adobe Launch
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 page(s).Target libraries will only be rendered 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:
- Create a Launch Property
- Add the required extensions
- Create a Data Element(to capture context hub parameters)
- Create a Page Rule
- Build and Publish
Creating a Launch Property
A property is a container that will be filled with extensions, rules, data elements.
- Select the New Property button.
- Provide a name for your property.
- As the domain enter the IP/host on which you want to load the launch library.
- Select the Save button.
Adding the required extensions
- Select the Extension Catalog option, and search for Target in the filter.
- Select Adobe Target at.js and Click on the Install option.
- Select the Configure button. Notice the configuration window with the Target account credentials imported, and the at.js version for this extension.
- Select Save to add the Target extension to your Launch property. You should be able to see the Target extension listed under the Installed Extensions list.
- Repeat the steps above to search for the Adobe ContextHub extension and install it (this is required for the integration with contexthub parameters, based on which targeting will be done).
Creating a Data Element
Data elements are the placeholders to which you can map context hub parameters.
- Select Data Elements .
- Select Add Data Element .
- Provide the name of data element and map it to a context hub parameter.
- select Save .
Creating a Page Rule
In Rule we define and order a sequence of actions, which will be executed on site, to achieve targeting.
- Add a set of actions as exemplified in the screenshot.
- In Add Params to All Mboxes add the data element configured earlier (see data element above), to the parameter which will be sent in the mbox call.
Build and Publish
To learn how to build and publish please refer to this page .
Changes in content structure between Classic and Touch UI configurations
Classic UI Configuration
Touch UI Configuration
Location of the Target Configuration.
Earlier multiple configurations were present under /etc/cloudservices/testandtarget but now single configuration will be present under a tenant.
Legacy configurations are still supported for the existing customers (without the option to edit or create new ones). Legacy configurations will be part of content-packages uploaded by customer using VSTS.