Connect your Adobe Experience Manager Instance with Launch
The following instructions provide guidance on configuring Adobe Experience Manager (AEM) with Adobe Launch. Although your AEM site may differ from the example site used below, you can use these steps as a guide for setting up your own configuration.
Adobe Launch is the next generation of Dynamic Tag Management. It provides a platform-based approach to building Dynamic Tag Management (DTM) extensions and a streamlined distribution system to quickly deploy client-side DTM libraries. Custom resources can now be created and reused within DTM to simplify the distribution of client side web applications.
These instructions include the following sections:
To Setup Adobe Launch:
-
On www.launch.adobe.com, click New Property.
-
On the Create Property box, provide the details for the new property and click Save.
-
Click the Extensions tab and install the Analytics extension.
-
Click on Adobe Analytics extension.
-
Enter your Adobe Analytics Report Suite ID in the corresponding report suites environments, such as Production Report Suites. If you do not have separate environments then please add the same report suite ID for all environments.
-
If you do not know how to find the Report Suite ID, login via Marketing Cloud in Analytics, click Admin >Report Suites and create a new report suite or copy an ID of an existing report suite that you want to use.
-
Click Save after entering the Report Suite ID as shown below.
-
Make sure you have the following extensions:
-
Click the Rules tab and click on Create New Rule.
-
Enter the rule name as Analytics and click the Add button under EVENTS.
-
Specify the Event Configuration options as shown below and click Keep Changes.
-
Click the Add button in the Actions section and specify the following options to Send Beacon. Click Keep Changes.
-
Make sure your final Rule definition appears as shown below. Click Save.
-
Click the Adapters tab, then click Add Adapter and then create an akamai adapter as shown below.
-
Click the Environments tab, then click Add Environment and create Dev, Stage, and Production environments.
-
Save the rule and click the Publishing tab. Click Add New Library.
-
Provide a Name for the build, select the Dev (Development) environment, and then click Add All Changed Resources.
-
Build for development and staging and then approve for production.
To configure Launch with AEM 6.4:
-
On the Adobe I/O Console, click New Integration.
-
Click Access an API and then click Continue.
-
Under Experience Cloud, select Launch, by Adobe and then click Continue.
-
Select New Integration for fresh setup and click Continue.
-
In the AEM instance in a new window and click Tools > Security > Adobe IMS Configurations.
-
Create a new Adobe IMS Configuration certificate as shown below:
-
Download the public key certificate by clicking on Download Public Key. This certificate needs to be uploaded in the Adobe I/O console integration.
-
On the I/O Console Integration window, click Select a file and upload the AEM-Adobe-IMS.crt in Public Key Certificates.
-
On the Overview tab, copy the Client ID and Client Secret. Then copy the JWT Payload and Authorization Server info from JWT tab.
-
Return to the AEM IMS Configuration step and provide the copied details from the I/O Console integration. Save the configuration.
-
In your AEM Instance, click Tools > Cloud Services >Adobe Launch Configurations.
-
Create a new configuration under the We.Retail website. Select the Associated Adobe IMS Configuration, Company and Property as shown below.
-
In your AEM instance, click Sites, then select Card View from upper right corner and click the info properties icon.
-
On the Advanced tab, select Cloud Configuration.
-
Select the We.retail path and save & close the configuration.
-
Open the We-Retail website. Right click and select Inspect > Sources. You will see that the Launch scripts are firing and events are flowing in the designated report suite.
AEM 6.3 does not have the official connector for Launch. However, to connect your AEM 6.3 instance with Launch, you can follow work around presented below.
To configure Launch with AEM 6.3:
-
In your DTM account, create a dummy empty property Adobe_Launch. Please do not customize this property as we are not using it in our integration.
-
In your AEM instance, click on Tools or the Hammer icon in the left panel.
-
In Deployment, click Cloud Services.
-
Locate "Dynamic Tag Management" and click "Configure Now".
-
Provide a Title and Name for the configuration and click Create.
-
In your Dynamic Tag Management profile, click on the DTM Account and copy the API Token.
-
Paste the API token to AEM > DTM Configuration window and click Connect To DTM.
-
Select the company and the dummy property that you previously created.
-
Click the Staging Settings and Production Settings tabs and uncheck the Use Self Hosting.
-
In Launch > Environments > Staging, copy the header code and replace it in AEM > DTM Configuration Staging Settings Header code section.
-
In Launch > Environments > Production, copy the header code and replace it in AEM > DTM Configuration Production Settings Header code section. Click OK.
-
After the configuring, it should appear as shown below. Nake sure the scripts are from Launch environments.
-
In your AEM instance, click Sites, and open the page in Card View from the upper right corner.
-
Click the Properties icon for the website that you want to connect to Launch.
-
Click Cloud Services > Add Configuration and Select Dynamic Tag Management.
-
Select the Launch integration you created in previous steps. Click Save & Close.
-
Open the We.Retail website. Right click and select Inspect > Sources. You will see that the Launch scripts are firing and events are flowing in the designated report suite.
- Hiren Shah @hirenshah111.
- John Wight @johnwight.
Please help make this solution as useful as possible. If you find a problem in the documentation or have a suggestion, click the Issues tab on this GiHhub repository and then click the New issue button. Provide a title and description for your comment and then click the Submit new issue button.
