Expand my Community achievements bar.

Webinar: Adobe Customer Journey Analytics Product Innovations: A Quarterly Overview. Come learn for the Adobe Analytics Product team who will be covering AJO reporting, Graph-based Stitching, guided analysis for CJA, and more!
SOLVED

Migration to CJA from AA - Merging Historical and Future Data in CJA

Avatar

Level 1

I have a situation where we are migrating a number of digital properties (web and mobile apps) off of Adobe Analytics and onto Adobe CJA.  We would like to retain AA historical data within CJA, and so we are thinking to use the Source Data Connector to pull data from AA to AEP/CJA.  After that, future data would be collected via WebSDK and transmitted to AEP via XDM. 

 

From a CJA perspective, the ideal state would be the ability to create Analysis Workspace projects and panels containing data from both historical and ongoing collected data (via WebSDK > AEP) in one table or visualization, irrespective of how it came into CJA. 

 

A simple example of this might be a listing of site visits broken down by month; for this example, let's assume that 10/1/23 was a cutover date from AA to AEP/CJA.  A user would be able to create a simple report in Workspace by selecting the Visits/Session metric (or whatever we've named it in the CJA Data View) and the Month dimension, and the report would render the data as one would hope (and no one would be the wiser that anything interesting occurred on 10/1/23).  This particular example probably works just fine, but how about custom events/dimensions?   

 

Suppose you had an existing AA event and eVar - event1 and eVar1 - that you will be representing in CJA as some named metric and dimension.  Similar to the example above, you'd like to be able to build a single workspace panel in CJA that relates these two pieces of data and be able to have the time range span the cutover date from AA to AEP/CJA.

 

Does something like this rely on utilizing the same schema for historical data vs. future-collected data?  Initially, I was thinking to use the default schema when using the Source Data Connector to pull data into AEP from AA since that is quick to setup and get working.  However, our intended XDM schema in a WebSDK->AEP->CJA world would look very different, of course. 

 

Would derived fields be another approach for this?  Any other options I am overlooking?

 

Thanks in advance for any ideas or suggestions!

 

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi, this modeling exercise is quite complex, and its success relies on effectively unifying your schemas in XDM. This will ensure that your data remains consistent in reporting and analysis within CJA. Additionally, pay close attention to the Person ID methods declared in CJA, as they will greatly influence how you can join data across different implementation methods. For more guidance on XDM and AA schema handling, refer to the following resources:

https://experienceleague.adobe.com/docs/experience-platform/sources/connectors/adobe-applications/an...

https://experienceleague.adobe.com/docs/experience-platform/xdm/field-groups/event/analytics-full-ex...

The Analytics source connector streams data collected by Analytics to Platform in real-time, converting SCDS-formatted Analytics data into Experience Data Model (XDM) fields for consumption by Platform.

https://experienceleague.adobe.com/docs/experience-platform/datastreams/overview.html?lang=en

Depending on your use cases, you may also want to explore and review the mapping functionality of the Data Prep application.

https://experienceleague.adobe.com/docs/experience-platform/data-prep/home.html?lang=en

 

Derived fields is not an option here as it is more an end reporting layer component manipulation function at the CJA Connection>Data Views level and does not change or alter the underlying schema.

https://experienceleague.adobe.com/docs/analytics-platform/using/cja-dataviews/derived-fields.html?l...

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-blogs/derived-fields-use-cases-for-...

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-blogs/making-the-most-of-your-data-...

 

 

 

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

Hi, this modeling exercise is quite complex, and its success relies on effectively unifying your schemas in XDM. This will ensure that your data remains consistent in reporting and analysis within CJA. Additionally, pay close attention to the Person ID methods declared in CJA, as they will greatly influence how you can join data across different implementation methods. For more guidance on XDM and AA schema handling, refer to the following resources:

https://experienceleague.adobe.com/docs/experience-platform/sources/connectors/adobe-applications/an...

https://experienceleague.adobe.com/docs/experience-platform/xdm/field-groups/event/analytics-full-ex...

The Analytics source connector streams data collected by Analytics to Platform in real-time, converting SCDS-formatted Analytics data into Experience Data Model (XDM) fields for consumption by Platform.

https://experienceleague.adobe.com/docs/experience-platform/datastreams/overview.html?lang=en

Depending on your use cases, you may also want to explore and review the mapping functionality of the Data Prep application.

https://experienceleague.adobe.com/docs/experience-platform/data-prep/home.html?lang=en

 

Derived fields is not an option here as it is more an end reporting layer component manipulation function at the CJA Connection>Data Views level and does not change or alter the underlying schema.

https://experienceleague.adobe.com/docs/analytics-platform/using/cja-dataviews/derived-fields.html?l...

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-blogs/derived-fields-use-cases-for-...

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-blogs/making-the-most-of-your-data-...