Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.

AEM Experience Fragments: URL Externalization with Adobe Target | AEM Community Blog Seeding




AEM Experience Fragments: URL Externalization with Adobe Target by Exadel


The Basics
Using the “Export to Target” feature you can create an XF, add components to it, and then export it as an Adobe Target Offer. This feature can be enabled on an author instance of AEM. Since Experience Fragments are exported from the AEM author instance, you need to make sure that any references within the XF are externalized for web delivery.
This requires a valid Adobe Target Configuration and configurations for the link externalizer.

The Link Externalizer is used to determine the URLs for the HTML version of the Target Offer. Adobe Target requires all links inside the Target HTML Offer to be publicly accessed, so you need to publish the XF itself and all its links before pushing to Target.
When a Target HTML Offer is being constructed, a request is sent to a custom Sling selector in AEM. This selector is called .atoffer.nocloudconfigs.html.
After you generate the HTML page, the Sling Rewriter pipeline makes modifications to the output:
-> The HTML, head, and body elements are replaced with div elements. The meta, noscript, and title elements are removed.
-> AEM modifies any internal links present in HTML so that they point to a published resource. AEM follows this pattern for attributes of HTML elements

Read Full Blog

AEM Experience Fragments: URL Externalization with Adobe Target


Please use this thread to ask the related questions.

Kautuk Sahni

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies