We're using AEM (AMS) and have been able to export experience fragments from AEM to Adobe Target. They show under Offers inside Adobe Target. However they don't show up correctly when we try to replace them in an activity in Target. Also the HTML for the fragment shows the message "cannot serve request to "fragment" on the server".
Hi @stiegjo22 ,
This usually happens when the Experience Fragment (XF) HTML that Target tries to render is not publicly accessible or is not being served correctly by AEM. In short, here’s how you can fix it:
Publish the XF – Make sure the XF and all referenced components/assets are published to the publish environment.
Check Dispatcher/Filters – Often the dispatcher or CDN blocks the XF HTML request. Add the XF path (/content/experience-fragments/...) to the allow rules.
Use the right variation (HTML) – In AEM Target integration, you must export the HTML variation of the XF, not JSON.
Preview URL – Open the fragment’s published URL directly in browser to confirm it serves HTML without the error. If it fails, check AEM logs for missing resource types or invalid Sling mappings.
Re-sync with Target – Sometimes re-exporting the XF to Target fixes mapping issues.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.