Understanding Adobe Launch (Tags) environment mapping in AEM as a Cloud Service
When configuring Adobe Launch (AEP Data Collection Tags) in AEM as a Cloud Service, customers often expect separate configurations for DEV, STAGE, and PROD environments. However, the AEM Launch configuration UI only shows two tabs: Staging and Production. This leads to confusion about which Launch library is used by each AEM environment. To fix this, understand the default mapping and apply the correct configuration for your author and publish environments.
Description description
Environment
- AEM as a Cloud Service (AEMaaCS)- Sites
- Managed Services project with DEV, STAGE, and PROD
Issue/Symptoms
- AEM Launch configuration UI only shows Staging and Production tabs.
- No DEV option is available in the configuration UI.
- Uncertainty about which Launch library (Development, Staging, or Production) is used by each AEM environment.
Resolution resolution
Note: There is no DEV-specific Launch configuration inside AEM. All non-production author environments use the same Launch Staging mapping. The Production mapping is used only by the production publish environment.
- AEM as a Cloud Service uses a fixed mapping for Launch environments based on author and publish types.
- All author environments, including DEV Author and STAGE Author, always load the Launch Staging library. Use the Staging tab in the Launch configuration dialog for these environments.
- The Production tab applies only to the production publish environment, which loads the Launch Production library.
- Do not create a DEV-specific tab or mapping. This setup is by design.
Verification
- Check the rendered page in each AEM environment and verify which Launch library is being loaded.
- DEV Author should load the Staging library.
- STAGE Author should load the Staging library.
- PROD Publish should load the Production library.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f