LogoLogo
WebsiteBlog
  • Introduction
  • CDP Overview
  • Identity Resolution
  • CDP Guidelines for Data Sanity and Campaign Governance
  • Login and User Management
    • Login to the platform
    • Change Password / Retrieve your Account
    • Role Based Access Control
      • User Management
      • Roles
    • Single Sign-On (SSO)
  • Events
    • Events Overview
    • App Events
    • Track
    • Identify
    • Page
    • Screen
    • Event Dictionary
  • Sources
    • Sources Overview
    • Android SDK
    • iOS SDK
    • JavaScript SDK
    • React Native SDK
    • Flutter SDK
    • REST API
    • Adobe Analytics Exports
    • SFTP
    • Kafka
    • Offline File Ingestion
  • Destinations
    • Destinations Overview
    • Quora Pixel
    • Hotjar
    • Clevertap
    • Google Analytics 4 (GA4)
    • Meta Pixel
    • Meta Conversion API
    • LinkedIn Insight Tag
    • Adobe Target
    • AppsFlyer
    • AWS S3
    • Criteo
    • Kafka
  • Integrations
    • Rudderstack
    • Azure Blob
    • Adobe Launch Private Extension
    • Adobe Launch Extension
    • Salesforce CRM
    • Microsoft Dynamics 365
  • Customer One View
    • Introduction
    • Basic details, Attributes and Devices
    • Segment and Engagement
    • Activity
  • Segments
    • Getting Started
    • Create a Segment
  • Channels
    • Getting Started
    • A/B Testing
    • SMS
      • Set up an SSP
        • Netcore
        • Twilio
        • Adobe Campaign Classic
        • Gupshup
        • Unifonic
        • Infobip
        • Tubelight
      • Add an SSP
      • Create SMS campaign
      • FAQs
    • Email
      • Set up an ESP
        • SendGrid
        • SendInBlue
        • SparkPost
        • Taximail
        • Netcore
        • Adobe Campaign Classic
        • Mailchimp
        • Oracle Email Delivery
        • Infobip
        • Vision6
      • 🆕Add an ESP
      • Create Email campaign
      • Common use cases with Email Editor
      • Why Email Notification may not get delivered?
      • FAQs
    • App Push Notification
      • Create App Push Notification - Android
      • Create App Push Notification - iOS
      • Why App Push Notification may not get delivered?
      • FAQs
    • WhatsApp
      • Configure a WSP
        • Yellow Messenger
        • Infobip
        • Gupshup
        • BIK.ai
        • Vonage
        • Sinch
        • Tubelight
      • Create WhatsApp campaign
      • FAQs
    • RCS
      • Add an RCS API
      • Example: Netcore RCS API
      • Create an RCS campaign
      • FAQs
    • Web Push Notification
      • Create a Web Push Notification
      • Create a Default Web Push Notification
      • FAQs
    • On-site Notification
      • Create On-site Notifications.
      • Common use cases with On-site Notification.
      • Notification Templates
    • Banner Personalization
      • Create a Personalized Banner
      • Create a Default Banner
    • External API
      • Create Engagement
      • Test your API configuration
      • Example Use Cases of External APIs
        • Use case 1: HubSpot - Create Contacts API
        • Use case 2: Exotel's Make a call API
        • Use case 3: Mailmodo's Send Campaign Email API
  • Ramanujan AI
    • Lead scoring
    • Channel Orchestration
    • Content Generator
      • Generate Web Push Content
  • Journey Builder
    • Overview- Journey Builder
    • View all Journeys
    • Create a Journey
    • Journey Reports
    • FAQs
  • Audience Export
    • Facebook Export Channel
    • Google Ads Export Channel
  • Analytics
    • Dashboard
      • Guiding through the Dashboard
      • Unique Profile
      • Profile and Merge Trends
      • Campaign and Revenue Dashboard
    • Campaign Summary
    • Events Occurrence
    • Event Telemetry
    • App Installs and Uninstalls
    • Funnels
    • Paths
    • Traffic Analysis
    • Cohorts
    • Data sanity between Funnels, Paths and Events
    • FAQs
  • Developer APIs
    • User Profile API
    • WhatsApp Opt-in/Opt-out API
    • Subscription Management
  • Settings
    • Product Label
    • Frequency Caps
    • Contacts
Powered by GitBook
On this page
  • Adobe Launch Configuration
  • Action Configuration
  1. Integrations

Adobe Launch Extension

This document covers the deployment instructions for Adobe Launch Extension for Lemnisk JavaScript SDK.

PreviousAdobe Launch Private ExtensionNextSalesforce CRM

Last updated 1 year ago

Adobe Launch Configuration

  • Go to Adobe Launch, and pick a Property.

  • Once you are inside, click on "Extensions".

  • Then click on "Catalog".

  • Search "Lemnisk", and you will get the Lemnisk extension.

  • Click the "Install" button.

  • 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.

Example:

Implement environment-specific logic:

Within your code or rules, you can use the value of the "Environment" data element to conditionally apply different behaviours or configurations based on the environment.

Client ID

Write Key

  • 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

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

  • Let us configure a Page Action. Created a Rule named "pageLoad", triggered by "Core" extension, "Window Loaded" event. Click on the "Actions"/"Add" button.

  • From the "Extension" dropdown, select "Lemnisk".

  • From the "Action Type" pick "Page".

  • Please fill in the appropriate fields, if needed you can use the Data Element icon next to the text fields.

  • Picking data elements.

  • Once done, press "Keep Changes".

We are done. You can follow Adobe documentation for deploying these changes in your dev/staging/prod environments!

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 ). Using data elements instead of specifying a static value, reference the corresponding data element that holds the environment information.

Lemnisk CDP UI