Highlighted

AEM 6.5: Removing ClientLibs from Experience Fragments exported to Target | AEM Community Blog Seeding

kautuk_sahni

Community Manager

29-09-2020

BlogImage.jpg

AEM 6.5: Removing ClientLibs from Experience Fragments exported to Target by Todd J. Haser

Abstract

Intended Audience
Product and Business Owners, Target Practitioners, AEM Developers, Architects and Consultants.

Overview
NOTE: If you are just looking for the overlays, skip down to Overlays section below.

Personalization with Adobe Experience Manager [AEM] and Adobe Target [Target] was reimagined with AEM version 6.4 (current version as of this writing is 6.5.6.0). Experiences, created within AEM, can now be delivered directly to Target as HTML Offers. This enables the best of both worlds between AEM and Target. Experiences in AEM can be easily created, put through a workflow (approval/governance of content), and then published and exported to Target. Target Practitioners can then, easily, use these offers to seamlessly test and personalize content across multiple channels.

Experience Fragments [XFs] contain full html tags and all of the necessary Client Libraries (CSS/JS) to render the XF exactly as it was created by the XF Content Author. This is by-design. XFs, themselves, can be used in many different scenarios:
1. Within AEM Sites
2. Via 3rd-Party Consumption: Applications (SPAs), Mobile Apps, etc.
3. In Target as an XF Offer

Problem Statement
When using an XF Offer with Target on a page that is being delivered by AEM, the Targeted page already contains all of the necessary Client Libraries. In addition, the extraneous html in the XF Offer is also not needed (see caveat section). Here is an psuedo-example of the html in an XF Offer:


Read Full Blog

AEM 6.5: Removing ClientLibs from Experience Fragments exported to Target

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager