The integration of AEM with Adobe Target via the Target Standard API requires the configuration of Adobe IMS (Identity Management System) and Adobe I/O.
Support for the Adobe Target Standard API is new in AEM 6.5. The Target Standard API uses IMS authentication.
Using the Adobe Target Classic API in AEM is still supported for backward compatibility. The Target Classic API uses user credentials authentication.
The API selection is driven by the authentication method used for AEM/Target integration.
Before starting this procedure:
Adobe Support must provision your account for:
Your organization’s System Admininstrator should use the Admin Console to add the required developers in your organization to the relevant product profiles.
The first stage of the configuration is to create an IMS Configuration in AEM and generate the Public Key.
In AEM open the Tools menu.
In the Security section select Adobe IMS Configurations.
Select Create to open the Adobe IMS Technical Account Configuration.
Using the drop down under Cloud Configuration, select Adobe Target.
Activate Create new certificate and enter a new alias.
Confirm with Create certificate.
Select Download (or Download Public Key) to download the file to your local drive, so that it is ready for use when configuring Adobe I/O for Adobe Target integration with AEM.
Keep this configuration open, it will be needed again when Completing the IMS Configuration in AEM.
You need to create the Adobe I/O Project (integration) with Adobe Target that AEM will use, then assign the required privileges.
Open the Adobe I/O console to create an I/O Project with Adobe Target that AEM will use:
See also the Adobe I/O tutorials.
Open the Adobe I/O console for Projects:
Any projects that you have will be shown. Select Create New Project - the location and usage will depend on:
Select Add to Project followed by API:
Select Adobe Target, then Next:
If you are subscribed to Adobe Target, but do not see it listed then you should check the Prerequistes.
Upload your public key, and when complete, continue with Next:
Review the credentials, and continue with Next:
Select the required product profiles, and continue with Save configured API:
The product profiles displayed with depend on whether you have:
The creation will be confirmed.
You must now assign the required privileges to the integration:
Open the Adobe Admin Console:
Navigate to Products (top toolbar), then select Adobe Target - <your-tenant-id> (from the left panel).
Select Product Profiles, then your required workspace from the list presented. For example, Default Workspace.
Select Integrations, then the required integration configuration.
Select Editor as the Product Role; instead of Observer.
From the Adobe I/O Projects console you can see a list of all your integration projects:
Select View (to the right of a specific project entry) to show further details about the configuration. These include:
Some of these you will need to complete the Adobe I/O integration for Target in AEM.
Returning to AEM you can complete the IMS configuration by adding required values from the Adobe I/O integration for Target:
Return to the IMS Configuration open in AEM.
Here you can use the details from Adobe I/O:
"aud"line of the Payload section below, e.g.
"https://ims-na1.adobelogin.com"in the example below
Confirm with Create.
Your Adobe Target configuration will be shown in the AEM console.
To confirm that the configuration is operating as expected:
Select your configuration.
Select Check Health from the toolbar, followed by Check.
If successful, you will see the message:
The configuration can now be referenced for a Cloud Service to use the Target Standard API:
Open the Tools menu. Then, within the Cloud Services section, select Legacy Cloud Services.
Scroll down to Adobe Target and select Configure now.
The Create Configuration dialog will open.
Enter a Title and, if you want, a Name (if left blank this will be generated from the title).
You can also select the required template (if more than one is available).
Confirm with Create.
The Edit Component dialog will open.
Enter the details in the Adobe Target Settings tab:
Tenant ID: the Adobe IMS Tenant ID
For IMS this value needs to be taken from Target itself. You can log into Target and extract the Tenant ID from the URL.
For example, if the URL is:
Then you would use
IMS Configuration: select the name of the IMS Configuration
API Type: REST
A4T Analytics Cloud Configuration: Select the Analytics cloud configuration that is used for target activity goals and metrics. You need this if you are using Adobe Analytics as the reporting source when targeting content. If you do not see your cloud configuration, see note in Configuring A4T Analytics Cloud Configuration.
Use accurate targeting: By default this check box is selected. If selected, the cloud service configuration will wait for the context to load before loading content. See note that follows.
Synchronize segments from Adobe Target: Select this option to download segments that are defined in Target to use them in AEM. You must select this option when the API Type property is REST, because inline segments are not supported and you always need to use segments from Target. (Note that the AEM term of ‘segment’ is equivalent to the Target ‘audience’.)
Client library: Select whether you want the AT.js client library, or mbox.js (deprecated).
Use Tag Management System to deliver client library: Use DTM (deprecated), Adobe Launch or any other tag management system.
Custom AT.js: Leave blank if you checked the Tag Management box or to use the default AT.js. Alternatively upload your custom AT.js. Only appears if you have selected AT.js.
Configuration of a Cloud Service to use the Target Classic API has been deprecated (uses the Adobe Recommendations Settings tab).
Click Connect to Target to initialize the connection with Adobe Target.
If the connection is successful, the message Connection successful is displayed.
Select OK on the message, followed by OK on the dialog to confirm the configuration.
You can now proceed to Adding a Target Framework to configure ContextHub or ClientContext parameters that will be sent to Target. Note this may not be required for exporting AEM Experience Fragments to Target.