Web SDK migration & Adobe Source Connectors Considerations

[YohanKh1]

Hello. 

I have a use case that I am unable to find much research on and would like some input. 

Context: There are three sites.

1. Site A - has moved to web SDK and will need to get set up with CJA. The use case for CJA is the data from Site B and Site C.
2. Site B - will be moved to web SDK and will be available in CJA
3. Site C - Currently in AA; there is work to bring the data into Site A's CJA through AA source connectors.

My inquiry is - what happens to the Adobe Analytics source connectors if Site C moves to web SDK? 

• The ideas is to use the same schema on all three sites (if not all three, Site A & C, where we may have to extend the schema for site A as we bring in Site C data). 
• What happens to the AA source connectors between Site C--> Site A once the site C moves to Wed SDK. The method of moving to web SDK is also being considered (we may leverage the adobe data-object fields to translate the evars/props to xdm fields)

[Sumit-Kumar]

hi @YohanKh1,

Moving a site to webSDK does not automatically prepare the data for CJA as it depends how well the schema is created. web sdk is only the transport layer, so it is your xdm schema determines how well the data works in CJA.

if site c migrates to webSDK from appmeasurement sure you
will have the upgraded better library but it is still using the adobe data object AA style (evar/prop/events fields), note that:
that data object is designed for AA/target, not CJA.

 

mapping props/evars directly into xdm will give you an xdm schema that looks like aa, which is not ideal for long-term CJA use.

It is recommended to
create a clean, custom xdm schema with business-friendly field names for CJA.
have sites A, B and C all send data into this shared schema.
extend as and when needed.

to answer what happens to the aa source connector note that
the AA to AEP source connector works at the report suite level. this means it keeps sending AA data into AEP as long as the report suite is active, even after site C moves to web SDK.
if the goal is to use web sdk to AEP to CJA data, you’ll eventually have to disable the aa source connector once the migration is complete else it keeps flowing as it creates oob schema and dataset from the AA source connector.

you can differentiate sites
use a datasource id field (or dataset metadata) inside your unified schema so CJA can separate site A/B/C traffic.

Also as a side note if you end up using source connector and mixed web sdk by any chance then also there is a possibility to create a common data view and this year I did a skill exchange session on how to merge multiple report suite datasets in CJA using query service + the oob AA source connector. here’s the link if helpful:
https://experienceleague.adobe.com/en/docs/events/the-skill-exchange-recordings/cja/aug2025/journey-...