Show Menu

Integrate Launch by Adobe

Technical walk-through of of how to configure the Adobe Experience Manager (AEM) integration with Launch by Adobe. This integration allows customer to pull the Launch "embed codes" and related JavaScript libraries into AEM Sites.


Launch is Adobe's next-generation tag management platform and the best way to deploy Adobe Analytics, Target, Audience Manager, Experience Cloud ID Service, and all of their 3rd party marketing solutions using Launch by Adobe.
The integration allows for the self-hosting of the Launch JavaScript libraries which gives the customer maximum control over their code, which is especially important for financial services customers. Alternatively, customers can use this integration to host their Launch libraries on Adobe's Akamai instance.
These three videos explain everything you need to know to successfully implement the integration, from creating a property in Launch, connecting Adobe IO to AEM, and configuring the Launch Cloud Service in AEM to finally pull in the embed codes and JavaScript libraries.

Step 1: Configure the Launch Property

In this step we will configure a Launch property with the bare-minimum configuration needed to set up the rest of the integration.

Full rights in Adobe Launch are required to complete the steps in this video.
More information about using Launch can be found in the Adobe Launch Videos, Help Documentation and Launch Reference Architectures landing page .

Step 2: Connect Adobe IO and Adobe Experience Manager

In this step, the Launch Integration will be configured in Adobe I/O and connected to AEM.

The Adobe Experience Platform Launch integration in the Adobe I/O interface is now labeled "Experience Platform Launch API" and is located under the "Adobe Experience Platform" heading.
System Administrator rights in the Experience Cloud organization and AEM admin rights are required to configure the Adobe IO integration and set up the IMS Configuration.

Step 3: Configure the Launch Cloud Service in Adobe Experience Manager

In the final step, the Launch Cloud Configuration will be set up and the correct Launch property will be applied to the AEM site.

There is a bug in some versions of the AEM Launch Wizard. The wizard incorrectly adds a prefix of /https: to the Staging, Production library URIs. This can easily be corrected by editing the wizard config and removing the /https: prefix.
Incorrect Library URI :
Corrected Library URI :
Admin rights in AEM are required to configure the Launch Cloud Service.

Additional Resources

If you have completed the steps above but you are not seeing the Launch embed codes in your own site please see the section "Map an Adobe Launch integration to a site in AEM" in the following article: