Exporting Experience Fragment as plain html to Adobe Target



We are trying to export experience fragments to Adobe Target as plain HTML.

Experience Fragment has a component based on Adobe Dynamic Media. In order to load the image or video, we have to add client library in the page policy of the experience fragment template.

While some content is swapped with this experience fragment, we can see client libraries are getting loaded 2ce in the source which will increase in load time of the page.

Is there a way that experience fragment can be exported to adobe target as plain HTML rather than composed of client libraries.

Answers (1)

Answers (1)



I am looking for the solution to same issue -  exported experience fragment loads all client libraries  (js, css etc.) in the source which increases load time of the page and it takes forever to load the fragment. Please suggest.