Edge delivery system AEM Migration impact on Adobe Target Activities and Experience Fragments

[Paturi]

Hello, 

Our organization is working on a migration of AEM from traditional 6.5.19, to Edge delivery service (AEM), We are assuming there will be changes to experience fragment delivery and Change in site level CSS classes and structure of the website HTML. Does anyone who might have handled the migration know about the impact it might have on existing personalization and AB tests and any suggestions on how to handle the switchover. I'd appreciate any insights or first hand information about this change. 

Thanks, 
Ravi Paturi

[kandersen]

@Paturi I've not been part on such a migration, so my answer is purely from a theoretical perspective. 

If the site level css classes and structure will change, the activities will stop working and you'll likely have to make minor corrections to the activities in order to get them to work again.

Target is depending on the css classes and structure to identify the elements that the activities are applying changes to, so if the structure changes it won't be able to identify the elements correctly and the changes in an activity will not be applied.

Regards,

Kasper

[Paturi]

Hi Kandersen, 

I agree, We have been setting up dedicated classes on sites, which are used specifically to load personalized content on, as long as these classes persist on HTML level, am assuming all activities will continue to work as expected, We will conduct a quick POC before we take on all sites migration. Am just curious and anticipating effort and time at the moment. Do you know if the experience fragment will be impacted, or will the new paths automatically get updated, I wasn't able to find anything on how the XF delivery and JCR paths will be impacted, if you have any thoughts I'd appreciate you sharing them. 

Regards, 
Ravi Paturi

[kandersen]

@Paturi Unfortunately i have no idea how experience fragments will be impacted.

@Gokul_Agiwal any chance you would know?