Utilizing Adobe Analytics report suite data in Customer Journey Analytics

Adobe Analytics customers can easily leverage their report suites in the Adobe Experience Platform and Customer Journey Analytics using the Analytics Source Connector. The following discussion explains how to do so.


As you get ready to start using Adobe Analytics report suites in AEP and CJA, there are several things you should consider doing to prepare your data for a seamless move to Customer Journey Analytics. Please review the following page for more information:

Set up report suites for ingestion into the Adobe Experience Platform and CJA

Once you have prepared your data you are ready to start configuring report suites for use in AEP and CJA.

  1. Create a dataflow for each report suite you wish to use in AEP and CJA. The Analytics Source Connector is the tool which allows you to create a connection (a.k.a dataflow) between Adobe Analytics and AEP. You will use the source connector to create one dataflow for each report suite you want to use in AEP. The dataflow creates a copy of your report suite data where the schema has been converted to XDM for consumption by AEP applications including CJA.

    Each report suite configured with a dataflow via the source connector is stored as a separate dataset in the AEP Data Lake. 13 months of historical report suite data will automatically be included with each dataflow, and new data will flow into AEP on an ongoing basis. (Note that beginning April 26, 2023, the backfill in non-production sandboxes is limited to 3 months.) With the Analytics Source Connector you don’t need to worry about creating the schema ahead of time. A standardized schema specific to Adobe Analytics is automatically created for you. However, AEP’s Data Prep tool can be used to enhance this schema before the data is stored in Data Lake and made available to CJA. Please note that certain types of data are filtered out by the source connector and will not be present in the dataset in AEP Data Lake. Other rows may be filtered out between Data Lake and CJA. See Compare your Adobe Analytics data to CJA data for more details.

  2. Use Data Prep to help you combine report suites in CJA. Data Prep can be used for many types of data transformation, and one common use for Adobe Analytics data is to resolve differences in prop and/or eVar mappings across multiple report suites so that report suites can easily be combined within CJA. See combine report suites with different schemas for more details.
  3. Enable Cross-Channel Analytics as necessary. When combining multiple datasets in CJA, the identity stitching capabilities of Cross-Channel Analytics can help resolve different ID namespaces into a single stitchedID for a single view of the customer across devices and channels. See Cross-Channel Analytics overview for more details.
  4. Create one or more CJA connections. Once the datasets for your report suites are available in AEP Data Lake, you can create one or more CJA connections to bring those datasets into CJA. Within a connection, report suite data can be combined with other types of data, allowing you to create a true cross-channel view of customer experiences.
  5. Create one or more CJA data views. A data view is a container specific to Customer Journey Analytics that lets you determine how to interpret data from a CJA connection. Data views have many powerful configuration options for customizing the data which is presented to your users within Analysis Workspace.

Comparing Customer Journey Analytics and Adobe Analytics

Customer Journey Analytics and Adobe Analytics have a number of similarities. For example, both CJA and Adobe Analytics offer the power of Analysis Workspace for freeform speed-of-thought analysis. However, since CJA is an application within the Adobe Experience Platform and utilizes AEP for data ingestion, CJA and Adobe Analytics differ in a number of important ways. The following articles are helpful for understanding these differences:

On this page