Adobe Target & AEM Integration using Launch

In my previous blog, I have explained how we can integrate AEM with Launch using Adobe I/O. If you have not visited that earlier, you can visit it here.

In this blog, I will explain how you can integrate Target with Adobe AEM using Launch.

What is Target

A successful business is that which can deliver what its customers need and that too at the right time. Moreover, there are times when a business wants to promote or recommend a particular product/solution to its customers when they are exploring others but are not finding a suitable match as per their expectations. Target is Adobe’s personalization tool, which helps the business find out the best content by utilizing tests and deliver it to the end-users at the right time.

Adobe Target can even integrate with Adobe Analytics so as to give the business total insight into what marketing offer or content is doing best and thus can achieve more customer satisfaction more customer engagement.

Integration With Adobe AEM

Image source:

We will learn here about how we can integrate Adobe Target with AEM through Launch. Below are the steps you can follow:

  1. If you have not configured launch already, please follow the steps mentioned here. If you have already configured Launch, then go to the Launch console and look for the property you created.
  2. Go to the Extensions tab, go to the catalog and search for Adobe Target V2 and install it.
  3. Build the library for any of the development of your choice (e.g. development, staging, production).
  4. This way you can configure Adobe Target via launch. The required library will be available to the AEM instance once the configuration is in place.
  5. Now, as we have already configured the Target, we can use it for targeting content based on different experiences created in Target.


This is how we can integrate Target with AEM using the Adobe Launch. Though Adobe Launch is used to expose Adobe Target on the AEM webpages on the live site, the AEM Author server needs to be connected to Adobe Target only through the backend by using Legacy Cloud Services. This connection will be required when you want to have authoring capabilities served by AEM author to Target, for example, to export experience fragments to Target from AEM Author.

Establish AEM Author- Target connection

  1. Go to AEM → Tools → cloud services → Legacy Cloud Service
  2. Look for Adobe Target, and create a new configuration.
  3. Provide the account details like id and password if you use the legacy way of connecting AEM and Adobe Target. However this has become deprecated now and AEM 6.5 onwards, the default way of authentication is using IMS authentication. All of the Adobe Target standard API calls will be authenticated using IMS tokens.
  4. In the above settings, get the client code from your Adobe Target –> Administration –> Implementation –> Account Details –> Client Code.
  5. Now on AEM, go to the Tools –>Security–> Adobe IMS Configuration.  Create a new certificate and download the same.  As you need to provide the same in your Adobe IO for configuration.
  6. Now go to the adobe i/o console and create a new project and then click on Add API to create a new adobe target integration.
  7. Upload the public key certificate you recently created and click on Next.
  8. Copy the public key obtained and keep it saved somewhere.
  9. Click Next, select the profile you want to select and then save the configuration.
  10. Once the configuration is created go to the Service Account to obtain few more details about this configuration.
  11. Now go back to the AEM where we were creating the IMS configuration. Retrieve the client secret and paste it under the Client Secret field. Copy the client Id under the API key and get the payload from the Generate JWT tab. Also, get the authorization server detail from the payload itself. Then click create.
  12. Once the IMS configuration is created, it’s time to link it with the Legacy Service that we started. Select the newly created IMS configuration from the dropdown. Provide the client code and then click on the Connect To Adobe Target button. Once the configuration is in place, you are ready to export content from AEM to Target.

( Please check here, how to use the cloud configuration in Pages or Assets. )

Exporting Experience Fragments to Target

To export fragments to Target, go to the Experience fragments, and navigate to the one which you want to export to target.


  • Go to the properties, and go to the Cloud Services tab, select the Adobe Target from the Cloud Service Configurations dropdown, and then browse the required configuration in the cloud configuration, select the appropriate one and then save.

  • That’s it. Now if you want to export any experience fragments to Target, you can simply create one, and then export after publishing it.

  • Once the above integrations are done, you can ask the Target developers to provide you with the Property implementation code. Alternatively, if you are aware of the target activity, then go to the Target launch console, find your activity, and get its implementation code.

Now there are two ways you can integrate Target with AEM. Either you can copy the above implementation code in the root page component. Or you can go to the Launch console and there you can integrate Target using target extension.

Using Target Extension in Launch

To use the Target extension in Adobe Launch, follow the below steps:

  1. Go to the Rules, and create a new rule.
  2. Then, go to the Events, and select an event of type ‘Library Loaded (Page Top)’.Then, go to the actions, and create one with Acton Type as ‘Load Target‘.
  3. Then, from the same extension, select the Action Type as ‘Add Params to Page Load Request‘.
  4. On the right side, provide the ‘at_property‘ and give the same value to it which you copied from the target property.
  5. Finally, add the action type of ‘Fire Page Load Request’ to make sure you get the target script on the page as soon as it loads. That’s the way of integrating Target with AEM using Launch.


Hope you liked the blog!

Feature Image Credit: Arrow photo created by freepik

About The Author