What is Adobe Launch
The Launch is a tag management platform from Adobe whose predecessor was previously known as DTM. It allows seamless integration of various digital marketing tools such as AAM, Adobe Analytics, Adobe Target, and all other third-party marketing solutions with Adobe AEM. In the launch, we call all these tools as ‘Extensions‘.
Launch provides an AppStore like convenience to select and install these extensions and also allows you to build and publish them easily. Launch allows customers to self-host the launch libraries Or they can even choose Adobe Akamai to host the launch libraries.
Launch can listen to what your customers are doing and based on that it can trigger actions created by you. (which of course are based on some rules defined by you as a developer)
When you integrate AEM with Launch, you get a way to keep all the above-mentioned libraries in one place which allows you to manage them easily and it reduces the overall go-live time by making them available in one place.
Image source: https://helpx.adobe.com/experience-manager/kt/integration/using/aem-launch-integration-tutorial-understand.html
The launch can be integrated using the below steps:
Step 1: Configure the Launch Property
To start the integration, you need to configure a property in the launch by following below steps:
- Go to experience cloud, and access launch: https://launch.adobe.com/
2. Create a new property, by clicking on the New Property button. You can configure properties as below :
A Property is a collection of rules, extensions, data elements, environments, and other libraries. In Launch, you can create multiple web properties per company.
Open the newly created property, and go to the Environments, ideally you should see a list of environments.
Click on the hosts, you should see this :
The default configuration is Managed by Adobe. This configuration makes use of Akamai to host and deliver the Launch libraries.
If you want to add any new host, you can click on the Add Host button. This way you can allow the custom hosting of the launch scripts, (if you don’t want to use Adobe’s Akamai hosting).
Now click on the Extensions tab. This tab allows you to see all added extensions. By default, the Core extension will be already added there. You can add further add more extensions depending on client requirements.
Data Elements: Data elements can be used to grab data from your site, store in the launch, and deliver it across different digital marketing solution tools. You can consider it as a dictionary data for your entire site.
Data elements can be used to capture information such as query strings, URL, cookie values, JS variable, etc. from your site. Eventually, you have a host of data elements collected from your website for various purposes and this collection of data elements becomes the dictionary of defined data that you can use to build your rules (events, conditions, and actions).
This data dictionary is shared across the Launch for use with any extension you’ve added to your property.
Now, go to the Publishing tab, and click on the Add New Library button,
Give a valid name to your new library and build it for different environments.
- You must have full rights on the launch, to perform the above steps.
- In the install tab of the environment, you can get the script tag to directly include the launch script.
Step 2: Connect Adobe IO and Adobe Experience Manager
Once you have created a launch property, you should configure the launch integration in Adobe I/O and should connect it to AEM later. Here are the steps:
Go to adobe i/o and create a new integration: https://console.adobe.io/home
When you click on the continue button, you will land on the below page.
On this page, select the highlighted (Experience Platform Launch API), and click on continue.
On the next page, you will be asked to fill in a few basic details, and also a public key. The public key can be obtained from the AEM environment which you will be integrating with the launch.
To obtain the public key, go to the AEM environment, and navigate
Go to Tools –> Security –> Adobe IMS configurations:
Create a new configuration :
Download the newly created key.
Now, go back to the launch and select the downloaded key.
Select the profile to finally create the integration.
Click on the Continue to Integration Details.
Now go back to the AEM server, back to the same screen where you created the public key, and click on the Next button.
Provide the details, and click on the create button.
That’s it. We are done with the Adobe IMS configuration with Adobe I/O.
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.
For this, go to the AEM environment, and then go to Tools -> General -> Configuration Browser, and then select the root folder where you want to configure launch.
Now go to the properties to check if this root allows cloud configurations or not. If not, then select the cloud configuration checkbox. And then save and close.
Now go to Tools–> Cloud Configurations –> Adobe Launch Configurations, select your site,
And click create.
After filling in the required details, click on the Next button.
Note: If you see the /https:// , prepended in the above Library URI, remove it.
Click create and that’s it.
Now once the integration is in place, we need to verify if the launch libraries are loading fine. For this, go to the view source of the page, and search for the ‘launch’ keyword. If you can find a script tag like this :
Or, you can write the below method in the web console to see the integration details.
It will give information about the web property you created.
If anything as mentioned is appearing on your site, that means your integration is working fine.
Feature Image Credit: Marketing vector created by stories – www.freepik.com