While exporting experience fragment from aem to adobe target. Is it physically exported or just a reference of XF is exported to adobe target

[tejas18]

In one of the use case, we want to export the export experience fragment from AEM to adobe target via IMS config, So is it physically exported to target or it resides in AEM and only reference to it is getting exported?

[Jacob_T1 · Accepted solution]

Hi @tejas18 

My understanding (based on my own experiences) is that once you have built the Experience Fragment (XF) in AEM and click the "Export to Adobe Target" button - the XF will be exported to Target at that point in time.

If you then make further changes to the XF in AEM, these won't be reflected in Target until you click the "Update in Adobe Target" button which will re-sync the latest XF to Target again.

Based on this I assume that the underlying XF code is physically exported to Target rather then just a reference.

Docos: https://experienceleague.adobe.com/docs/experience-manager-65/administering/integration/experience-f... 

Thanks,
Jacob

[alexbishop]

Yes, that's correct, as the XF export ultimately works by utilising on the Target Create/Update Offer APIs