Show Menu
TOPICS×

Integrating with Adobe Analytics

Integrating Adobe Analytics and AEM as a Cloud Service allows you to track your web page activity:
  • An Adobe Analytics configuration enables AEM to authenticate with Adobe Analytics.
  • A framework identifies the data that is sent to your Adobe Analytics report suite.
The data includes page and user data, for example:
  • data that AEM components collect
  • link clicks
  • video usage information
  • the number of page visits from Adobe Analytics
The pages listed below can help you configure the integration. To be noted that Launch by Adobe is the defacto tool for instrumenting an AEM site with Analytics capabilities (JS libraries). Therefore, integrating AEM as a Cloud Service with Launch and Adobe Analytics goes hand-in-hand.
Adobe Experience Manager as a Cloud Service customers who do not have an existing Analytics account, can request access to the Analytics Foundation Pack for Experience Cloud. This Foundation Pack provides volume limited use of Analytics.
The IMS configuration (technical accounts) for Launch by Adobe is preconfigured in AEM as a Cloud Service. Users do not have to create this configuration.

Further Information

See:
  • Extending the Adobe Analytics Integration for information about developing components that collect user data and customizing the Adobe Analytics framework. Please note that "Analytics frameworks" are legacy in AEM, and their creation does not work in AEM as a Cloud Service because it requires the Classic UI. Launch by Adobe should be used instead, both for variable mapping and for deployment of JS libraries to pages.
  • The knowledge base article, Adobe Analytics integration - troubleshooting issues , for information about troubleshooting your Adobe Analytics integration.
If you are using Adobe Analytics with a custom proxy configuration, you need to configure two OSGi bundles (for example, with the Web console) required for the Apache HTTP Client proxy configurations. Both are required as some functionalities of AEM use the 3.x APIs, while others use the 4.x APIs. Configure: