Adobe Launch Private Extension
This document covers the deployment instructions for Adobe Launch Extension for Lemnisk JavaScript SDK.
Installation Instructions
Lemnisk's Launch Extension is a private extension. The code is provided to our customers (for security reasons) and they can deploy it to their Launch Property.
Step 1: Installation is only needed if you don't have 'Lemnisk AIA' in your "Properties" -> "Extension"-> "Catalog" already. If it is present, you can skip the installation step.
Step 2: Download the code (zip file) from here or clone the repository
For TALIC please download from the TALIC branch here or switch to TALIC branch in the git repo above.
Step 3: Please run the following command inside adobe-launch-extension folder.
Step 4: Publish the package to your Adobe Organization.
Step 5: Once the integration works, you can publish it to other properties in your organization
Please refer Adobe Access Token guide for generating the credentials needed for the above command.
Important
In order to create an Integration in Adobe I/O you must be an Experience Cloud Organization Administrator or an Experience Cloud Org Developer.
Adobe Launch Configuration
Step 1: Go to Adobe Launch, and pick a Property.
Step 2: Once you are inside, click on "Extensions".
Step 3: Then click on "Catalog".
Step 4: Search "Lemnisk AIA", and you will get the Lemnisk extension.
Step 5: Click the "Install" button.
Step 6: Determine the different environments in which you want to configure the extension. This typically includes development, staging, and production. This can be determined by creating an “Environment” variable as shown in the below image.
Step 7: Configure dynamic values "Client ID" and "Write Key" (you can reach out to your Lemnisk customer success partner for these details or get them from the Lemnisk CDP UI). Using data elements instead of specifying a static value, reference the corresponding data element that holds the environment information.
Example:
Implement environment-specific logic:
Within your code or rules, you can use the value of the "Environment" data element to conditionally apply different behaviors or configurations based on the environment.
Client ID
WriteKey
Step 8: By referencing these data elements in your extension configuration and implementing environment-specific logic, you can effectively customize the behavior of the extension based on the environment in which it is deployed.
Please note that you can use DataElements to pick the write key and client id from the environment. This way you can do dev/staging/prod environment differentiation for Lemnisk tags. When you do this, please take care of any AEM-specific tags too (say many of you may have Browser Push tags from Lemnisk - this is not covered by this Launch configuration and has to be handled by AEM depending on the environment)..
Note that for the above configuration, you can hard-code write key and client id. This way Lemnisk will load the same tags across dev/staging/prod environments. You can still be able to make the environment differentiation in Segmentation variables in Lemnisk UI. Most of the clients who are on the previous versions of the Lemnisk Launch extension are in this configuration.
Action Configuration
The Lemnisk team will share an "Event Tracking Plan" in an Excel sheet. This will talk about which website "Events" should trigger which Lemnisk Extension "Actions". Please configure them. For example
Step 1: Let us configure a Page Action. Created a Rule named "pageLoad", triggered by the "Core" extension, "Window Loaded" event. Click on the "Actions"/"Add" button.
Step 2: From the "Extension" dropdown, select "Lemnisk AIA".
Step 3: From the "Action Type" pick "Page".
Step 4: Please fill in the appropriate fields, if needed you can use the Data Element icon next to the text fields.
Step 5: Picking data elements. Once done, press "Keep Changes".
Step 6: Now press 'Save'.
We are done. You can follow the Adobe documentation for deploying these changes in your dev/staging/prod environments!
Last updated
