Exporting AEM Experience Fragment/Page Content for A/B Testing and External Systems without HTML Tags | AEM Community Blog Seeding

[kautuk_sahni]

Exporting AEM Experience Fragment/Page Content for A/B Testing and External Systems without HTML Tag... by Kiran Sg

Abstract

Problem Statement:
How to export experience fragment or page content from author to:

Adobe Target or any other application similar to Target without HTML Head/Body tags just component content for A/B Testing or targeting etc.
Salesforce Marketing Cloud or Adobe Campaign system without HTML Head/Body tags
Non-AEM sister sites are to be used as an iframe content.
Introduction:
If you are using an A/B Testing tool or when you are using SFMC for an email campaigning system in your project and you want to export Experience fragment or Page content to the external system using HTTP Post request.

Adding the entire HTML content (which includes the head, body etc.) on the existing page would negatively impact the accessibility score and page performance.

Usually with the above use case people follow exporting HTML content from AEM involves sending an HTTP request to the AEM server and receiving a response that contains the HTML content. This can be achieved using various tools and techniques, but in this article, we will focus on using the SlingRequestProcessor OSGi service.

Advantages of using are:

Process an HTTP request through the Sling request processing engine for example passing any selectors or params or suffixes etc.
Request parameter – Usually a “synthetic” request, i.e., not supplied by the servlet container.
Response parameter – Usually a “synthetic” response, i.e., not supplied by the servlet container.
ResourceResolver parameter – The ResourceResolver is used for the Sling request processing.

Read Full Blog

Exporting AEM Experience Fragment/Page Content for A/B Testing and External Systems without HTML Tag...

Q&A

Please use this thread to ask the related questions.